What evidence do auditors commonly ask for on CA-9 Internal System Connections?

SSP CA-9 statement listing internal component connections authorised and the interface characteristics documented for each; Internal connection register showing each connection, its approval and security requirements; System security plan covering the authorization boundary; Control assessment report with tester names and dates; Plan of action and milestones tracking open findings; Authorization to operate memorandum signed by the authorizing official.

What is the most common gap auditors find on CA-9?

Assessment scope omits inherited cloud provider controls

FedRAMP Moderate (NIST SP 800-53 Rev 5 baseline) · CA - Assessment, Authorization, and Monitoring

`CA-9` Internal System Connections

Authorize internal connections of components to system; document interface characteristics.

Source: FedRAMP Moderate (NIST SP 800-53 Rev 5 baseline), CA-9. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open FedRAMP Moderate (NIST SP 800-53 Rev 5 baseline) in the compliance library.

A FedRAMP baseline is a subset of NIST SP 800-53 Rev 5, enhancements included.

artefacts

held by a system

at each review

hard

to go live

Document repository

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

Control assessment report with tester names and dates · Document repository

governing documentDocuments that govern the control

SSP CA-9 statement listing internal component connections authorised and the interface characteristics documented for each · Document repository
Internal connection register showing each connection, its approval and security requirements · Policy repository / GRC workspace
System security plan covering the authorization boundary · Policy repository / GRC workspace
Plan of action and milestones tracking open findings · Policy repository / GRC workspace
Authorization to operate memorandum signed by the authorizing official · Document repository

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Assessment scope omits inherited cloud provider controls
Reauthorization scheduled past the policy required interval
Authorization boundary description does not match the asset inventory

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

CA-8(2) Penetration Testing | Red Team Exercises (CA-8(2)) · CM-1 Policy and Procedures