Browser Security
What is Browser Security?
Security measures and configurations for web browsers to protect against web-based threats including malicious websites, extensions, and exploits.
Frameworks that govern browser security
What the standards actually require on browser security
Requirements naming browser security across 2 standards, quoted from the control text.
Web browser security settings cannot be changed by users. Required at Maturity Levels One, Two and Three of the User application hardening mitigation strategy (Appendices A, B and C);
acsc-essential-eight::E8-UAH-ISM-1585 · User application hardening (ISM-1585): Web browser security settings cannot be changed by users →HL7 FHIR Resilience + Privacy + SMART Health Cards. RATE LIMITING AND ANTI-ABUSE (FHIR-SEC-14) - API rate limiting + throttling + DDoS protection + abuse detection + IP/Subject + Token-based limits + sliding window + token bucket + sectoral best practices;
HL7-FHIR-Resilience-RateLimit-CORS-AntiAbuse-SmartHealth · HL7 FHIR Resilience - Rate Limiting + Anti-Abuse + CORS + SMART Health Cards + De-identification + Privacy →Questions people ask about browser security
What is Browser Security?
Why is Browser Security important for compliance?
Which compliance frameworks address Browser Security?
Where can I learn more about Browser Security?
See how Browser Security applies across compliance frameworks
Our platform maps 1,016 frameworks with 316K cross-framework control mappings. Explore how this concept is addressed across standards.