EvidenceSheet

SC-8 Transmission Confidentiality and Integrity

Protect confidentiality and integrity of transmitted information using cryptographic mechanisms.

6
artefacts
1
held by a system
1
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

  • TLS configuration scan results across in scope endpoints · Vulnerability scanner / patch tooling

periodic reviewEvidence produced at each review

  • Denial of service protection configuration and capacity test results · Source control / CI pipeline

governing documentDocuments that govern the control

  • Control implementation statement for SC-8 citing the system mission and inheritance from common controls · Document repository
  • Boundary protection architecture with firewall and proxy rule documentation · Policy repository / GRC workspace
  • Cryptographic standards specifying approved algorithms and key lengths · Policy repository / GRC workspace
  • Key management procedures including rotation and escrow · Policy repository / GRC workspace

First move

Mostly documents and reviews. Pull the 1 system-held artefact from your Vulnerability scanner / patch tooling on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.

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-7(18) Boundary Protection | Fail Secure. Prevent systems from entering unsecure states in the event of an operational failure of a boundary protection device · SC-8(1) Cryptographic Protection