1.5.1 Security controls on dual-connected computing devices
Security controls are implemented on any computing devices that connect to both untrusted networks and the CDE to prevent threats entering via these devices.
5
artefacts
1
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- MDM configuration export · Endpoint management (MDM / EDR)
periodic reviewEvidence produced at each review
- Sample device inspection records · Endpoint management (MDM / EDR)
governing documentDocuments that govern the control
- Endpoint policy defining required controls · Policy repository / GRC workspace
- EDR or host firewall deployment report · Policy repository / GRC workspace
- User attestation of policy · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Endpoint management (MDM / EDR) on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- BYOD devices outside MDM scope
- Personal firewall disabled by user
- No alteration prevention controls
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 sheet1.4.5 Internal IP and routing information protected · 2.1.1 All security policies and operational procedures that are identified in Requirement 2 are: • Documented. • Kept up to date. • In use. • Known to all affected parties