SOX Change Log Checker
Clause text

PCI DSS v4.0: the clauses the checker cites

The 4 PCI DSS v4.0 clauses behind the findings, each with the evidence an auditor asks for where it is held.

Summarised: a one-line statement of what the requirement asks. The standard's own text is not stated here, so it is not quoted.

4 clauses

PCI DSS 6.2.3 Custom software reviewed prior to production

Bespoke and custom software is reviewed before release to production by someone other than the developer who wrote it, using manual and automated methods.

A one-line statement; the standard's own text is not quoted here.

Evidence an auditor expects: Code review procedure referencing the secure coding guidelines in force; Pull request or merge request records showing review before merge to the release branch; Static analysis scan results for recent releases with findings tracked to closure; Secure coding guideline document used as the review baseline; Sample of released changes traced to completed reviews and fixed findings
Where it usually falls short: Branch protection allows direct commits to main without review; High-severity static analysis findings released with no documented fix or exception
Source: PCI DSS v4.0
PCI DSS 6.5.1 Change control procedures in production

Changes to system components in production follow a set procedure that records the reason for the change, its security impact, a documented approval, testing and a way back.

A one-line statement; the standard's own text is not quoted here.

Evidence an auditor expects: Change management procedure covering reason, security impact, approval, testing and back-out; Sample of change tickets with security impact assessment and authorised approvals; Test results showing security testing before deployment, including 6.2.4 checks for software changes; Documented rollback or back-out plans attached to changes; Deployment logs reconciled against approved change records
Where it usually falls short: Emergency or cloud console changes made with no change ticket; Security impact field completed as 'none' for every change
Source: PCI DSS v4.0
PCI DSS 6.5.2 Requirements confirmed after a significant change

After a significant change, the applicable PCI DSS requirements are confirmed in place on the new or changed systems and the documentation is updated.

A one-line statement; the standard's own text is not quoted here.

Evidence an auditor expects: Significant change criteria definition; Post-change PCI DSS validation checklists for recent significant changes; Updated network and data-flow diagrams and system inventory after the change; Evidence new systems were added to vulnerability scanning, logging, anti-malware and FIM; Link from significant changes to the annual scope confirmation record
Where it usually falls short: No definition of what counts as a significant change; New systems go live without being added to scanning or log collection
Source: PCI DSS v4.0
PCI DSS 6.5.4 Roles separated between production and pre-production

Roles and functions are separated between production and pre-production so that only reviewed and approved changes are deployed.

A one-line statement; the standard's own text is not quoted here.

Evidence an auditor expects: Segregation of duties matrix for development, deployment and production administration; Production access list showing developers hold no or only user-level access; CI/CD pipeline approval gates requiring reviewer approval before production deployment; Documented compensating procedural controls for small teams; Observation notes of a deployment demonstrating the approval gate
Where it usually falls short: Developers hold standing administrator access to production; Pipeline allows the change author to trigger production deployment without independent approval
Source: PCI DSS v4.0