Permissions-Policy header check

Short answer

Permissions-Policy (formerly Feature-Policy) switches off browser features your site doesn't need, such as the camera, microphone and location, so an injected or third-party script can't use them either. A sensible starting value is camera=(), microphone=(), geolocation=(). SiteShield warns when it's missing (2 of 100 points).

Browser protectionWorth 2 of 100 pointsBy Mumshad JawadUpdated

What is Permissions-Policy?

Each entry names a browser feature and the origins allowed to use it. An empty list () disables the feature for your page and every frame inside it; (self) allows only your own origin.

Weak
(no Permissions-Policy header: every feature follows the browser default)
Good
Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=(self)

Why it matters

Switches off browser features your site doesn't use (camera, microphone, location), so an injected script can't use them either.

Third-party scripts and embedded frames run with your page's permissions. If one is compromised, a locked-down policy stops it from prompting your visitors for camera, microphone or location access under your site's name. It's a cheap way to shrink what an attacker can do after a successful injection.

SiteShield maps this check to:

OWASP ASVS V14.4

See how these standards fit together in the UAE website security checklist.

How SiteShield grades it

This check, "Permissions-Policy", can cost up to 2 points: a fail loses all 2, a warning loses 1. Every scan starts at 100.

ResultWhenPoints lost
PassA Permissions-Policy header is present (any value).0
WarningNo Permissions-Policy header.1

How to check it yourself

curl -sI https://example.com | grep -i permissions-policy

Or run a free SiteShield scan, which checks this and 16 other settings in one go.

How to fix it

The quick version: Send Permissions-Policy: camera=(), microphone=(), geolocation=()

Cloudflare

Rules → Transform Rules → Modify Response Header: set static header Permissions-Policy to camera=(), microphone=(), geolocation=().

Nginx

add_header Permissions-Policy "camera=(), microphone=(), geolocation=()" always;

Apache

Header always set Permissions-Policy "camera=(), microphone=(), geolocation=()"

WordPress

If a plugin needs a feature (a store locator needs geolocation, a video-call widget needs camera), allow it for your own origin with (self) or for the provider's origin.

add_action('send_headers', function () {
    header('Permissions-Policy: camera=(), microphone=(), geolocation=()');
});

FAQ

Which features should I disable?

Everything your site doesn't use. camera, microphone and geolocation are the common ones; add payment, usb or fullscreen depending on your site. Only list features you understand so you don't block something your site needs.

What's the difference between Permissions-Policy and Feature-Policy?

Permissions-Policy is the renamed, current version with a different syntax. SiteShield checks for the Permissions-Policy header.

Test your Permissions-Policy now

Run all 17 checks on your website and email domain in about 30 seconds. Free, no signup, passive checks only.

Rather not do it yourself? Fix it for me starts at AED 750 (about USD 205 by PayPal), quote agreed first. Monitoring re-scans weekly for AED 99/month or AED 990/year.

Related checks

See all 17 security checks →