PSS-03 Online Register of Known Vulnerabilities
Operate or point to a daily updated online register of known vulnerabilities affecting the provider and assets customers install or run themselves, scored using CVSS, reachable by every customer, and stating per flaw whe
4
artefacts
0
held by a system
1
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
- Screenshot of the customer facing vulnerability register showing its last update timestamp · Vulnerability scanner / patch tooling
governing documentDocuments that govern the control
- Register entries carrying CVSS vectors and calculated scores · Policy repository / GRC workspace
- Register fields stating patch availability, rollout date and the party who deploys · Policy repository / GRC workspace
- Access route demonstrating that any customer can reach the register · 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
- Register refreshed when convenient rather than every day
- Severity shown as a local high or low label instead of a CVSS score
- Register covers hosted components but omits agents customers install themselves
- Register placed behind a support portal many customers cannot open
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 sheetPSS-02 Identification of Vulnerabilities of the Cloud Service · PSS-04 Error handling and Logging Mechanisms