ANKASecure© replaces the long-lived private key or the cleartext file an outsourced process usually receives with a capability grant. Five objects describe each relationship: an exchange context for the counterparty and the keys in scope, the cryptographic actor that invokes, authenticated through workload identity federation, the capability granted, the key protected by the owner’s HSM or KMS, and a constraint policy that enforces a validity window, a usage cap, a per-minute rate limit and single use. The existing channel (SFTP, managed file transfer, APIs or messaging) stays in place. Every invocation is recorded in a signed audit trail forwardable to a SIEM, revoking the grant refuses the next invocation without re-encrypting data, and the key and algorithm behind a grant can change, including to post-quantum algorithms, without any change on the third party’s side.

Your provider has your private key. It should have a permission.

Sharing data with a third party usually means handing over a long-lived key, or decrypting the data and sending it in the clear. Either way, control ends at the moment of sharing. ANKASecure© replaces both with a capability grant: the counterparty invokes only the operations it was granted, within enforced constraints, every use is recorded in your domain, and every future operation is refused the moment you revoke it. Your counterparty keeps receiving data over the channel you already use, whether SFTP, an API, messaging or an MFT platform.

CISOHead of third-party riskData protection officer

Share the information. Keep the authority.

Is this you

Three ways this lands on your desk

A provider holds your key

Payroll, claims, KYC, card embossing. Somebody outside the company can decrypt the data because that was the only way to let them work on it, and the same key opens every delivery they ever received.

Or you send it in the clear

A CSV over SFTP to a collections BPO, a JSON payload over TLS to a fintech. It arrives readable on their servers, and you have no record of which records were opened, or when.

A relationship ends, or a regulator asks

A contract terminates, a provider has an incident, or a supervisor asks who can decrypt what and how you prove it. With a shared key or a cleartext file, the answer is a project, not a decision.

Who signs this: A CISO or head of third-party risk who owns the provider relationship, and a data protection officer who has to answer for what the provider can see. If revoking a counterparty means re-encrypting data or rebuilding a pipeline, this is the conversation.

Why existing approaches fall short

Each tool solves its own problem. None decides when your data is opened.

Transport protection gets information to the third party safely, and encryption keeps it unreadable in transit and at rest. Neither decides when, under which conditions and how often the third party may open it.

  • Who holds the authority to decrypt?

    Transport protection (SFTP/MFT, APIs over TLS, messaging)
    The third party: it receives cleartext
    Encryption to the third party (PGP, shared keys)
    The third party: it holds the key
    Sovereign exchange with ANKASecure©
    You; the third party only invokes
  • Can access be revoked without the third party’s cooperation?

    Transport protection (SFTP/MFT, APIs over TLS, messaging)
    Only for future deliveries; what was delivered stays readable
    Encryption to the third party (PGP, shared keys)
    No: keys must be replaced on both sides
    Sovereign exchange with ANKASecure©
    Yes, at the next invocation
  • Can use be limited (once, a time window, a cap)?

    Transport protection (SFTP/MFT, APIs over TLS, messaging)
    No
    Encryption to the third party (PGP, shared keys)
    No
    Sovereign exchange with ANKASecure©
    Yes, per grant
  • Is there evidence of use in your domain?

    Transport protection (SFTP/MFT, APIs over TLS, messaging)
    Of the delivery, not of its use
    Encryption to the third party (PGP, shared keys)
    No: decryption happens at the third party
    Sovereign exchange with ANKASecure©
    Yes, signed and with full context
  • Does exposure grow over time?

    Transport protection (SFTP/MFT, APIs over TLS, messaging)
    Yes: cleartext accumulates
    Encryption to the third party (PGP, shared keys)
    Yes: one key opens everything
    Sovereign exchange with ANKASecure©
    No: bounded to what is authorized
  • Can the algorithm change without a bilateral project?

    Transport protection (SFTP/MFT, APIs over TLS, messaging)
    Not applicable: no cryptographic control over the information
    Encryption to the third party (PGP, shared keys)
    No
    Sovereign exchange with ANKASecure©
    Yes, by policy
  • Is the relationship with the third party modeled?

    Transport protection (SFTP/MFT, APIs over TLS, messaging)
    Only as a connection or endpoint
    Encryption to the third party (PGP, shared keys)
    No
    Sovereign exchange with ANKASecure©
    Yes: an exchange context
  • Do you control when and under which conditions cleartext is obtained?

    Transport protection (SFTP/MFT, APIs over TLS, messaging)
    No
    Encryption to the third party (PGP, shared keys)
    No
    Sovereign exchange with ANKASecure©
    Yes: every decryption is an authorized, recorded invocation

