PQC concepts
What is Cryptographic agility?
Also known as Crypto-agility.
The architectural property that lets an organisation swap one cryptographic algorithm for another without changing application code or data-at-rest formats. QNSI crypto-policy tiers + KMS algorithm parameter implement this directly - application code calls `kms.encrypt(key)` and the policy decides which algorithm runs.
Decision context
Why Cryptographic agility matters
Cryptographic agility reduces the cost and risk of algorithm transition by separating application intent from primitive, parameter, provider and key-lifecycle decisions. It is operational only when inventory, policy, compatibility, migration, rollback and evidence mechanisms work across deployed systems.
How to evaluate Cryptographic agility
Demonstrate a controlled algorithm or provider change on a representative workload without application rewrites or data loss. Verify policy enforcement, downgrade resistance, dual-read or overlap windows, rollback, historical decryption, audit records and dependency ownership. A configurable string is not crypto-agility.
PQC concepts
PQC concepts evidence boundary
Post-quantum programmes combine cryptography, architecture, data lifetime, operational ownership, and migration governance. A concept is useful only when it changes a concrete inventory, policy, design, test, or evidence decision. Treat terminology as a decision aid rather than proof that a control exists.
FAQ
Common questions
What is Cryptographic agility?
The architectural property that lets an organisation swap one cryptographic algorithm for another without changing application code or data-at-rest formats. QNSI crypto-policy tiers + KMS algorithm parameter implement this directly - application code calls `kms.encrypt(key)` and the policy decides which algorithm runs.
Why does Cryptographic agility matter?
Cryptographic agility reduces the cost and risk of algorithm transition by separating application intent from primitive, parameter, provider and key-lifecycle decisions. It is operational only when inventory, policy, compatibility, migration, rollback and evidence mechanisms work across deployed systems.
How should Cryptographic agility be evaluated?
Demonstrate a controlled algorithm or provider change on a representative workload without application rewrites or data loss. Verify policy enforcement, downgrade resistance, dual-read or overlap windows, rollback, historical decryption, audit records and dependency ownership. A configurable string is not crypto-agility.
What is Cryptographic agility also known as?
Cryptographic agility is also known as Crypto-agility. The architectural property that lets an organisation swap one cryptographic algorithm for another without changing application code or data-at-rest formats. QNSI crypto-policy tiers + KMS algorithm parameter implement this directly - application code calls `kms.encrypt(key)` and the policy decides which algorithm runs.
More