Oracle Identity Governance has completed Common Criteria certification, an evaluation milestone that matters far more to the identity governance and administration (IGA) market than its modest announcement footprint suggests. For organisations running identity governance in government, defence, financial services or critical national infrastructure, independent security evaluation is often the difference between a platform that can be deployed and one that cannot.

The procurement problem certification solves

Identity governance platforms occupy a privileged position in the enterprise. They hold the authoritative map of who can access what, they drive joiner, mover and leaver workflows, and they execute access certifications that auditors rely on. That means the IGA layer sees, and frequently controls, the most sensitive entitlement data in the estate. Yet buyers have historically had to accept vendor assertions about how that data is protected, isolated and evaluated.

Procurement teams in regulated sectors have responded by pushing security evaluation requirements into tenders. The result is a familiar friction. An IGA programme is approved on functional grounds, then stalls for months while the vendor’s assurance evidence is scrutinised, or while the buying organisation accepts a residual risk position it would rather not take. Common Criteria certification reduces that friction by moving the evaluation from a bilateral negotiation into a recognised, repeatable assessment against a published protection profile.

What common criteria actually changes for IGA

Three practical consequences follow from certification of an identity governance platform.

First, the security target becomes explicit. Common Criteria work forces a vendor to document the boundary of the evaluated product, the threats it addresses, and the assumptions placed on the operating environment. For identity governance that documentation is unusually valuable, because deployments are rarely clean. Hybrid directories, legacy applications and locally managed repositories sit outside the evaluated boundary, and buyers benefit from seeing that line drawn clearly rather than inferred.

Second, certification supports the audit narrative. Access governance controls are typically evidenced through policy, configuration and operational records. A certified platform gives auditors an external reference point for the integrity of the underlying control layer, which shortens the distance between “the tool is configured correctly” and “the tool itself is trustworthy.”

Third, it reframes competitive evaluation. Identity governance administration buying has long been driven by connector coverage and certification campaign usability. Assurance evidence adds a dimension where smaller vendors can differentiate without matching the broadest connector catalogue, and where larger vendors face pressure to keep evaluations current rather than treating them as a one-off exercise.

The limits worth understanding

Certification is a snapshot of a defined configuration, not a permanent property of every deployment. Version currency, deployment topology and local customisation all affect whether the evaluated assurance carries over to a live environment. Identity lifecycle management programmes therefore need to ask vendors how often evaluations are refreshed and which releases they cover, and they should treat the security target as a document to read rather than a badge to cite.

For teams building a regulated IGA roadmap, the certification is best understood as one input among several: it shortens assurance conversations, it strengthens audit evidence, and it gives security architecture a documented baseline to test against. It does not replace the control design work that determines whether identity governance actually holds under operational pressure.