SA-2 Allocation of resources
Requires high level security and privacy requirements for the system or service to be established during mission and business process planning, the resources needed to protect it to be identified, documented and allocate
4
artefacts
0
held by a system
2
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
none for this control
periodic reviewEvidence produced at each review
- Resource allocation records tied to the protection of the system · Document repository
- Evidence security requirements were considered before funding decisions · Document repository
governing documentDocuments that govern the control
- Documented high level security and privacy requirements from the planning stage · Policy repository / GRC workspace
- Budget or investment documentation showing a discrete security and privacy line item · Policy repository / GRC workspace
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
- Security funded from residual project budget with no separate line item
- Requirements determined after design, when funding is already committed
- Ongoing operational security costs omitted, only build costs funded
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-1 Policy and procedures for system and services acquisition · SA-3 System development life cycle