PM-32 Purposing
Ensures systems and components are used only for the purpose they were acquired and assessed for, since repurposing invalidates the supply chain assessment.
3
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
- Records of intended purpose per system or component · Document repository
- Reassessment evidence when purpose changes · Document repository
governing documentDocuments that govern the control
- Approval process for repurposing · 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
- components repurposed into higher-criticality use with no reassessment
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 sheetPM-31 Continuous Monitoring Strategy · PS-1 Policy and Procedures