Every TLS connection, signed release, workload certificate and post-quantum migration plan depends on a small number of people who understand cryptography and public key infrastructure well enough to run it safely. This guide covers two related careers: the PKI engineer, who designs and operates certificate authorities and certificate lifecycles, and the applied cryptographer or cryptography engineer, who selects, implements and reviews cryptographic mechanisms. It sets out what each does, the skills and tools, routes in, credentials that help and how the work progresses. It is written for engineers in identity, infrastructure or development who are drawn to the field, and for managers hiring their first PKI specialist. Facts on standards and credentials were checked on official pages on 27 October 2026. It does not give salary figures.
Key takeaways
- Two roles, one discipline. PKI engineers run trust infrastructure; cryptography engineers choose and implement the mechanisms; research cryptographers design and break them, usually in academia or specialist labs.
- Certificate lifetimes are shrinking fast. The CA/Browser Forum Baseline Requirements cut the maximum public TLS certificate validity to 200 days from 15 March 2026, 100 days from 15 March 2027 and 47 days from 15 March 2029, which makes automation skills central.
- Post-quantum migration is a multi-year workload. NIST approved FIPS 203, 204 and 205 in August 2024, and inventory, crypto-agility and migration planning now fill PKI roadmaps.
- Machine identity is most of the job. Certificates for servers, workloads, devices and code signing are non-human identities, and their sprawl drives demand for this skill set.
- No single certification defines the field. Employers look for demonstrable PKI operations, standards knowledge and secure engineering practice; broad credentials such as CISSP cover cryptography only as one domain.
What the role does
Neither the ENISA European Cybersecurity Skills Framework nor the NIST NICE Framework has a dedicated cryptographer or PKI engineer role. NICE (version 2.2.0 components) instead has a Cryptography competency area, NF-COM-006, describing a learner's capability to transform data using cryptographic processes so that only authorised people can read it. In practice, organisations hire under the titles below.
| Role | Main focus | Typical deliverables | Where it sits |
|---|---|---|---|
| PKI engineer | Design, build and operate certificate authorities, enrolment and revocation | CA hierarchy design, certificate policy (CP) and certification practice statement (CPS), key ceremony scripts, automated issuance | Identity, infrastructure or security engineering |
| Certificate lifecycle or machine identity engineer | Discover, issue, renew and revoke certificates at scale | Certificate inventory, ACME and EST integrations, expiry monitoring, renewal automation | Platform engineering or identity |
| Cryptography engineer (applied cryptographer) | Choose algorithms and protocols, implement or review cryptographic code, set organisational crypto standards | Cryptographic standards, design reviews, library choices, PQC migration plans, CBOM | Product security, platform security or central architecture |
| HSM and key management engineer | Operate hardware security modules and key management services | HSM clusters, key hierarchies, backup and recovery procedures, access control for key custodians | Infrastructure security, payments, cloud |
| Research cryptographer | Design and analyse algorithms and protocols | Papers, proofs, cryptanalysis, standards contributions | Universities, research labs, government, a few large technology firms |
A week in PKI operations
- Issuance and renewal: keeping automated enrolment working (ACME for web servers, EST or SCEP for devices, platform integrations for workloads) and chasing certificates that fall outside automation.
- Trust management: distributing root and intermediate certificates, retiring old ones, and handling the outages caused when a chain changes.
- Revocation and incident work: revoking compromised certificates, keeping CRL and OCSP services healthy, and responding to mis-issuance.
- Ceremonies: running key generation and signing ceremonies for offline roots. The CA/Browser Forum Baseline Requirements (version 2.3.1) require CA key pairs to be generated by personnel in Trusted Roles under multiple person control and split knowledge, inside suitable cryptographic modules, with the activity logged; CA private keys may be backed up and recovered only by Trusted Role personnel under at least dual control.
- Governance: maintaining the CP and CPS, preparing for audits, and reviewing requests for new certificate profiles.
See the Enterprise PKI Design and CA Hierarchy Guide and the Machine Identity, PKI and Certificate Lifecycle Guide for the technical depth behind these tasks.
Core skills and tools
| Skill area | What to know | Key references |
|---|---|---|
| X.509 and PKI standards | Certificate and CRL profiles, extensions, path validation, name constraints, revocation | RFC 5280 (Proposed Standard, May 2008, updated by later RFCs including RFC 6818 and RFC 9549) |
| Public trust rules | Baseline Requirements for publicly trusted TLS certificates: validation, validity limits, key generation, audits | CA/Browser Forum Baseline Requirements |
| Enrolment automation | ACME, EST and SCEP; integration with load balancers, Kubernetes and service meshes | See the ACME and Automated Certificate Management Guide |
| Enterprise CA platforms | Microsoft Active Directory Certificate Services templates and their abuse paths, cloud private CAs, open source CAs | See the AD CS Security Guide |
| Key protection | HSM operation, FIPS 140-3 validated modules, key custodian roles, backup and recovery | NIST CMVP (with the Canadian Centre for Cyber Security), FIPS 140-3 |
| Applied cryptography | Symmetric and asymmetric primitives, authenticated encryption, key derivation, randomness, protocol design pitfalls | See the Cryptographic Protocol Failures and Misuse Guide |
| Post-quantum cryptography | ML-KEM (FIPS 203), ML-DSA (FIPS 204), SLH-DSA (FIPS 205), hybrid deployment, crypto inventory and agility | NIST IR 8547 (Initial Public Draft, November 2024) on the transition |
| Programming and automation | Scripting (Python, PowerShell, Go), infrastructure as code, using cryptographic libraries correctly, reading OpenSSL output | Your own lab and code |
| Governance and audit | Writing CP and CPS documents, trusted roles, separation of duties, audit evidence | See the ISO/IEC 27099 PKI Practices and Policy Framework Guide |
Where identity fits
Most certificates an enterprise PKI issues authenticate machines rather than people: web servers, workloads talking over mTLS, devices, and code signing keys. That makes the PKI engineer one of the main operators of non-human identity, with the same problems of ownership, sprawl and stale credentials. Code signing shows the stakes: in the NVIDIA code-signing certificate theft, leaked certificates that had already expired were still accepted by Windows for driver signing and were used to sign malware within days. See the Code Signing Security Guide and the SPIFFE and SPIRE Guide for workload identity patterns.
Routes into the role
- Windows or identity administrator to PKI engineer: many PKI engineers start by inheriting an AD CS deployment. Learning templates, enrolment and the known misconfiguration classes properly is a direct route.
- Infrastructure or platform engineer to certificate lifecycle engineer: engineers who automate TLS for load balancers, Kubernetes ingress or service meshes build the core skill set for machine identity work.
- Software engineer to cryptography engineer: developers who work on security libraries, authentication systems or payment software move into applied cryptography, often via design reviews and fixing cryptographic misuse.
- Academic route: a mathematics or computer science degree, often a master's or doctorate in cryptography, leads to research roles and to senior applied roles in specialist teams.
- Payments and HSM route: key custodians and HSM operators in banking and payments move into wider key management and PKI roles.
What to do first: build a two-tier lab PKI (offline root, issuing CA), issue certificates through ACME to a test web server and an mTLS client, revoke one, publish a CRL, and write a one-page CPS for it. Then break it on purpose: let a certificate expire, change an intermediate, and observe what fails. This lab teaches more than any course, and it is a portfolio item hiring managers can discuss with you.
Choosing between PKI and cryptography engineering
- Choose PKI engineering if you enjoy operations, automation and governance, and want broad demand across almost every organisation with internal certificates.
- Choose cryptography engineering if you prefer code, protocol design and reviews, and are comfortable reading standards and papers closely. Fewer roles exist, concentrated in technology, finance and government.
- Small organisations rarely hire either full time; the work sits with an identity or infrastructure engineer, often supported by a managed PKI. Large organisations run dedicated PKI teams and sometimes a central cryptography function that sets standards.
Certifications that help
There is no widely recognised vendor-neutral certification that defines PKI engineering. The credentials below help in different ways; details are from the issuing bodies' own pages.
| Credential or evidence | What it shows | Notes |
|---|---|---|
| ISC2 CISSP | Broad security management knowledge, including cryptography | Exam outline effective 15 April 2024; Domain 3 Security Architecture and Engineering covers selecting cryptographic solutions, including PKI, and cryptanalytic attacks. See the CISSP Certification Guide |
| Cloud provider security certifications | Operating cloud KMS, HSM and private CA services | See the AWS Certified Security Specialty Guide |
| Vendor product training | Competence on a specific CA, HSM or certificate lifecycle platform | Useful when an employer runs that product; less portable |
| Postgraduate study in cryptography | Depth for research and senior cryptography engineering | Expected for research cryptographer roles |
| Public evidence | Practical ability | Open source contributions to cryptographic or PKI tooling, conference talks, published lab write-ups, standards mailing list contributions |
For a wider view of credentials, see the Identity Certifications Guide and the Cybersecurity Certifications Guide.
Progression
| Stage | Typical titles | Scope |
|---|---|---|
| Entry | PKI administrator, certificate operations analyst | Process requests, renew certificates, monitor expiry, follow runbooks |
| Established | PKI engineer, machine identity engineer, cryptography engineer | Design certificate profiles, automate enrolment, run ceremonies, review cryptographic designs |
| Senior | Senior or lead PKI engineer, principal cryptography engineer | Own the CA hierarchy and CP/CPS, set crypto standards, lead PQC migration planning, act as audit point of contact |
| Leadership | Head of PKI, head of cryptography, identity or security architect | Strategy for trust infrastructure, crypto-agility programme, budget and vendor decisions |
Common next moves are identity architecture, security architecture and product security. The IAM Engineer Career Guide covers the adjacent identity path.
Measuring yourself in the role
- Share of certificates issued and renewed automatically, and outages caused by expiry (target: none).
- Coverage of the certificate and cryptographic inventory against discovered endpoints.
- Time to revoke and replace a compromised certificate or intermediate.
- Progress of post-quantum readiness: systems inventoried, algorithms identified, migration paths agreed. See the Post-Quantum Cryptography Migration Guide.
- Audit findings on trusted roles, ceremonies and key protection.
Common pitfalls
- Treating PKI as set and forget: the shrinking public validity periods mean manual renewal no longer scales.
- Weak ceremony discipline: roots generated by one person without scripts or witnesses cannot be trusted or audited.
- Rolling your own cryptography: cryptography engineers add most value by using well-reviewed libraries correctly, not by inventing schemes.
- Ignoring machine identity ownership: certificates with no owner are the ones that expire unnoticed or survive compromise.
Practitioner checklist
- Read RFC 5280 path validation and the CA/Browser Forum Baseline Requirements sections on key generation and validity.
- Build a two-tier lab PKI with ACME issuance, revocation and a short CPS.
- Learn one enterprise CA platform in depth, including its common misconfigurations.
- Operate an HSM or cloud HSM in a lab and document a backup and recovery procedure with dual control.
- Study ML-KEM, ML-DSA and SLH-DSA and try them in a test TLS or signing setup.
- Build a certificate inventory script for your own environment and track expiry.
- Decide between PKI operations and cryptography engineering and pick the credentials and evidence for that path.
- Publish one write-up or open source contribution that shows your work.
Standards and references
- CA/Browser Forum: Baseline Requirements for TLS Server Certificates
- IETF: RFC 5280 Internet X.509 PKI Certificate and CRL Profile
- NIST: Post-Quantum Cryptography FIPS 203, 204 and 205 Approved
- NIST: IR 8547 Transition to Post-Quantum Cryptography Standards
- NIST: Cryptographic Module Validation Program
- NIST: NICE Framework components v2.2.0
- ISC2: CISSP Certification Exam Outline
Related NHI Mgmt Group resources: Cybersecurity Careers Guide · PKI Basics Guide · Machine Identity, PKI and Certificate Lifecycle Guide · Crypto-Agility Guide · IAM Engineer Career Guide