CA-3(6) Information Exchange | Transfer Authorizations
Verify that individuals or systems transferring data between interconnecting systems hold the requisite authorizations, meaning write permissions or privileges, before accepting such data.
3
artefacts
0
held by a system
2
at each review
hard
to go live
Vendor register / contract 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
- Authorisation records for the systems and individuals permitted to write across each interconnection · Document repository
- Evidence that write permission is checked before data is accepted · Identity provider / directory
governing documentDocuments that govern the control
- Interconnection security agreements naming the parties authorised to transfer data · Vendor register / contract repository
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
- Interconnection agreements exist but nothing checks that the transferring party is authorised
- Authorisations never re-reviewed after the interconnection goes live
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-3 Information Exchange · CA-5 Plan of Action and Milestones