What evidence do auditors commonly ask for on TVM-07 Penetration Testing?

Penetration testing schedule and scope definitions; Reports from independent testers with dates and findings; Tester selection criteria and evidence of independence; Remediation tracking for findings with retest results.

What is the most common gap auditors find on TVM-07?

Testing done by internal staff only

CSA CCM v4.1 · TVM - Threat & Vulnerability Management

`TVM-07` Penetration Testing

The organisation sets up, operates and evaluates processes, procedures and technical measures for having independent third parties perform penetration tests on a periodic basis.

Source: CSA CCM v4.1, TVM-07. 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 CSA CCM v4.1 in the compliance library.

Version 4.1 adds 11 controls (among them API security, log sanitisation and a service bill of materials) and renumbers several domains. CSA accepts v4.0.x during its transition; if your STAR assessment is still on v4.0.1, check the numbering against it.

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

Reports from independent testers with dates and findings · Vulnerability scanner / patch tooling
Tester selection criteria and evidence of independence · Vulnerability scanner / patch tooling

governing documentDocuments that govern the control

Penetration testing schedule and scope definitions · Policy repository / GRC workspace
Remediation tracking for findings with retest results · 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

Testing done by internal staff only
Scope excludes cloud management interfaces or APIs
Findings left open with no retest

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

TVM-06 External Library Vulnerabilities · TVM-08 Vulnerability Remediation Schedule