DCS-02 Off-Site Transfer Authorization Policy and Procedures
Require written or cryptographically verifiable authorisation before hardware, software or data is relocated or transferred to an offsite or alternate location, under policies reviewed at least annually.
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
- Authorisation records for recent transfers · Document repository
- Evidence the authorisation is written or cryptographically verifiable · Document repository
- Annual review record · Document repository
governing documentDocuments that govern the control
- The relocation and transfer procedure stating the authorisation requirement · 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
- Transfers approved verbally with no retained record
- Authorisation retained but not attributable to a specific approver
- Data transfers treated as out of scope, with only hardware covered
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 sheetDCS-01 Off-Site Equipment Disposal Policy and Procedures · DCS-03 Secure Area Policy and Procedures