WEB-10: Web Application Output Encoding
Mechanisms exist to ensure output encoding is performed on all content produced by a web application to reduce the likelihood of cross-site scripting and other injection attacks.
Renumbered: Formerly WEB-11 in SCF 2025.4.
Code reused: In SCF 2025.4 and earlier, WEB-10 was Secure Web Traffic. That control is now WEB-09.
Control Question: Does the organization ensure output encoding is performed on all content produced by a web application to reduce the likelihood of cross-site scripting and other injection attacks?
APAC (1)
| Framework | Mapping Values |
|---|---|
| APAC Australia ISM June 2026 | ISM-1241 |
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
SCR-CMM Level 1 criteria definitions are not available for this control: ▪ A reasonable person would conclude this control requires a structured process. ▪ At this level of maturity, the "ad hoc" nature of performing a capability informally would indicate the intent of the control is not met due to a lack of consistency and formality.
Level 2 — Planned & Tracked
SCR-CMM Level 2 criteria definitions are not available for this control: ▪ A reasonable person would conclude a well-defined and standardized process is required. ▪ At this level of maturity, the “requirements-driven” nature of performing the control is focused on a localized and/or regionalized implementation, not uniform and consistent across the organization. ▪ Requirements are narrowly scoped for applicability and are primarily derived from compliance obligations (e.g., laws, regulations and contracts).
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 ensure output encoding is performed on all content produced by a web application to reduce the likelihood of cross-site scripting and other injection attacks.
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-10_A01 output encoding is performed on all content produced by a web application to reduce the likelihood of cross-site scripting and other injection attacks.
Evidence Requirements
- E-WEB-04 Web Application Input Validation & Output Encoding
-
Documented evidence of web application input validation, sanitization and output encoding controls (e.g., test results, framework configuration).
Website Security
Technology Recommendations
Micro/Small
- Use output encoding to prevent XSS
Small
- Output encoding policy for web applications
- Prevent XSS
Medium
- Formal output encoding standards
- Prevent XSS via content security policy and encoding
Large
- Enterprise output encoding program
- CSP enforcement
- SAST for XSS detection
Enterprise
- Enterprise web security program with output encoding standards
- Automated XSS detection (DAST/SAST)
- CSP enforcement