11.6.1 Payment page change and tamper detection
A change- and tamper-detection mechanism is deployed for payment pages to alert personnel to unauthorized modifications to HTTP headers and contents of payment pages as received by the consumer browser.
5
artefacts
2
held by a system
1
at each review
moderate
to go live
SIEM / log platform
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Client-side monitoring tool deployment evidence · SIEM / log platform
- Sample tamper detection alerts · SIEM / log platform
periodic reviewEvidence produced at each review
- Weekly or risk-based scan results · Vulnerability scanner / patch tooling
governing documentDocuments that govern the control
- HTTP header and script inventory for payment pages · Policy repository / GRC workspace
- Response runbooks · Policy repository / GRC workspace
First move
Start with the 2 of 5 artefacts that already live in a system (SIEM / log platform); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- No client-side monitoring
- Script inventory missing
- Alerts untriaged
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 sheet11.5.2 Change detection mechanism (FIM) · 12.1.1 An overall information security policy is: • Established. • Published. • Maintained. • Disseminated to all relevant personnel, as well as to relevant vendors and business partners