You hand over the key once. They open every delivery, forever.

Most third-party exchanges are recurring. When a key is handed over once and reused for every delivery that follows, after a year the provider holds 24 deliveries under the same key, and that key opens every one of them, at any time, as many times as it wants, along with anything else ever encrypted with it. A compromise in month twelve exposes the year, not one delivery.

Traditional third-party exchange: the organization hands its private key to the provider once, on day zero; the same key then opens all 24 deliveries of the year, any time and as many times as the provider wants, and a breach exposes the whole year.

An HSM stores. A proxy transports. A control plane governs.

  • Sovereign key custody

    Traditional HSM / KMS
    Yes
    Encryption libraries and schemes (HPKE, Tink)
    No: the recipient holds the private key
    API gateway / proxy
    No
    ANKASecure©
    Yes
  • Exchange context as a first-class object

    Traditional HSM / KMS
    No
    Encryption libraries and schemes (HPKE, Tink)
    No
    API gateway / proxy
    Partial
    ANKASecure©
    Yes, native
  • Granular usage constraints

    Traditional HSM / KMS
    Limited
    Encryption libraries and schemes (HPKE, Tink)
    No
    API gateway / proxy
    Not cryptographic
    ANKASecure©
    Yes, per invocation
  • Immediate multi-party revocation

    Traditional HSM / KMS
    Partial
    Encryption libraries and schemes (HPKE, Tink)
    No: delivered ciphertext remains decryptable
    API gateway / proxy
    Partial
    ANKASecure©
    Yes, from the plane
  • Evidence with full context

    Traditional HSM / KMS
    Limited
    Encryption libraries and schemes (HPKE, Tink)
    No: decryption occurs at the recipient
    API gateway / proxy
    Traffic only
    ANKASecure©
    Yes, cryptographic and signed
  • Crypto-agility and native PQC

    Traditional HSM / KMS
    Provider-dependent
    Encryption libraries and schemes (HPKE, Tink)
    At library level; coordinated changes on both sides
    API gateway / proxy
    Not applicable
    ANKASecure©
    Yes, by design

How it works

Five building blocks, one governed invocation

The key never moves; the capability does. Every relationship is described with the same five objects, and every invocation is evaluated against all of them before it executes.

  1. Exchange context

    The relationship itself: the counterparty, the purpose, the direction of the exchange and the keys in scope. It has a lifecycle of its own (created, active, suspended, closed) and every transition is audited.

    • counterparty
    • purpose
    • direction
  2. Cryptographic actor

    The workload that actually invokes: the provider’s integration service, authenticated with the token its own OIDC platform already issues, through workload identity federation. No ANKASecure© credential is handed over.

    • workload identity federation
    • OIDC
  3. Capability

    The function granted (encrypt, decrypt, sign or verify), decoupled from the algorithm and the key that perform it, so you can change both behind the grant.

    • encrypt
    • decrypt
    • sign
    • verify
  4. Cryptographic asset

    The key. It stays protected by your HSM or KMS as Root of Trust and is never handed over: the binding grants use, not possession.

    • your HSM or KMS
    • Root of Trust
  5. Constraint policy

    The conditions of the grant, enforced at every invocation: a validity window, a total usage cap, a per-minute rate limit and single use.

    • validFrom / validUntil
    • maxUsage
    • rateLimitPerMinute
    • revokeOnUse

What happens on every invocation

  1. 1 · Authentication

    The invoking workload is identified as a known cryptographic actor.

  2. 2 · Authorization

    It holds a valid grant for this capability, over this key, in this exchange context.

  3. 3 · Constraints

    The validity window, the usage cap, the rate limit and single use are evaluated.

  4. 4 · Mediation

    The operation executes in your domain; the key stays under the protection of your Root of Trust.

  5. 5 · Evidence

    The invocation, its context and its outcome are recorded in a signed, tamper-evident audit trail.

Revocation follows the same path: withdraw a grant, revoke an actor, or suspend or close the exchange context, and the next invocation is refused, without any action by the third party and without re-encrypting data.

Enterprise integration

Keep the exchange you already have

Exchanging with a third party is two jobs. ANKASecure© changes only the second, and it does not sit in the middle of the exchange: your application protects the information before it is sent, and the third party invokes a governed capability when it needs to use it.

