Direct Answer: What is Permissions-Policy & Why is It Crucial?
Permissions-Policy (formerly Feature-Policy) is a standardized HTTP response header (W3C Working Draft) that allows webmasters to declare which browser APIs, hardware sensors, and tracking features can be executed by a website and any embedded <iframe> elements. By explicitly setting directives like camera=(), microphone=(), geolocation=(), interest-cohort=(), browsing-topics=(), websites prevent rogue third-party advertising scripts, analytics tags, or compromised dependencies from silently eavesdropping on microphones, accessing webcams, tracking physical GPS coordinates, or compiling Google FLoC / Topics behavioral interest profiles without explicit user authorization.
Security Headers Comparison Matrix
Architectural distinctions between Permissions-Policy, CSP, and legacy Feature-Policy
| Security Header | Primary Function | Primary Threat Mitigated | Current Specification Status |
|---|---|---|---|
| Permissions-Policy | Restricts browser hardware (camera, mic, GPS) & privacy tracking APIs (FLoC, Topics, payments) | Rogue third-party script hardware access, behavioral ad tracking, and unauthorized sensor fingerprinting | W3C Working Draft (Active Standard) |
| Feature-Policy | Legacy predecessor to Permissions-Policy (semicolon-delimited format) | Unauthorized browser feature execution in legacy Chromium & Gecko builds | Deprecated (Replaced by Permissions-Policy) |
| Content-Security-Policy (CSP) | Controls origin sources for scripts, styles, images, fonts, frames, and connect endpoints | Cross-Site Scripting (XSS), data injection, clickjacking (frame-ancestors), and packet sniffing | W3C Recommendation (Standard) |