EvidenceSheet

SC-17 Public key infrastructure certificates

Requires public key certificates to be issued under an organization-defined certificate policy or obtained from an approved service provider, and requires trust stores managed by the organization to contain only approved

4
artefacts
0
held by a system
0
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • Certificate policy or the approval record for the external certificate provider · Policy repository / GRC workspace
  • Certificate inventory with issuer, subject and expiry · Policy repository / GRC workspace
  • Trust store contents reviewed against the approved trust anchor list · Document repository
  • Procedures for certificate issue, renewal and revocation · Policy repository / GRC workspace

First move

This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.

Common gaps auditors find

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 sheet

SC-16 Transmission of Security and Privacy Attributes. Associate [organization-defined] with information exchanged between systems and between system components · SC-18 Mobile Code. Define acceptable and unacceptable mobile code and mobile code technologies; and Authorize, monitor, and control the use of mobile code within the system