Your channels move it. ANKASecure© decides who opens it.

Steps 2 and 3 are the exchange as it works today. Steps 1 and 4 are the only new element: your application calls ANKASecure© to protect the information, and the third party’s application invokes it to decrypt, under your policy. Neither call travels through the channel.

Two planes: the organization’s application protects the data with ANKASecure©, sends it through its existing SFTP/MFT, API, messaging or integration channel unchanged, and the third party invokes ANKASecure© to decrypt it under the owner’s policy; identity, policy, constraints, revocation and evidence sit in the cryptographic control plane, with keys in the owner’s HSM or KMS.
  • Managed file transfer and SFTP

    What it solves (transport plane)
    Reliable delivery of files and batches
    What it leaves open
    The file is decrypted with a key the third party holds, or arrives in cleartext
    What sovereign exchange adds
    The third party opens each delivery by invoking a bounded capability
  • APIs and integration services

    What it solves (transport plane)
    Exchange of payloads and records between systems
    What it leaves open
    The payload arrives in cleartext at the third party’s application
    What sovereign exchange adds
    Protected fields or records, opened per invocation
  • Messaging platforms

    What it solves (transport plane)
    Distribution of events and messages
    What it leaves open
    Consumers read messages in cleartext or with their own keys
    What sovereign exchange adds
    Protected messages whose use is authorized per consumer
  • Direct application integrations (EDI, connectors)

    What it solves (transport plane)
    Point-to-point connectivity
    What it leaves open
    Each integration manages its own keys
    What sovereign exchange adds
    One cryptographic access policy across all of them

Identity

Counterparty workloads authenticate with the OIDC tokens their own identity platform issues, so no shared secret joins the relationship.

Custody

Keys stay protected by your HSM, cloud KMS or PKCS#11 environment. Execution happens in ANKASecure© or in your HSM or KMS, depending on the operation; the Root of Trust stays yours.

Evidence

Every invocation lands in a signed audit trail that forwards to your SIEM with the signature intact.

Information is not only files: records, JSON or XML payloads, messages and transactions follow the same model. Each third party adapts its integration once to invoke the capability; after that, key rotation and algorithm changes require no further change on either side.

In practice

Sovereign exchange in practice

Four banking scenarios, one per exchange channel. In every one, the existing channel stays in place.

Channel: Batch files

Several embossing providers, one bank

Today

The bank shares a key with each provider, or sends decrypted files. Every provider holds the bank’s cryptographic authority, and a compromise at any one of them exposes the material for all.

With ANKASecure©

One exchange context per provider, each with its own actor and grant. Each batch is protected under its own key, and each provider decrypts only its batch, once, within its window. Providers are isolated from one another, and the bank can cut any of them without coordinating anything.

How it is configured

Exchange context
Embossing: Network A
Actor
network-a-embossing-actor
Capability
decrypt, over the key of its own batch
Constraints
single use · 2-hour window

Beyond banking

Financial services
Card issuance · Collections BPO · Recurring outsourced processing · Regulatory reporting · Embedded fintechs · Open banking
Government and defense
Inter-agency exchange · Contractors · Binational interoperability · Sovereign signing
Healthcare
Shared clinical records · External laboratories · Insurers · Clinical research
Telecommunications
Partner data sharing · Roaming · MVNOs · CDR exchange · IPX interconnection
Retail and value chains
EDI with suppliers · Federated loyalty · Outsourced logistics · Marketplaces
Software and SaaS
Multi-tenancy · B2B integrations · Data processors · BYOK for enterprise clients

Crypto-agility

One capability, any key, any algorithm

Because the third party invokes a capability rather than holding a key, the key and the algorithm behind it are your lifecycle decisions. A new key every month or a new algorithm every quarter happens in your domain; the third party keeps making the same call and cannot know which key or algorithm fulfils it. Your applications do not change either.

The key never leaves your domain. Rotating it changes nothing.

Twelve keys, four algorithms and no line of code changed after the initial integration, on either side. Each delivery is decrypted once, within 48 hours, and a delivery already decrypted cannot be opened again: if the provider is breached, there is no key to steal.

With cryptographic sovereignty: over one year, twelve keys and four algorithms (RSA-3072, ECDH P-384, hybrid PQC, ML-KEM-768) set by policy in the owner’s domain, while the third party makes the same decrypt call all year and holds no key.

