Skip to content
FixSecurityHeadersScan a site

How to add Permissions-Policy on Nginx

Last updated · Reviewed by a CISSP-certified security practitioner

To add Permissions-Policy on Nginx, set the header in nginx.conf (server block) with the value camera=(), microphone=(), geolocation=(), payment=(), usb…. Turns off browser features (camera, mic, geolocation) you don't use. Run nginx -t, then systemctl reload nginx. Then confirm it with curl -I or a free FixSecurityHeaders scan.

What does Permissions-Policy do?

Permissions-Policy disables powerful browser APIs for your page and any embedded iframes unless you explicitly allow them.

Risk if missing: Injected or third‑party scripts could request camera, microphone, geolocation or payment APIs.

What is the Nginx configuration?

Add this to nginx.conf (server block):

nginx.conf (server block)
# Inside your server { } block
add_header Permissions-Policy "camera=(), microphone=(), geolocation=(), payment=(), usb=(), interest-cohort=()" always;

How do I add it step by step?

  1. Open nginx.conf (server block).
  2. Paste the Permissions-Policy configuration shown below.
  3. Run nginx -t, then systemctl reload nginx.
  4. Run curl -I https://yourdomain.com and look for the permissions-policy line.
  5. Scan your site on FixSecurityHeaders to confirm the grade improved.

How do I verify it worked?

terminal
curl -sI https://yourdomain.com | grep -i "permissions-policy"
# expected:
# permissions-policy: camera=(), microphone=(), geolocation=(), payment=(), usb=(), interest-cohort=()

Check your site now

Free scan, instant grade, exact fixes for your stack.

What are the common mistakes?

  • Allow features you actually use, e.g. payment=(self) for Payment Request checkouts.
  • Always add the always flag so headers are sent on error responses too.
  • add_header in a location block replaces all add_header directives inherited from server — repeat them or use an include file.

Quick reference

HeaderPermissions-Policy
Recommended valuecamera=(), microphone=(), geolocation=(), payment=(), usb=(), interest-cohort=()
StackNginx
Wherenginx.conf (server block)
ComplianceOWASP ASVS V14.4, SOC 2 CC6.8

FAQ

What value should I use for Permissions-Policy?

A safe default is camera=(), microphone=(), geolocation=(), payment=(), usb=(), interest-cohort=(). Allow features you actually use, e.g. payment=(self) for Payment Request checkouts.

Why isn't Permissions-Policy showing up on Nginx?

Always add the always flag so headers are sent on error responses too. Also clear any CDN or page cache, and check you edited the config that actually serves your domain.

Does Permissions-Policy affect SEO or performance?

No measurable performance cost — it's a few bytes per response. It doesn't affect rankings directly, but a misconfigured policy can break page resources, so test before enforcing.

Which compliance frameworks reference Permissions-Policy?

OWASP ASVS V14.4, SOC 2 CC6.8.

Related guides