Certificate management policy
How certificates are requested, issued, inventoried, renewed before expiry and revoked, and which authorities are trusted.
How the register reads it
| Also called | PKI policy, TLS certificate management |
|---|---|
| Family | Operations and technology |
| Document type | Policy. The regimes ask for the content, not the label; a line pasted as a standard, procedure, plan or schedule is placed here with the label noted. |
| Folds into | The regimes accept it folded into the cryptography policy; when neither is listed, the gap is counted once, under the parent. |
| Expected owner | The head of IT operations. |
| Review cadence | Annual (the register's default: the clauses say planned intervals and on significant change, and do not fix a period). |
| On the gap list when | never on its own: the register recognises it and names the clauses, but no ticked regime lists it as a separate document (its parent, cryptography policy, is). |
| Template | Certificate management policy. |
Which standards require it, and what each expects it to contain
1 requiring clauses, 1 regimesShown on a register for the regimes you tick; with none ticked, ISO 27001 is applied. Requirement text drawn from a human-verified compliance corpus under licence: the corpus statement of each clause, not the instrument verbatim.
ISO/IEC 27001:2022
ISO 27001 8.24 Use of cryptographyDefine and implement rules for effective use of cryptography and key management.
What the ISO 27002 guidance expects the document to say: Requires defined and implemented rules on using cryptography effectively, including how cryptographic keys are managed.
Common gap: Missing documented key lifecycle
Source: ISO/IEC 27001:2022; guidance ISO/IEC 27002:2022
Do this for every document on your list
Paste the list and get this reading for every document at once, with the owner and cadence against each, the clauses quoted, and the documents the regimes expect that the list does not carry. Eight documents free, no account.
Build a register