CA-9 Internal system connections
Requires internal connections of organization-defined components to be authorized, each documented with its interface details, the security and privacy needs it carries and what information passes over it, terminated whe
4
artefacts
0
held by a system
3
at each review
hard
to go live
Document repository
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
- Authorization records for each connection class or component type · Document repository
- Termination conditions and evidence connections were closed when met · HR system / LMS
- Periodic review confirming each connection is still needed · Document repository
governing documentDocuments that govern the control
- Register of authorized internal connections with documented characteristics · 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
- Internal connections treated as out of scope because they do not cross the boundary
- Register never updated as components were added, replaced or retired
- No defined termination conditions, so temporary connections become permanent
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 sheetCA-8 Penetration testing · CM-1 Policy and procedures for configuration management