7.4.9 PII transmission controls
The organization must subject personal data transmitted over a data transmission network to controls designed to ensure it reaches its intended destination, typically by ensuring only authorized individuals have access t
4
artefacts
1
held by a system
1
at each review
moderate
to go live
SIEM / log platform
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Audit logs of transmissions retained and reviewable · SIEM / log platform
periodic reviewEvidence produced at each review
- Evidence of recipient verification, not merely of encryption in transit · Document repository
governing documentDocuments that govern the control
- Documented transmission controls covering authorisation, protection and recipient verification · Document repository
- Access controls over transmission systems · Document repository
First move
Start with the 1 of 4 artefacts that already live in a system (SIEM / log platform); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Encryption treated as the whole of the control, with no assurance the data reached the right recipient
- Transmission logs absent, so a misdirection cannot be detected or investigated
- Bulk transfers run by individuals with no authorisation step
- Recipient addresses maintained manually in scripts, where a single edit misroutes a whole file
- Ad hoc transfers by email and file sharing outside the controlled route
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 sheet7.4.8 Disposal · 7.5.1 Identify basis for PII transfer between jurisdictions