Product · High audit risk
IBM Cognos licensing and audit defense.
Cognos Analytics mixes per user and processor based metrics, role tiers that are easy to miscount, and a bundled Db2 that buyers routinely use past its allowed scope. Those are exactly the seams IBM probes. We challenge the count line by line. Independent and buyer side only.
User reconciliation · roles mapped to entitlementsBundle scope · limited use Db2 defended
How Cognos is licensed.
Cognos Analytics is licensed against named user roles and, for some deployments, against processor capacity. Authorized User entitlements are assigned to specific individuals by role, with administrators, authors, and consumers carrying different entitlement weights. A user who only views dashboards is not the same line item as one who builds and schedules reports, and counting them as equals in either direction creates exposure.
Where Cognos is licensed by processor, the PVU metric applies: PVU per core times the cores allocated to the software, with sub-capacity available only when ILMT is deployed and reporting correctly. On Cloud Pak for Data, Cognos is consumed through entitlement on the platform metric rather than as a standalone install, which changes how the count is read entirely.
Cognos also ships with a restricted use Db2 for its content store and reporting repository. That entitlement is limited to supporting the Cognos deployment. Using it as a general purpose database is one of the most common bundling findings IBM raises.
Common audit traps.
The Cognos findings that show up again and again, and where the real exposure hides.
01
Role miscount
Consumers, authors and administrators counted at the wrong tier, or inactive accounts left assigned, inflating the user claim.
02
Bundled Db2 overreach
The restricted use Db2 shipped with Cognos used beyond the reporting repository, treated by IBM as an unlicensed Db2 deployment.
03
PVU sub-capacity gaps
Processor based Cognos defaulted to full capacity because ILMT was missing, broken, or not reporting for the period.
04
Shadow user growth
Self service adoption adds consumers faster than the license count is updated, so deployment drifts past entitlement quietly.
05
Cloud Pak metric confusion
Cognos consumed on Cloud Pak for Data measured as if it were a standalone install, double counting against entitlement.
06
Non production sprawl
Test, development and disaster recovery instances assumed to be free, when their licensing depends on the entitlement terms.
How we defend it.
01
Contain
Scope the Cognos data request and control what leaves your network until it is curated and defensible.
02
Reconcile
Map active users to roles and entitlements, and recalculate any processor based capacity before IBM finishes theirs.
03
Challenge
Dispute role miscounts, bundled Db2 claims and full capacity defaults item by item with evidence.
04
Settle
Close on a number that names the products and counts, with forward terms folded into the deal.
A related result.
Enterprise · Cognos + Maximo
$2.8M
over-deployment cut
User reconciliation
Actual user counts mapped to entitlements, excess license claim removed at renewal.
Manufacturing · WebSphere + Db2
71%
claim reduced
Methodology challenge
Incorrect PVU values and denied sub-capacity reversed against clean ILMT evidence.
Financial Services · ILMT
$3.1M
penalty avoided
Sub-capacity reinstated
Missing agents and misconfigured reports corrected before full-capacity charging landed.
Related services.
The engagements that carry a Cognos audit from notice to settlement.
Cognos finding on the table?
$250M+ in exposure defended. 500+ engagements. We mobilize within 48 hours of your audit notice. Independent and buyer side, every time.
Get audit help now →
The IBM Audit Brief
Audit triggers, ILMT pitfalls, and settlement tactics for IBM software buyers.
IBM Audit
Independent, buyer side IBM software audit defense and negotiation. Not affiliated with IBM Corporation.
Independent. Not affiliated with IBM Corporation.Buyer Side · Est. 2019