EvidenceSheet
PCI DSS 4.0 · Req 6: Secure Systems and Software

6.2.4 Coding practices prevent common attacks

Software engineering techniques or other methods are defined and used by software development personnel to prevent or mitigate common software attacks and related vulnerabilities (e.g., injection, broken auth, XSS).

5
artefacts
1
held by a system
0
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

  • SAST and DAST configuration · Cloud console / configuration management

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • Secure coding guideline document · Document repository
  • Mapping to OWASP Top 10 · Document repository
  • Sample remediated findings · Document repository
  • Library and framework standards · 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

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

6.2.3.1 Code review findings corrected · 6.3.1 Security vulnerabilities are identified and managed as follows: • New security vulnerabilities are identified using industry-recognized sources for security vulnerability information, including alerts from international and national computer emergency response teams (CERTs). • Vulnerabilities