SC-8 Transmission confidentiality and integrity
Requires the confidentiality or integrity, as the organization determines, of transmitted information to be protected, so that data in transit cannot be read or altered by parties along the path.
4
artefacts
2
held by a system
0
at each review
easy
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Configuration evidence for transport encryption and its accepted versions and ciphers · Cloud console / configuration management
- Scan results confirming protection across in scope endpoints · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Definition of the transmissions in scope and the protection required for each · Policy repository / GRC workspace
- Treatment of internal service to service traffic as well as external traffic · Document repository
First move
Automate the pull from your Cloud console / configuration management. Configuration snapshots and change history from the cloud console or IaC repository, diffed against the baseline.
Common gaps auditors find
- External traffic encrypted while internal traffic between services is in the clear
- Deprecated transport versions and weak ciphers left enabled
- Certificate validation disabled in application clients, so encryption gives no assurance of peer identity
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