SA-23 Specialization. Employ [organization-defined] on [organization-defined] supporting mission essential services or functions to increase the trustworthiness in those systems or components
Specialization. Employ [organization-defined] on [organization-defined] supporting mission essential services or functions to increase the trustworthiness in those systems or components.
5
artefacts
0
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
none for this control
periodic reviewEvidence produced at each review
- Evidence linking the specialisation to the increase in trustworthiness sought · Document repository
- Documented evidence of the modification, augmentation or reconfiguration as implemented · Document repository
- Assessment or test results confirming the specialisation achieved its intent without breaking function · Source control / CI pipeline
governing documentDocuments that govern the control
- Identification of the systems or components supporting mission essential services or functions that are in scope · Policy repository / GRC workspace
- The specialisation employed, such as design modification, augmentation or reconfiguration, documented for each · 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
- Hardening applied generically rather than specialised to the mission essential function it protects
- Modification implemented with no record, so it is lost at the next refresh or vendor update
- Trustworthiness increase asserted with no assessment behind it
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 sheetSA-22 Unsupported System Components · SA-24 Design For Cyber Resiliency. Design organizational systems, system components, or system services to achieve cyber resiliency by: Defining the following cyber resiliency goals: [organization-defined]. Defining the following cyber resiliency objectives: [organization-defined]. Defining the following