1.4.3 Anti-spoofing measures implemented
Anti-spoofing measures are implemented to detect and block forged source IP addresses from entering the trusted network.
5
artefacts
2
held by a system
2
at each review
moderate
to go live
Endpoint management (MDM / EDR)
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- URPF or equivalent configuration on edge devices · Endpoint management (MDM / EDR)
- Sample logs of dropped spoofed packets · SIEM / log platform
periodic reviewEvidence produced at each review
- Test results from spoofing simulation · Source control / CI pipeline
- Annual validation report · Cloud console / configuration management
governing documentDocuments that govern the control
- Bogon and martian ACLs · Policy repository / GRC workspace
First move
Start with the 2 of 5 artefacts that already live in a system (Endpoint management (MDM / EDR)); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Anti-spoofing disabled for performance
- No logging of drops
- Not configured on all ingress points
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.2 Inbound traffic from untrusted networks restricted · 1.4.4 Account data not stored on internet-accessible systems