An audit finding with no owner
“Which algorithms are in use, where, and who approved them?” The honest answer is a spreadsheet three people maintain, and it was wrong the day it was finished.
ANKASecure© centralizes cryptographic decisions in a three-layer policy engine — algorithm availability, key rotation and key lifecycle — defined per deployment and overridable per tenant, with 37 policy templates (29 algorithm availability, 6 rotation, 2 lifecycle), the availability templates aligned with NIST, NSA CNSA 2.0, BSI, ANSSI, ETSI and CRYPTREC among others. Every key generation, rotation and cryptographic operation is checked against the active policy before it runs and refused with a reason when it violates it; a policy change propagates to every service instance in under a second. Authority over operations is modelled as revocable capability grants with constraint policies on a platform/tenant/operator role model. Each operation is recorded with its algorithm, key, outcome and reason in a signed, tamper-evident audit trail, every policy change is itself a signed audit event, and the trail is queryable per tenant and forwardable to a SIEM with the signature preserved. The console computes five posture measurements from the live estate. Discovery and inventory are delivered by ANKATech channel partners.
The decision lives in every team’s code: which cipher, which key length, which library, which mode. ANKASecure© takes that decision out of the applications, makes it once, enforces it before every operation, and keeps the evidence that it applied.
Is this you
“Which algorithms are in use, where, and who approved them?” The honest answer is a spreadsheet three people maintain, and it was wrong the day it was finished.
Every team picks its own library, parameters and key handling. The standard exists; nothing enforces it, so each release is a new place for it to drift.
The board adopted a cryptographic standard. No system in the estate can refuse an operation that violates it, so compliance is a matter of trust and a yearly review.
Who signs this: A CISO or head of security architecture who is accountable for a standard they cannot enforce, and a GRC lead who has to evidence it. If the answer to “which policy applied to this operation?” is a meeting, this is the conversation.
Why existing approaches fall short
Crypto sprawl is not the result of poor engineering. It is what happens when every team inherits a library and chooses its own parameters, and nothing between the application and the key decides whether the operation is allowed. The tools a security team already has each govern a piece: where keys are stored, when certificates expire, what the estate contains. None of them sits where the algorithm is chosen.
Who chooses the algorithm
Can it refuse a disallowed operation
What it can evidence
What a new standard costs
The board adopts a cryptographic standard: no new keys below a given strength, post-quantum or hybrid for new long-lived data. The KMS keeps issuing whatever key type an application requests, because the request is valid. Six months later a discovery scan finds new keys below the standard in three business units. Each team opens a ticket; two close it, one asks for an exception. At the next audit the standard has not changed, the inventory has, and the finding is the same. Nothing was broken. Nothing could refuse.
How it works
Applications keep referencing a key identifier and calling the same operation. ANKASecure© decides what that means, checks it, and writes down that it did.
Algorithm availability, key rotation and key lifecycle are three policies, defined once for the deployment and overridable per tenant. A template names the standard — NIST, NSA CNSA 2.0, BSI, ANSSI, ETSI, CRYPTREC and more — or a custom policy names your own.
Key generation, rotation and every cryptographic operation are checked against the active policy before they run. A violation is refused with the reason, not logged and allowed. A policy change reaches every service instance in under a second.
Who may exercise which operation, on which keys, under which constraints, until when — ANKASecure© models that as capability grants with constraint policies, on a role model that separates platform, tenant and operator authority. A grant can be revoked without touching the data it governed.
Each operation is recorded with its algorithm, key, outcome and reason, signed, in a tamper-evident chain, and every policy change is itself a signed audit event. The trail is queryable per tenant and forwards to your SIEM with the signature intact, so an auditor verifies it without trusting the forwarding step.
Control done right
NIST’s crypto-agility guidance describes the target plainly: a cryptographic policy translated into a machine-consumable configuration and, for an application, enforced through an API. The fair objection to any central layer is that everything comes to depend on it. That is answered by how the layer behaves when it cannot decide, and by what it leaves where it already is.
The policy is evaluated where the cryptography executes, before any key is used. A request with no resolvable tenant, or a deployment policy that does not verify, is refused rather than served under a default: an unreadable policy denies.
The platform administrator sets the deployment policy and decides, tenant by tenant, whether its administrators may set their own. Every tenant policy is held to the deployment’s minimum security strength, and a compliance-locked deployment refuses changes to its own policy.
An optional quorum makes changes to algorithm, rotation and lifecycle policy, and to a key’s limits, wait for a set number of approvers. Destroying a key always does. Revoking, suspending or declaring a compromise never waits: a response to an incident is not put to a vote.
Each event is signed, the stored trail is chained per tenant and verifiable on demand, the signed tables are write-once for every runtime role, and every read of the trail is itself recorded. Your SIEM receives the original signature, so it can verify without calling back.
The control plane does not replace the HSM or cloud KMS that holds the keys, the identity provider, or the SIEM. The reference architecture is explicit: an architecture that requires the enterprise to consolidate its key, identity or security infrastructure before governance can improve has not met the bar. Nor does it require every cryptographic function to move into one platform. It governs the operations that are brought to it, and keeps keys in the custody you already chose.
The enforcement gap
Between the day an organization adopts or tightens a cryptographic requirement and the day it can show that every governed operation conforms, the requirement exists only on paper. That interval is the governance counterpart of the cryptographic response gap: it is not set by the strength of the standard, but by how many places have to change before anyone can refuse an operation that violates it.
Translation
Enforcement
Existing material
Cryptoperiods
Evidence
Review
On a control plane the first two rows collapse into a policy change. The third becomes a measurement: the conformance reading shows, per tenant, the live keys whose algorithm no longer satisfies the policy now in force, so tightening a standard produces a worklist instead of a surprise. Rotation intervals above the deployment maximum or the key class’s maximum cryptoperiod are refused when they are set, and the evidence is the signed trail itself. What stays long is everything the plane does not see, which is why onboarding the critical applications first matters more than onboarding many.
Four pillars, and each one states what it measures, what it deliberately does not, the threshold it passes at, and the action that would close it. Conformance is judged against each tenant’s own declared policy — never against an external bar — and a tenant that declares no policy is counted as unmeasured rather than quietly passed.
Fifteen minutes
Live, on a real deployment, on the kind of estate you have. Nothing in this list is a mock-up or a roadmap item.
The posture view: the five CAPA pillars measured across the estate, computed from live keys and policies.
A tenant running on the deployment default. A standard’s template is applied to it; the change is visible on every service in under a second.
An application asks for a key the policy no longer allows. The request is refused, with the reason the auditor will want to read.
A constrained capability is granted to a counterparty, exercised once, and revoked. The data it governed is untouched.
The audit trail is queried: each operation with its algorithm, key and outcome, and each policy change beside them, signed, in a chain that would show any edit.
Your audit finding, answered on the deployment rather than on a slide.
Policy on paper is not the requirement
The current European and payment-card frameworks no longer stop at “use strong encryption”. They require a documented cryptographic policy, criteria for choosing mechanisms, control over the whole key lifecycle, and a way to change the cryptography when the assessment changes. The NIS2 implementing rules name crypto-agility outright. What none of them accepts is a policy that nothing enforces.
DORA RTS, Art. 6(3)–(4)
DORA RTS, Art. 7(1)–(3)
NIS2 Art. 21(2)(h); Implementing Regulation (EU) 2024/2690, Annex 9
PCI DSS v4.0, 3.7.4–3.7.5
PCI DSS v4.0, 12.3.3
NIST CSWP 39, §5
DORA asks for provisions to change the cryptographic technology as cryptanalysis develops, and the NIS2 implementing rules ask for review at planned intervals against the state of the art. A policy that cannot be changed without a release is a policy that will not be changed on time.
An operation the policy refuses is recorded with its reason, signed like any other. That the control worked is a record an auditor can read, not an inference from the absence of incidents.
ANKASecure© maps its controls onto these frameworks and produces the evidence. It does not maintain your certificate register, inventory your estate or certify you; the determination remains your auditor’s.
What it rests on
Shipping
Three-layer policy engine
Algorithm availability, rotation and lifecycle policies; deployment-wide with per-tenant override; propagation in under a second.
Shipping
37 policy templates
29 algorithm-availability templates, 6 rotation templates and 2 lifecycle templates.
Shipping
Capability grants and constraint policies
Explicit, revocable authority over cryptographic operations, on a role model that separates platform, tenant and operator.
Shipping
Signed audit trail
Tamper-evident chain recording each operation’s algorithm, key, outcome and reason, and every policy change; queryable per tenant; forwardable to your SIEM with the signature preserved.
Shipping
Posture measurement
Five measurements computed from the live estate in the console, with the provenance of each number.
Per channel
Discovery and inventory
What your estate uses today, delivered by ANKATech channel partners. Discovery produces visibility; the control plane produces control.
The framework
The Cryptographic Control Plane reference architecture describes each pillar through the scenarios it must handle and one practical test. This solution is the governance pillar’s own definition, and it is measured against its test.
04
Primary pillar
Scenario realised
Enforcing a new enterprise security requirement
Practical test
“Can the organization prove, by querying the control plane, which policy applied to a given operation, and change that policy centrally?”
01
Primary pillar
Scenario realised
Evolving cryptographic strategy without an application release
Practical test
“Can the cryptographic strategy change without requiring an application change or release?”
02
Supporting pillar
Scenario realised
Maintaining revocable cryptographic authority over third parties
Practical test
“Can the organization govern policy across all its trust domains without moving keys, and revoke a third party’s cryptographic authority without re-encrypting the data?”
Maturity move
From a KMS and partial inventory with no policy governance to a Control Plane that enforces the standard on every governed application. Level 3 is the plane in place; levels 4 and 5 are the estate coming under it, application by application.
It does not inventory your estate. Finding where cryptography is used today is a discovery engagement, and ANKATech partners run it.
It does not govern cryptography that never reaches the plane. A library call inside application code that does not delegate the operation is invisible to policy until that application is brought under it.
It does not certify you. ANKASecure© maps its controls to NIST CSWP 39, the GSA PQC Buyer’s Guide and OWASP and hands you the evidence; the determination is still your auditor’s.
Where to start
Cryptographic governance does not start with a program across the estate. It starts with one requirement the organization has already adopted and cannot yet refuse to violate, and one set of applications where refusing it matters.
1
Choose the requirement and the scope. Map it to a policy template or a custom policy, decide who owns the deployment policy, which tenants may set their own, and which changes need a second approver.
2
ANKASecure© applying that policy on a live deployment: a violating request refused with its reason, existing keys that no longer conform, and the signed trail an auditor would read.
3
One business unit or critical application under the policy, with keys anchored in your existing HSM or KMS and the audit trail forwarded to the SIEM your security operations team already uses.
Whitepaper
Why hardcoded cryptography is the structural problem, the pattern identity, networking and secrets already followed, CAPA’s five pillars and six-level maturity model, and a migration path toward the control plane. 68 pages, November 2026.
Read it online →Download the PDF
The download opens on this page as soon as the form is submitted. We ask for a corporate account so we can route follow-up to the right team.
After this
No new deployment, no second contract for the platform. The policy engine that governs the estate is the one that migrates it and the one that governs counterparties.
The one nobody could answer. Fifteen minutes on a live deployment to show the policy that answers it, and the evidence behind it.
Book the demo