WEB-05: Unauthorized Code On Web Pages
Mechanisms exist to prevent unauthorized code from being present in a secure page as it is rendered in a client's browser.
Renumbered: Formerly WEB-01.1 in SCF 2025.4.
Code reused: In SCF 2025.4 and earlier, WEB-05 was Cookie Management. That control is now PRI-25.
Control Question: Does the organization prevent unauthorized code from being present in a secure page as it is rendered in a client's browser?
General (5)
| Framework | Mapping Values |
|---|---|
| PCI DSS 4.0.1 (source) | 6.4.3 |
| PCI DSS 4.0.1 SAQ A (source) | 6.4.3 |
| PCI DSS 4.0.1 SAQ A-EP (source) | 6.4.3 |
| PCI DSS 4.0.1 SAQ D Merchant (source) | 6.4.3 |
| PCI DSS 4.0.1 SAQ D Service Provider (source) | 6.4.3 |
Capability Maturity Model
Level 0 — Not Performed
Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.
Level 1 — Performed Informally
Web Security (WEB) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include: ▪ Policies, standards & procedures associated with WEB domain capabilities provide limited coverage due to the depth and breadth of the existing documentation. ▪ Web management-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
Level 2 — Planned & Tracked
Web Security (WEB) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with WEB domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with WEB domain capabilities are documented and maintained by process owners. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with WEB domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Web security-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Web security management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.
Level 3 — Well Defined
Web Security (WEB) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with WEB domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with WEB domain capabilities are well-documented and kept current by process owners. ▪ A web management team, or simiE210:E1635main capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of web management operations (e.g., secure web gateway and Content Management System (CMS) solution). ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with WEB domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls). ▪ An implemented and operational capability exists to prevent unauthorized code from being present in a secure page as it is rendered in a client's browser.
Level 4 — Quantitatively Controlled
Utilize SCR-CMM Level 3 criteria definitions: ▪ There are no defined Level 4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to operationalize this control. ▪ While it may be possible to develop “metrics-driven” capabilities for this control, the criteria would be organization-specific to define.
Level 5 — Continuously Improving
Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.
Assessment Objectives
- WEB-05_A01 a capability exists to review secure pages for unauthorized code.
Evidence Requirements
- E-WEB-03 Website Change Detection & Unauthorized Code Monitoring
-
Documented evidence of website change detection and monitoring for unauthorized code on web pages.
Website Security
Technology Recommendations
Micro/Small
- Review website for unauthorized scripts or content regularly
Small
- Policy to prevent and detect unauthorized code on web properties
Medium
- Formal unauthorized code detection program
- Web integrity monitoring
Large
- Enterprise web integrity monitoring (e.g., RiskIQ, Reflectiz)
- Automated unauthorized code detection
Enterprise
- Enterprise web security platform with unauthorized code detection (e.g., Featurespace, Reflectiz, c/side)
- Real-time monitoring