SI-16 Memory Protection
Implement FedRAMP-defined safeguards to protect memory from unauthorized code execution (DEP, ASLR).
5
artefacts
1
held by a system
0
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
- Security monitoring alert tuning records · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Control implementation statement for SI-16 citing the system mission and inheritance from common controls · Document repository
- Input validation standards and code review checklist · Policy repository / GRC workspace
- Patch management policy with severity based SLAs · Policy repository / GRC workspace
- Patch deployment reports across server, endpoint, and network estates · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your SIEM / log platform 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
- EDR coverage gaps on legacy operating systems
- Anti malware signatures not updated on isolated network segments
- Input validation handled inconsistently across microservices
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 sheetSI-12 Information Management and Retention · SR-1 Policy and Procedures (SR-1)