Skip to content

Experience Center

What this screen is for

The Experience Center lets you see for yourself what ANKASecure© does, on prepared data, in your own console, in a few minutes per experience. It offers five experiences, in any order: Crypto-Agility, Cryptographic Sovereignty, Frictionless Migration, Policy-Driven Governance and Enterprise Readiness. Start anywhere, and leave and come back whenever you like.

Each experience is run on the screens the console already has: the Cryptographic Playground, Key Inventory, Exchange Topology, Capability Grants, Catalogs, Policies, the Dashboard and Settings › Integrations. The Experience Center only orients you and links those screens. It never simulates an operation, never grants a permission, and records a milestone only when the platform has confirmed the outcome.

What must exist first

  • A deployment your organization operates. The Experience Center is not offered on ANKASecure© SaaS, and not to API Marketplace tenants. Where it is not offered, the screen says so and links back to your dashboard.
  • A tenant administrator, key manager or platform super administrator working in a tenant.
  • For Crypto-Agility, Cryptographic Sovereignty and Frictionless Migration, the Cryptographic Playground: they run real operations there. A role the Playground is not offered sees those three marked as unavailable to it.
  • The prepared data each experience runs on: keys, Exchanges and grants. The experiences do not create them.

Decisions you make here

Choosing where to start

Each experience card shows its status: Not started, In progress or Experienced, plus Revisited once you run an experienced one again. It also shows its evidence: the milestones recorded so far, each with an Audit trace link to the correlation trace of the operation behind it, where that operation has one.

Crypto-Agility is marked Recommended first. What brings you here? is optional: your answer only orders the experiences for you, and the best match for it is marked Best match. Choose from Preparing for post-quantum, Encrypted data we must modernize, Partners or providers use our cryptography, Compliance, audit and regulation or Fitting it into our stack (KMS, SIEM, identity).

Each card offers Start, Continue, Revisit or Restart, as its status allows, and Explore freely, which opens the experience's first screen without starting the guide; the Explore freely at the top of the screen opens your dashboard. Restart clears that experience's milestones and starts the guide again from its first step; the other experiences keep their progress.

What each experience proves

  • Crypto-Agility: same Key ID, a different algorithm, and no application changes. You encrypt with the key's RSA version, rotate the key to ML-KEM-768 (the rotation wizard opens with it preselected, and nothing rotates until you confirm), encrypt again with the identical request, and compare both runs. The rotation does not rewrite earlier ciphertext, which stays decryptable because a retired version still decrypts. An optional signature variant goes from RSA-PSS to ML-DSA-65.
  • Cryptographic Sovereignty: partners use your cryptography under your rules, and never hold your keys. You see the partner's relationship on Exchange Topology, read the partner's capability grant (who may act, what they may do, on which key and under which limits), and run the partner's operation as the partner's Actor. A KMS you bring is the root of trust that protects your keys, not the store of every key.
  • Frictionless Migration: one action runs the Playground's migration test. Ciphertext A, made with Key ID 1 (RSA), is re-encrypted into ciphertext B under Key ID 2 (ML-KEM) without being decrypted, and B is decrypted. The recovered text must match the original byte for byte. B has one recipient, the ML-KEM key: the data was moved, not encrypted twice, and ML-KEM protects the content key (envelope encryption).
  • Policy-Driven Governance: you note how many algorithms your tenant may use and how many of your keys conform, apply the US_NSA_CNSA (CNSA 2.0) template on Algorithm Availability, then compare the permitted catalogue and the Dashboard. The figures are the ones your screens read before and after, never fixed numbers. A key that does not conform keeps working: the policy tells you which keys to remediate.
  • Why CNSA 2.0: it keeps AES-256, admits ML-KEM-1024 and ML-DSA-87, and retires RSA, ECC and lower-level post-quantum parameters. The broader POST_QUANTUM template is not used because it also retires AES. Applying the template changes your tenant's policy for every user of the tenant.
  • Enterprise Readiness: you open any integration and see whether it is supported, configured, in effect and verified, where it comes from (the deployment default, your own, or managed by the deployment), and what your role may change. Opening the form to use your own service saves nothing until you choose to.

Each experience opens with Why this matters and What you will see, and ends on What you just proved. Do this from your code links the screen that shows the run's HTTP exchange and its cURL. Your application sends the same request with its own Actor's credential: you mint one on the Actor, where it is shown once. The Experience Center never displays a secret.

Following the guide

Starting or continuing an experience opens the Experience guide, a panel on every screen while the experience is active and hidden on the Experience Center itself. It shows Step n of m, what to do there, and Open the screen for this step. It never blocks a menu or a form. Back and Next move freely, you may navigate anywhere and the guide follows you, and a step completes only when its milestone is recorded, never because you visited a page. Minimize the guide folds it away; Close the guide keeps your progress.

Where your progress is kept

Your progress is saved in this tenant, for you, and kept until your membership or the tenant ends. This deployment's platform administrators can see each member's progress on their Experience progress screen.

It stores no payload, plaintext, ciphertext, key, token or credential: only which milestones you reached and when, the correlation identifier of the operation behind each one, the figures Policy-Driven Governance read, your answer to What brings you here?, when you first started and when you were last active, and three counts: the Do this from your code links you opened, the screens you opened from the guide, and the API documentation you opened from an experience.

An experience's status is worked out from the milestones it requires. Where the guide stands is kept in this browser, and only that is cleared when you sign out.

In a support-access session, and in the System context, nothing is saved for you in the tenant: your progress is kept in this browser, for you only, while you work in this tenant. It is cleared when you sign out. Nobody else sees it, and it stores no payload, plaintext, ciphertext, key, token or credential: only which milestones you reached and when, the correlation identifier of the operation behind each one, the figures Policy-Driven Governance read, your answer to What brings you here? and where the guide stands.

Presenter mode

A platform super administrator sees Presenter mode on the Experience Center, for showing the platform to an audience. It is kept on this browser only and offers:

  • Preflight: whether each experience is ready to run here, or why not: it needs the Cryptographic Playground, which this session is not offered, or an Exchange with a partner, which a SIMPLE tenant does not have (it has Internal Use Cases only). The prepared keys, the partner and the integrations are not checked: open each experience's first screen to confirm them before the audience arrives.
  • Talking points in the guide, one per step.
  • Reset for the next audience: every experience returns to Not started for you, the answer to What brings you here? is cleared and the guide closes. Only your own experience progress is cleared, wherever it is kept: other users' progress, keys, policies and audit records stay as they are. The confirmation says how many of your experiences hold progress. A key rotated during a session stays rotated, and an applied template stays applied.

What you can verify afterwards

  • Every milestone that carries a correlation identifier opens its Audit trace: the correlation trace of that operation, which records a Playground run as run by you as the configuration's Actor.
  • Keys and policies show what each experience changed, on their own screens. Only Crypto-Agility's rotation and Policy-Driven Governance's template change your tenant's configuration, and only when you confirm them. Every Playground run is a real operation that leaves its audit record.