IA-7 Cryptographic module authentication
Requires authentication to a cryptographic module to be implemented by mechanisms that satisfy the laws, directives, policies, regulations, standards and guidelines that apply to authentication for such modules.
4
artefacts
1
held by a system
0
at each review
moderate
to go live
Identity provider / directory
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Configuration showing role based authentication to the module is enforced · Identity provider / directory
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Inventory of cryptographic modules in use and their validation status · Policy repository / GRC workspace
- Documented authentication requirements applicable to those modules · Policy repository / GRC workspace
- Vendor certification or validation certificate references · Policy repository / GRC workspace
First move
Start with the 1 of 4 artefacts that already live in a system (Identity provider / directory); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Cryptographic module operating in a non-validated mode
- Administrative access to key management platforms without the required authentication strength
- Applicable requirements never identified, so compliance cannot be demonstrated
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetIA-6 Authentication feedback · IA-8 Identification and authentication of non-organizational users