PM-5 System Inventory. Develop and update [organization-defined] an inventory of organizational systems
System Inventory. Develop and update [organization-defined] an inventory of organizational systems.
5
artefacts
1
held by a system
0
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
- Reconciliation records showing the inventory was compared against an independent source such as network discovery or the finance asset register · Cloud console / configuration management
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- The inventory of organisational systems, with the attributes recorded for each · Policy repository / GRC workspace
- Evidence the inventory is updated at the defined frequency · Policy repository / GRC workspace
- The process and sources used to build and reconcile the inventory · Policy repository / GRC workspace
- Ownership assignment for each system in the inventory · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Cloud console / configuration management 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
- Inventory maintained manually and reconciled against nothing, so unregistered systems stay invisible
- Cloud subscriptions and vendor hosted services excluded because the inventory was built around owned hardware
- Systems recorded with no owner, so nothing downstream in the programme can be assigned
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-4 Plan of Action and Milestones Process. Implement a process to ensure that plans of action and milestones for the information security, privacy, and supply chain risk management programs and associated organizational systems: Are developed · PM-6 Measures of Performance. Develop, monitor, and report on the results of information security and privacy measures of performance