references/security.md
GitHubManaging Microfrontends Security
How Deployment Protection and Vercel Firewall apply to each microfrontend application.
Deployment Protection and microfrontends
Each URL is protected by the Deployment Protection settings of the project it belongs to, so protection for the microfrontend experience as a whole is determined by the default application:
- Requests to a microfrontend host (a domain of the default application) are verified only by the default application's Deployment Protection.
- Requests directly to a child application (a child domain) are verified only by that child application's Deployment Protection.
This applies to all protection methods and bypass methods, including Vercel Authentication, Password Protection, Trusted IPs, Shareable Links, Protection Bypass for Automation, Deployment Protection Exceptions, and OPTIONS Allowlist.
Recommended configuration
- Default app: use Standard Protection so end users can reach the microfrontend through the default app's URL.
- Child apps: enable protection for all deployments so they aren't directly accessible. Child content is served through the default app's URL.
This works because Vercel routes to child apps within a single request at the network layer (see Path Routing) — not a rewrite that issues a separate request to the child's URL. Deployment protection on a child app therefore applies only when the child's URL is accessed directly.
Vercel Firewall and microfrontends
- The platform-wide firewall is applied to all requests.
- The customizable Web Application Firewall (WAF) of both the default application and the relevant child application is applied to a request:
- Requests to a microfrontend host are verified by the default application's WAF; requests to child paths are additionally verified by the child application's WAF.
- Requests directly to a child application are verified only by the child application's WAF.
This covers the entire Vercel WAF, including Custom Rules, IP Blocking, WAF Managed Rulesets, and Attack Challenge Mode.
Managing the WAF
- A rule that applies to all requests to a microfrontend → use the default application's WAF.
- A rule that applies only to a child application's paths → use the child project's WAF.