This is a problem of today, not of the quantum era: a key handed to a provider is just as exposed with RSA as with ML-KEM, so it can be solved now, with the algorithms and HSMs already in place. Post-quantum readiness across your external relationships then follows as a consequence: a migration that would be a bilateral project with every counterparty becomes a policy change.

Crypto-agility →Post-quantum migration →

Every exchange, with its risk and its evidence

One application in a demo bank, its counterparties, and the sensitivity of every flow between them. Selecting an application names each exchange context — the PSD2 token issuance, the consent revocation — and who is on the other end of it.

ANKASecure© · Cryptographic exchange topology
The ANKASecure© cryptographic exchange topology: a demo bank’s applications on the left, its counterparties on the right, 65 exchanges coloured by sensitivity, and a panel listing the exchange contexts of the selected application.
Real deployment · non-production data. The applications and counterparties are the demo bank’s own, not ANKATech’s.

Fifteen minutes

What you will actually watch

Live, on a real deployment, with a counterparty of the kind you have. Nothing in this list is a mock-up or a roadmap item.

  1. An exchange context for a provider: counterparty, type, the keys in scope.

  2. A grant with its constraints: decrypt only, one key set, a two-week window, a usage cap.

  3. The provider decrypts within scope. Then asks for an operation outside it, and is refused with the reason.

  4. The grant is revoked. The very next call from the same workload is refused. Nothing was re-encrypted.

  5. The audit trail: every use, the constraint decision, the revocation — signed, in a chain that would show any edit.

  6. Your provider contract, discussed on the deployment rather than on a slide.

Business value

What changes for each person who signs

-70%

Onboarding time

An exchange context is defined, instead of a key exchanged and a pipeline built.

0

Keys shared

With providers, BPOs or external integrations: key exposure is eliminated, not reduced.

< 1 min

Effective revocation

On an incident, without coordinating with the third party and without re-encrypting data.

100%

Auditable evidence

Of every cryptographic operation, with full context, generated in your domain.

CEO and board

  • Structural reduction of third-party risk
  • A defensive posture against litigation and sanctions
  • An enabler of new commercial integrations
  • A differentiator with regulated clients

CISO

  • Cryptographic sovereignty that is real, not declarative
  • Attack surface from third parties bounded to the authorized scope
  • Complete evidence for audits and forensics
  • Instant revocation, without external coordination or re-encryption

CIO and CTO

  • One control plane for every third party
  • Keys rotated and algorithms migrated without touching applications or counterparties
  • Post-quantum readiness built in
  • Standard integration with your HSMs and the rest of your stack

Regulatory alignment

Built around the principle regulators share

Sovereign exchange is not designed around any single regulation, but around the principle they share: the data owner remains responsible for how third parties use its data, and must be able to demonstrate control. Implemented architecturally, alignment with each framework follows.

  • DORA

    Scope
    Digital Operational Resilience Act · EU
    What sovereign exchange provides
    ICT third-party risk management with evidence of controls over every provider that processes protected data.
  • PCI-DSS 4.0

    Scope
    Card industry · global
    What sovereign exchange provides
    Key custody and segregation; demonstrable control over service providers that handle cardholder data.
  • SOX

    Scope
    Sarbanes-Oxley · USA
    What sovereign exchange provides
    Controls over financial systems, with full traceability of who accessed protected information and under what authorization.
  • GDPR and national equivalents

    Scope
    Data protection · EU and other jurisdictions
    What sovereign exchange provides
    The controller’s responsibility over processors, supported by evidence produced in the controller’s own domain.
  • SAMA Circular 482021280

    Scope
    Saudi Central Bank · financial institutions in Saudi Arabia
    What sovereign exchange provides
    Its cryptographic-asset inventory asks institutions to identify their dependencies on third parties; counterparties that hold no keys remove a whole class of them.
  • CNSA 2.0

    Scope
    Post-quantum · USA (NSA)
    What sovereign exchange provides
    Transition to quantum-resistant algorithms without renegotiating cryptographic material with each counterparty.

Evidence

Most frameworks ask the owner to demonstrate control, not merely to assert it. Evidence generated by your infrastructure for every cryptographic operation is qualitatively different from a contractual attestation.

Revocability

Third-party risk frameworks expect you to be able to terminate access when a provider is compromised or a relationship ends. Here it is a structural property, not a procedure that depends on the counterparty.

Dependency

Supervisors have begun to ask explicitly about third-party dependencies in cryptography. The Saudi Central Bank’s circular on quantum computing risks, in force since August 2026, requires institutions to identify them for their priority cryptographic assets.

