SC-51 Hardware-based Protection. Employ hardware-based, write-protect for [organization-defined] ; and Implement specific procedures for [organization-defined] to manually disable hardware write-protect for firmware modifications and re-enable the write-protect prior to returning to operational mode
Hardware-based Protection. Employ hardware-based, write-protect for [organization-defined] ; and Implement specific procedures for [organization-defined] to manually disable hardware write-protect for firmware modificati.
5
artefacts
0
held by a system
2
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
- Evidence the write protect is hardware based, such as a jumper, switch or one time programmable setting · Document repository
- Records of each firmware modification showing write protect was disabled, the change made, and protection re-enabled before return to operation · Document repository
governing documentDocuments that govern the control
- The defined components carrying hardware based write protection for firmware · Document repository
- The specific procedures for the defined personnel to manually disable write protect for firmware modification · Policy repository / GRC workspace
- Verification that write protect is enabled on operational systems · Document repository
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
- Write protect left disabled after a firmware update because re-enablement is not a checklist step
- Protection implemented as a software setting the firmware itself can change
- No verification sweep, so a system running unprotected is only found by chance
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 sheetSC-50 Software-enforced Separation and Policy Enforcement. Implement software-enforced separation and policy enforcement mechanisms between [organization-defined] · SI-1 Policy and procedures for system and information integrity