Journal · Rocket Software · Audit

Rocket Software audit activity: what we are seeing.

Rocket Software has grown by acquisition, and the licensing exposure has grown with it. From the buyer side the activity clusters on entitlement that moved and got renamed as portfolios were absorbed. Advisors are seeing rising Rocket audit and contract declaration requests, and the products from ASG and the former Micro Focus estate are where it concentrates.

A Rocket audit follows the acquisition trail. Entitlement moved, got renamed, and drifted.

Rocket Software has assembled its portfolio through acquisition: ASG Technologies in 2021, and the Micro Focus and OpenText Application Modernization and Connectivity (AMC) business in 2024, among others. Since then it has renamed and consolidated products across that estate, folding a set of terminal emulators that includes the former Micro Focus RUMBA line into Rocket Secure Host Access. That history is exactly what a Rocket audit tests. When a product changes owner, then changes name, the entitlement document and the deployed software stop matching unless someone keeps them aligned. The activity we observe clusters on entitlement across the acquired portfolios, on emulation seat counts, on the data from the Rocket licensing daemon, and on the push to move perpetual licenses to subscription at renewal.

The pattern we commonly observe is an entitlement reconciliation that the buyer is poorly positioned to win unless the products are mapped first. Terminal emulation licensed per named or concurrent seat drifts as headcount and access change, and unused seats are rarely reclaimed. The licensing daemon reports deployed and concurrent usage, and a buyer who has not validated that data hands Rocket the reading. Renaming makes it easy to lose the thread between the product on the invoice and the entitlement that covers it. The buyers who come through a Rocket audit cleanly are the ones who mapped every renamed product back to its original entitlement, reconciled emulation seats against active users, and validated the daemon data before the notice arrived. Read this with what happens to pricing after a vendor is acquired and the Rocket Software publisher hub.

Four Rocket audit focus areas

Where Rocket Software audits cluster · what we commonly observe and the buyer defense

Focus areaWhat Rocket checksBuyer defense
Acquired portfolio entitlement Products from ASG and the Micro Focus and OpenText AMC estate, often renamed Map every renamed product back to its original entitlement
Emulation seat counts Named and concurrent seats on terminal emulation Reconcile active seats, reclaim unused before the count
Licensing daemon data Deployed and concurrent usage reported by the licensing daemon Validate daemon data independently against your deployment
Perpetual to subscription Pressure to convert perpetual licenses to subscription at renewal Protect perpetual rights, model the conversion before agreeing

These are patterns we commonly observe across Rocket Software audits, not statements of Rocket audit policy. Your specific entitlements, acquisition assignment terms, and metrics govern; validate against your own records and your contract before relying on any position.

Three defenses that hold

№ 01

Map renamed products to original entitlements

The single most common gap in a Rocket audit is the broken thread between a renamed product and the entitlement that covers it. Build a crosswalk from every product you run today back to the agreement and SKU it was licensed under, accounting for ASG and Micro Focus and OpenText AMC origins and every rename since. An entitlement you can trace is an entitlement you can defend. See Rocket Host Access licensing.

Trace every product back to where it was licensed.

№ 02

Reconcile emulation seats

Terminal emulation licensed per named or concurrent seat drifts steadily as people join, leave, and change roles, and the unused seats are almost never reclaimed. Reconcile the seat count against active users before the audit does, retire the dormant ones, and confirm whether your metric is named or concurrent. A seat count you have cleaned is a seat count you control. See our Rocket Software cost optimization service.

Clean the seat count before it is counted for you.

№ 03

Protect perpetual rights through the subscription push

A common renewal pattern is pressure to convert perpetual licenses to subscription, often framed as the only path to current support. Preserve your perpetual rights, separate the support question from the conversion question, and model the full lifetime cost of subscription against maintaining perpetual before agreeing to anything. The conversion may be right, but it should be a buyer decision made on the numbers. See the quiet rise of third party support.

Convert on your numbers, not under deadline.

Where the Rocket audit is won

A Rocket audit follows entitlement through the acquisitions. The defense is a crosswalk you built first. Map the renames, reconcile the seats, protect perpetual rights.

48 hr

Mobilization on an audit notice

$180M+

Mainframe spend negotiated on the buyer side

500+

Engagements delivered since 2019

Frequently asked questions

Q1

What does Rocket Software focus on in an audit?

Four areas: entitlement across the acquired portfolios from ASG and the Micro Focus and OpenText AMC business that have often been renamed, seat counts on terminal emulation, usage data from the Rocket licensing daemon, and the push to convert perpetual licenses to subscription at renewal. The common thread is entitlement that moved and got renamed as the portfolio was acquired.

Q2

Why has Rocket audit activity increased?

Rocket has absorbed large portfolios through ASG in 2021 and the Micro Focus and OpenText AMC business in 2024, then renamed and consolidated many products, including folding several emulators into Rocket Secure Host Access. Acquired estates with drifted entitlement are a common audit target, and advisors have observed rising Rocket audit and contract declaration requests as the portfolios integrate.

Q3

How should I respond to a Rocket audit notice?

Treat it as an entitlement reconciliation across acquired products. Map every renamed product back to its original entitlement before sharing anything, reconcile emulation seats against active users, validate the licensing daemon data independently, and answer each request in writing scoped to the products in question. Protect perpetual rights and model any subscription conversion before agreeing. See what good license governance looks like.

Q4

How can MLE help with a Rocket audit?

We build the product to entitlement crosswalk across the acquired portfolios, reconcile emulation seats, validate the licensing daemon data, and manage the response from the buyer side so the reconciliation runs on your evidence. Our audit defense service mobilizes within 48 hours of a notice and our Rocket Software cost optimization service trims the profile the audit and the next renewal build on.

Related: Rocket Software publisher hub · IBM audit activity · Broadcom (CA) audit activity · Rocket Host Access · audit defense

Audit notice or renewal under 18 months out? We mobilize within 48 hours.

Get expert help

Rocket audit notice in hand? We mobilize within 48 hours and map every entitlement to your evidence.

Get expert help