What it rests on

The capabilities underneath, with their state

  • Shipping

    Exchange contexts and counterparty types

    The relationship as an entity with its own lifecycle — created, active, suspended, closed — every transition audited.

  • Shipping

    Capability grants and constraint policies

    Operation and key scope, plus four enforced constraints: time window, usage cap, rate limit, single use.

  • Shipping

    Workload identity federation

    A counterparty workload authenticates with the token its own OIDC platform issues; no ANKASecure© credential is handed over.

  • Shipping

    Immediate revocation

    A revoked grant, a suspended exchange or a deleted application stops authorizing on the next call, with no re-encryption.

  • Shipping

    Signed audit trail

    Every use recorded with its grant and constraint decision, tamper-evident, forwardable to your SIEM with the signature preserved.

  • Shipping

    Role model

    Platform, tenant and operator authority kept apart, so the person who grants is not the person who operates.

All of the platform →

The framework

Where this sits in CAPA

The Cryptographic Control Plane reference architecture describes each pillar through the scenarios it must handle and one practical test. One of the sovereignty pillar’s scenarios is this solution, word for word.

02

Primary pillar

Cryptographic Sovereignty

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?”

04

Primary pillar

Cryptographic Governance & Compliance

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?”

05

Supporting pillar

Enterprise Readiness

Scenario realised

Interoperating with external cryptographic ecosystems

Practical test

“Can the control plane be adopted without replacing the identity, KMS/HSM, PKI, or monitoring platforms already in place?”

L3L4–L5

Maturity move

A control plane has to be in place first. On top of it, governing counterparties by grant rather than by key is what the reference architecture calls agile operations and full governance: the authority you extend outward is as revocable as the one you keep inside.

The six maturity levels →Reference architecture: cryptographiccontrolplane.org

What this does not do

  • It is not a file-transfer product. It does not replace SFTP, your APIs, your messaging or your MFT platform; it governs the cryptographic operations behind them.

  • It does not remove integration. Your application protects the information before it is sent, and each third party adapts its integration once to invoke the capability instead of decrypting with a key of its own.

  • It does not protect data you send to the counterparty in the clear, and it does not reach what the counterparty has already decrypted: that remains under the contractual and data-protection obligations of the relationship.

  • It does not manage the counterparty’s own systems. It decides what they may do with your keys; it does not see what they do afterwards with the result.

  • 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.

Adoption path

It starts from a list you already have

Not a cryptographic inventory and not a post-quantum roadmap: the list of your third parties. Procurement, risk and security teams already know which counterparties receive keys or files today. Adoption goes one exchange context at a time, with the algorithms and HSMs already in place.

  1. 1 · 2–4 weeks

    Discovery

    An inventory of third-party exchanges, not of the whole cryptographic estate, and the most acute case for the pilot: the highest risk, the most regulatory pressure, or the most frequent need to revoke.

  2. 2 · 6–8 weeks

    Pilot

    One exchange context in production, keys anchored in your existing HSM, evidence flowing to your audit infrastructure.

  3. 3 · 3–6 months

    Expansion

    The remaining third parties, onboarded progressively and integrated with your HSM or KMS and identity provider; per-context policies replace per-counterparty key exchanges.

  4. 4 · 6–12 months

    Platform

    The control plane governs all the cryptography in your exchanges, with key rotation and post-quantum migration by policy across every external relationship.

Getting started

  1. A technical discovery session that maps your critical third-party exchanges and the most pressing one.
  2. A demonstration and reference architecture on a case analogous to yours.
  3. A scoped pilot plan: one exchange context, six to eight weeks, keys anchored in your existing HSM.

Whitepaper

Cryptographic sovereignty in third-party information exchange

Why control ends at the moment of sharing, the three properties and five building blocks of sovereign exchange, four banking scenarios, regulatory alignment, business value and an adoption path. 38 pages, October 2026.

Read it online →

Download the PDF

Complete your details to download it

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.

Personal mailboxes (gmail, hotmail, outlook, yahoo, proton, icloud, aol) are not accepted.

Your personal profile URL, in the form linkedin.com/in/your-name. Company pages are not accepted.

We use your details to share related ANKATech content and to route follow-up. You can ask us to remove them at any time.

This site is protected by reCAPTCHA.

Bring the provider contract.

The one where they hold your key. Fifteen minutes on a live deployment to replace the key with a permission you can revoke.

Book the demo