What evidence do auditors commonly ask for on PSS-03 Online Register of Known Vulnerabilities?

Screenshot of the customer facing vulnerability register showing its last update timestamp; Register entries carrying CVSS vectors and calculated scores; Register fields stating patch availability, rollout date and the party who deploys; Access route demonstrating that any customer can reach the register.

What is the most common gap auditors find on PSS-03?

Register refreshed when convenient rather than every day

BSI C5 (121-criteria catalogue) · C5: Product Safety and Security

`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 whether an update exists, when it ships and who deploys it.

Source: BSI C5 (121-criteria catalogue), PSS-03. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open BSI C5 (121-criteria catalogue) in the compliance library.

The edition of the catalogue is not stamped here; check the edition your attestation is issued against.

artefacts

held by a system

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. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

Screenshot of the customer facing vulnerability register showing its last update timestamp · Policy repository / GRC workspace
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

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

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 sheet

PSS-02 Identification of Vulnerabilities of the Cloud Service · PSS-04 Error handling and Logging Mechanisms