Essential Eight · User application hardening
ISM-1585
Web browser security settings cannot be changed by human users
frameworkASD Essential Eight
sectionUser application hardening
levelsML1, ML2, ML3
csf 2.0PR.PS-01
topicsSecure Config
frameworks0 9 1
Official textWeb browser security settings cannot be changed by human users.Australian Signals Directorate, Information Security Manual (September 2026). © Commonwealth of Australia, CC BY 4.0
Wrong or missing mapping? Report it
| Framework | Requirement | Title | Link | Source / reason |
|---|---|---|---|---|
| NIST CSF 2.0 | PR.PS-01 | Configuration management practices are established and applied | Editorial | Same topic: Secure Config (editorial pick) |
| ISO 27001 | A.8.9 | Configuration management | Editorial | Same topic: Secure Config (editorial pick)3 loosely related (not mappings) |
| CIS v8.1 | CIS 4.1CIS 4.2CIS 4.3CIS 4.6CIS 4.7CIS 4.8CIS 16.7 | Establish and Maintain a Secure Configuration Process; Establish and Maintain a Secure Configuration Process for Network Infrastructure… | Editorial | Same topic: Secure Config (editorial pick)3 loosely related (not mappings)CIS 4.10 Enforce Automatic Device Lockout on Portable End-User Devices Only shares CSF PR.PS-01: related, not a mapping CIS 4.11 Enforce Remote Wipe Capability on Portable End-User Devices Only shares CSF PR.PS-01: related, not a mapping CIS 4.12 Separate Enterprise Workspaces on Mobile End-User Devices Only shares CSF PR.PS-01: related, not a mapping |
| SOC 2 | CC5.2CC7.1 | General controls over technology; Detecting configuration changes and new vulnerabilities | Editorial | Same topic: Secure Config (editorial pick) |
| PCI DSS | 2.2.12.2.2 | System configuration standards developed and maintained; Vendor default accounts managed or removed | Editorial | Same topic: Secure Config (editorial pick) |
| CMMC | CM.L2-3.4.1CM.L2-3.4.2CM.L2-3.4.6CM.L2-3.4.7 | System Baselining; Security Configuration Enforcement… | Editorial | Same topic: Secure Config (editorial pick)6 loosely related (not mappings) |
| 800-53 | CM-2CM-6CM-7 | Baseline Configuration; Configuration Settings… | Editorial | Same topic: Secure Config (editorial pick)8 loosely related (not mappings) |
| HIPAA | §164.310(d)§164.310(d)(2)(iii)§164.316(b)(2)(ii)§164.316(b)(2)(iii) | Device and Media Controls; Accountability… | No mapping. Only shares CSF PR.PS-01: related, not a mapping | |
| GDPR | Art.28(1) | Processor | No mapping. Only shares CSF PR.PS-01: related, not a mapping | |
| NIS2 | 6.3 | Configuration management | Editorial | Same topic: Secure Config (editorial pick) |
| DORA | Art.28(8)Art.30(2) | General principles; Key contractual provisions | No mapping. Only shares CSF PR.PS-01: related, not a mapping | |
| CPS 234 | — | No requirement | No mapping in our data | No mapping in our data (CPS 234 is principles-based and its links are editorial). |
| Cyber Essentials | CE 2 | Secure Configuration | Editorial | Same topic: Secure Config (editorial pick)1 loosely related (not mappings) |
Crosswalk a published crosswalk (NIST, ENISA, CIS, PCI SSC) makes the link · Editorial ControlMapping's judgement where no crosswalk exists; the reason is shown · only shares a CSF 2.0 outcome: worth checking, not a mapping · No mapping in our data nothing mapped in our data; often new work, but check the coverage notes. How links are sourced.