
Cryptographic Controls Policy Writers
What are Cryptographic Controls Policies?
Cryptographic controls policies define how encryption and related technologies are used to protect sensitive data, systems and communications across an organisation’s digital infrastructure.
These policies help ensure that encryption is applied consistently and effectively, supporting compliance with legal, regulatory and contractual obligations, including those under the UK GDPR and ISO 27001.
What Do Cryptographic Controls Policies Cover?
A cryptographic controls policy typically includes:
-
When and where encryption must be used (e.g. data in transit, data at rest)
-
Approved encryption algorithms, key lengths and protocols
-
Management of encryption keys including generation, storage, rotation and disposal
-
Secure email, file transfers and remote access using encryption
-
Use of digital certificates and signatures
-
Roles and responsibilities for implementing cryptographic tools
-
Links to IT security, communications security and access control policies
A clear policy ensures encryption is applied in a way that protects data integrity and confidentiality without disrupting day-to-day operations.
It also provides assurance to clients, partners and auditors that sensitive information is safeguarded using recognised security standards and techniques.
Effective cryptographic controls can protect against threats such as unauthorised access, data interception, tampering and identity fraud, especially in cloud-based or hybrid working environments.
By embedding encryption into systems and procedures, businesses can reduce risk, support regulatory compliance and uphold the trust of their users and stakeholders.
requirements, and operational style.
Policy and Procedure Development
Creation of clear, practical policies that reflect current legislation, best practice, and your organisation’s values.
Review and Gap Analysis
A thorough review of your existing policies to identify areas for improvement and ensure they remain compliant and effective.
Tailored Solutions
All documents are written in accessible language and adapted to suit your company’s size, culture, and ways of working.
Implementation Support
Guidance to help you introduce and embed policies across your organisation so they are understood and applied confidently by all staff.
Standards
Cryptographic controls are a foundational ISO 27001:2022 control (A.8.24 use of cryptography, A.8.26 secure coding intersect). The NCSC Cryptographic Guidance sets practical expectations on algorithm selection, key length and key management.
PCI DSS v4.0 has prescriptive requirements for card-handling environments. UK GDPR Article 32 explicitly mentions encryption as an example of an appropriate technical measure.
Common Compliance Pitfalls
- Algorithms past their NCSC-recommended lifetime (TLS 1.0/1.1, SHA-1, RC4) still in use.
- Self-signed certificates in production with no rotation plan.
- Key management bundled with the encrypted data, defeating the protection.
- End-of-life certificates triggering service outage rather than scheduled renewal.
- Encryption-at-rest claims that do not hold up to scrutiny (database encryption only, not the underlying disk).
What Policy Pros Delivers
Our Cryptographic Controls Policy package includes the main policy aligned to NCSC guidance and ISO 27001:2022, an approved-algorithms register with lifecycle dates, a key management procedure with separation of duties, a certificate management procedure with renewal automation, and integration with the access control and information transfer policies.
PCI DSS v4.0 add-on available for card-handling environments.
Frequently Asked Questions
Is TLS 1.2 still acceptable?
Yes for most use cases as a minimum. NCSC and PCI DSS expect TLS 1.2 minimum, with TLS 1.3 preferred. TLS 1.0 and 1.1 should be disabled.
Where should encryption keys be stored?
Separately from the data they protect. A hardware security module (HSM) or managed cloud key management service (KMS) is the typical choice. Storing keys with the data defeats the protection.
Do we need post-quantum cryptography now?
NCSC has begun publishing migration guidance and recommends starting an inventory of cryptography in use, particularly long-lived data and signatures. Active migration to post-quantum algorithms is generally not yet required for typical UK businesses.