SC-43 Usage Restrictions. Establish usage restrictions and implementation guidelines for the following system components: [organization-defined] ; and Authorize, monitor, and control the use of such components within the system
Usage Restrictions. Establish usage restrictions and implementation guidelines for the following system components: [organization-defined] ; and Authorize, monitor, and control the use of such components within the syste.
5
artefacts
1
held by a system
3
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
- Monitoring records showing use is observed against the restrictions · SIEM / log platform
periodic reviewEvidence produced at each review
- Authorisation records for use of those components within the system · Document repository
- Evidence of control action taken when unauthorised use was detected · Document repository
- Review of the restrictions when the component or its risk profile changed · Document repository
governing documentDocuments that govern the control
- The defined system components subject to usage restrictions, and the restrictions and implementation guidelines established for each · 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
- Restrictions written for a component class with no way to detect which instances are actually in use
- Authorisation granted once with no expiry, so components stay authorised after the need ends
- Monitoring absent, so the authorise, monitor and control triad reduces to authorise alone
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-42 Sensor Capability and Data. Prohibit [organization-defined] ; and Provide an explicit indication of sensor use to [organization-defined] · SC-44 Detonation Chambers. Employ a detonation chamber capability within [organization-defined]