AC-4(4) Flow Control of Encrypted Information
Prevent encrypted information from bypassing flow control mechanisms; required at HIGH.
2
artefacts
0
held by a system
1
at each review
hard
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
none for this control
periodic reviewEvidence produced at each review
- TLS inspection config · Cloud console / configuration management
governing documentDocuments that govern the control
- SSL break-and-inspect policy · 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
- Encrypted bypass paths
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 sheetAC-4 Information Flow Enforcement · AC-4(21) Physical or Logical Separation of Information Flows