Netlify security: what production, Deploy Previews and branch deploys each expose
A Netlify project serves one repository as several live deploys, each with its own address, functions and variable values.
This guide explains the project and team settings that decide what each deploy context exposes, what Netlify says it secures and what it leaves to you, and what its Acceptable Use Policy says about testing. It comes with a matrix comparing production, Deploy Previews and branch deploys across visibility, environment variables, functions, forms, notifications, headers, redirects and repository visibility, with one synthetic form submission and a review of where your secrets reach.
In this guide
Netlify deploy-context exposure matrix
Paste the table into a spreadsheet and keep a separate copy for each Netlify project. For each area, read the setting where the second column points, write what production, Deploy Previews and branch deploys each show, and keep what the last column lists.
How to use itHide the instructions
Rows 3 to 5 are the secret-exposure review: record that a variable exists, its scopes, the contexts it reaches and whether it is flagged as secret, never a value. Rows 1, 12 and 14 go only to your own site. Row 1 is one page view per kind of address in a private browser window, row 12 is one synthetic form submission to a preview once row 11 has listed every notification and integration and each email recipient, Slack channel, webhook destination and automation is yours, and row 14 sends one header request to each of five addresses, with no load. Every other row reads a setting, list, file, log or policy page. Plan conditions are as Netlify's documentation gave them on 15 November 2026, and this page calls the plan Netlify's pages name after Pro the top plan.
18 rows
Area
Where to look
1. Who can open each deploy (one page view per kind of address)
- Where to look
- Credit-based plans: Project configuration > General > Visitor access > Project visibility, and the team default at Team settings > General > Visitor access > Default project visibility. Other plans: Project configuration > General > Visitor access > Password Protection, and Team settings > Access & security > Visitor access > Default Password Protection settings. Then load one production, one Deploy Preview and one branch deploy address of your own project, a single time each, in a private window with no Netlify session.
- Production
- Public, password or private for production. Netlify's project visibility page says a public project exposes its production deploys to anyone or any bot that visits the URL, unless additional authentication was added. Note whether that is intended.
- Deploy Previews
- The preview setting: private, public, or a password set for "Previews only" or "Production and previews". Netlify says preview links can be shared with anyone who has them unless password or team login protection is set up. Note the default your team started with: private for teams created on or after 28 July 2026.
- Branch deploys
- Branch deploys fall under the same preview setting. Under Password Protection, note whether a basic password (anyone who knows it) or team login (team members only, and not Git Contributors) protects them.
- Record and keep
- The setting in a dated screenshot, and what each of the three addresses showed: the site itself, a password prompt or a Netlify login. Never the shared password.
2. Deploy addresses, permalinks and old deploys
- Where to look
- The Deploys tab, filtered by deploy context, and Project configuration > Developer settings > Automatic Deletion, which Netlify's manage deploys page names. The same page says changing the retention limit is available on the top plan.
- Production
- The production branch, the main URL and each custom domain. Earlier production deploys keep their own permalinks, and Netlify says a permalink's content never changes.
- Deploy Previews
- Each open Deploy Preview by number, including agent run previews with the agent- prefix. Netlify says a Deploy Preview stays available until the deploy is deleted.
- Branch deploys
- Each branch with a branch deploy and any branch subdomain. Netlify does not automatically delete the most recent successful deploy of a branch.
- Record and keep
- The retention setting (by default 30 days, or 90 on paid plans, per Netlify's page) and, by deploy ID, any old deploy that still holds an outdated build or outdated values. Deleting one is the owner's call, and Netlify logs it as Deploy deleted.
3. Secret-exposure review: variable inventory
- Where to look
- Project configuration > Environment variables, using the scope and deploy context filters that Netlify's overview says the list supports. Read key names from the filtered list only: do not expand a variable, use the clipboard copy in .env format or run netlify env:list.
- Production
- Each key listed under the Production filter, with its scopes. Whether it is flagged "Contains secret values", and whether its value is shared with other contexts, which is Netlify's default: take both from the list only where it shows them without expanding the variable, and otherwise from whoever set it.
- Deploy Previews
- Each key listed under the Deploy Previews filter, and whether previews get a value of their own or the shared one, taken from whoever set it rather than by comparing values. Flag every payment, email, database or CRM credential that previews receive at its production value.
- Branch deploys
- The same for Branch deploys, plus each Branch value and wildcard such as release/*, which Netlify says also applies to that branch's permalinks and Deploy Previews.
- Record and keep
- Key names, scopes, contexts and the secret flag. Never a value, and no step that displays one.
4. Secret-exposure review: variables outside the project list
- Where to look
- netlify.toml in the repository, Team settings > Environment variables for shared variables (Pro and the top plan), read by key name without expanding a variable, and the build command for each context.
- Production
- Each key netlify.toml sets for the production context. Netlify says file values override UI values with the same key, are stored in the repository and are not available to serverless functions.
- Deploy Previews
- Each key under [context.deploy-preview.environment]. Netlify recommends setting sensitive values with the UI, CLI or API rather than in the file, where possible.
- Branch deploys
- Each key under [context.branch-deploy] and branch-named contexts. Shared variables reach every site in the team, and Netlify says only Team Owners can read and access them, so a Team Owner records their key names and scopes.
- Record and keep
- File path and line with the key name. Where a line holds a credential, note only that one is there. On credit-based plans, note whether the AI model provider variables Netlify sets automatically are in use.
5. Secret-exposure review: scanning and its exclusions
- Where to look
- The project overview page and the deploys list, which Netlify's Secrets Controller page says show scanning alerts and per-deploy detection, and the variable list, by key name, for keys starting SECRETS_SCAN_.
- Production
- Whether any recent production deploy shows secrets detected, and whether a SECRETS_SCAN_ENABLED or SECRETS_SCAN_SMART_DETECTION_ENABLED key exists. Netlify says the first set to false disables all secret scanning, and the second set to false turns off smart detection.
- Deploy Previews
- Whether a Deploy Preview build failed on a detected secret, and the file its deploy log named. Netlify says scanning covers repository code and build output and fails the build before publishing.
- Branch deploys
- The same for branch deploys. Whether SECRETS_SCAN_OMIT_KEYS, SECRETS_SCAN_OMIT_PATHS or SECRETS_SCAN_SMART_DETECTION_OMIT_VALUES exists, by key name only, and what each covers according to whoever set it.
- Record and keep
- Deploy IDs with their detection status, the file location from the log, and each SECRETS_SCAN_ key by name. Never the detected value, and never the value of any key.
6. Repository visibility and builds from outside the team
- Where to look
- The repository's visibility at your Git provider, Project configuration > Developer settings > Continuous deployment > Untrusted deploys policy, Team settings > Access & security > Visitor access > Auto-approve deploys from non-team members, and the project's deploy log visibility setting.
- Production
- Whether the repository is public or private and who can merge to the production branch. For a private repository, whether deploy requests from non-team members need approval or are auto-approved; Netlify's deploy overview says the options depend on the team's plan.
- Deploy Previews
- For a public repository, the untrusted deploys policy: "Require approval" (the default), "Build without sensitive variables" or "Build without restrictions". Netlify says fork builds run code you have not reviewed and can access your environment variables.
- Branch deploys
- Whether people outside the team can push branches that deploy. For a public repository, whether deploy logs are public or private.
- Record and keep
- Dated screenshots of each setting, and the Deploys tab entries with the status Pending review, Accepted or Rejected.
7. What can start a build
- Where to look
- Project configuration > Developer settings > Continuous deployment > Branches and deploy contexts, and the Build hooks list in the same section, which Netlify's build hooks page says displays each hook's name. Read names and branches only, without copying a hook or sharing the screen.
- Production
- The production branch, and whether auto publishing is on or a deploy is locked. Each build hook that builds the production branch, by name.
- Deploy Previews
- Whether Deploy Previews are on for new pull or merge requests, and whether agent runs are used on the project.
- Branch deploys
- Whether branch deploys are set to All, individual branches or None. Each build hook by name and default branch. Netlify treats deploys triggered by build hooks as trusted. On this page's reading, a hook URL works as a credential.
- Record and keep
- Hook names, branches and the service that calls each hook. Never the hook URL.
8. Functions in each context
- Where to look
- Cloud compute > Functions, with the list set to the published deploy, then a branch, then a Deploy Preview number, as Netlify's function logs page describes, and the function source in the repository.
- Production
- Each function with its path and method, and whether it checks the caller. Mark scheduled functions, which Netlify says run on their schedule only for published deploys and cannot be invoked by URL, and event functions such as formSubmitted or deploySucceeded.
- Deploy Previews
- The functions in one open Deploy Preview. Netlify says deployed functions are immutable, so a preview can run a version production no longer has. Note which Functions-scoped keys it reads and which context's values those are.
- Branch deploys
- The same for each branch deploy, and any function that exists only on a branch.
- Record and keep
- A table of function, path, context and the keys it reads. Do not press "Run now", which invokes the function.
9. Function logs
- Where to look
- Cloud compute > Functions, then each function's log, filtered by date and by text.
- Production
- The retention your plan gives, which Netlify's page puts at no less than 24 hours of function activity and 7 days on certain plans, and whether Log Drains (top plan) send logs to another service.
- Deploy Previews
- One recent invocation for each preview function: whether its lines hold tokens, keys, personal details or request bodies.
- Branch deploys
- One recent invocation for each branch deploy function, checked the same way.
- Record and keep
- Function, time and the field names of anything sensitive. Never the values.
10. Forms and stored submissions
- Where to look
- Forms and Forms > Form detection in the project, each form in the Active forms list and its Submissions page, and the form's HTML in the repository.
- Production
- Each form by name with its fields, any file upload field, and whether its Submissions page shows extra spam prevention (a honeypot field or reCAPTCHA 2) as enabled. Whether it collects personal information, and how often submissions are exported and deleted. Confirm no form collects card data, which the Acceptable Use Policy rules out.
- Deploy Previews
- Which forms exist in a Deploy Preview build, since detection parses each deploy's HTML, and any form that exists only in a preview.
- Branch deploys
- Which forms exist in each branch deploy, and any form that exists only on a branch.
- Record and keep
- Form names, field names, spam protection and how long submissions are kept. No submission content.
11. Form notifications and integrations (complete before row 12)
- Where to look
- Forms > Submission notifications, read from the list without opening a notification's edit form, the Netlify App for Slack, any Zapier, n8n or ChatGPT automation connected to the site, and functions with a formSubmitted handler.
- Production
- Each email, webhook and Slack notification with its form and recipient, and whether each recipient, channel, webhook destination and connected automation belongs to you or your business. Netlify says each email recipient must be a team member or an outside address that has confirmed it wants the notifications, a requirement it applies when a notification is created or edited.
- Deploy Previews
- For each notification and integration, what it does downstream: sends email, creates a CRM lead, adds a spreadsheet row, starts a deploy. Treat every one as live for row 12.
- Branch deploys
- Which integrations cover all forms on the site rather than a single form.
- Record and keep
- The full list with an owner for each. Record each webhook by its destination host only, never its full URL.
12. Synthetic submission (one submission, to a preview)
- Where to look
- One form on a Deploy Preview or branch deploy of your own site, opened in your own browser, once row 11 is complete. Go ahead only if every email recipient, Slack channel, webhook destination and connected automation row 11 lists belongs to you or your business; otherwise leave this row blank.
- Production
- Nothing is sent to production in this row. Record that it was left untouched.
- Deploy Previews
- Submit once with an invented name and message and an email address whose inbox you control. Netlify's troubleshooting page recommends a real email address instead of a fake one such as test@test.com, to avoid a test being flagged as spam. Treat every webhook and integration the form reaches as live. No file upload, no second submission, no load.
- Branch deploys
- If a branch deploy is used instead, the same limits apply. Record whether the submission appeared in the verified list, the spam list or neither.
- Record and keep
- Time sent, the deploy address, where the submission appeared, and every notification or integration that acted on it, compared with row 11. List anything it created elsewhere so the owner can remove it.
13. Deploy notifications and outgoing webhooks
- Where to look
- Project configuration > Notifications > Deploy notifications, which Netlify's deploy notifications page names, read from the list without opening a notification's edit form.
- Production
- Each notification by event and type. For each HTTP POST webhook, whether a JWS secret is set so the receiver can check X-Webhook-Signature, taken from whoever configured it where the list does not show it, and whether the receiver's code does check it.
- Deploy Previews
- GitHub pull request comments and commit statuses, which Netlify adds by default to new GitHub-connected sites with a link to the Deploy Preview. For a public repository, note that the link is readable on the pull request.
- Branch deploys
- Email notifications (Pro and the top plan) with their recipients, and deploy request notifications where untrusted deploys need approval. Any GitLab notification and whose personal access token it uses.
- Record and keep
- Event, type, destination host and whether it is signed. Never the JWS secret or the token.
14. Response headers by kind of address (one request each)
- Where to look
- From your own machine, curl -I sent once to each of five addresses on your own site: your main URL, one function or server-rendered path on it, one Deploy Preview, one branch deploy and one permalink. curl's man page says -I fetches the headers only.
- Production
- The security headers you expect, such as Strict-Transport-Security, Content-Security-Policy and X-Frame-Options, on the main URL, and whether the function or server-rendered path lacks them. Netlify says custom headers do not apply to URLs a function handles.
- Deploy Previews
- Whether the Deploy Preview response carries X-Robots-Tag: noindex, which Netlify says it adds to Deploy Previews, and whether its other headers match production.
- Branch deploys
- Whether the most recent deploy of the branch carries X-Robots-Tag: noindex. Netlify says it does not add it to the most recent deploy of a branch.
- Record and keep
- The header lines saved as text with the time sent, any Set-Cookie value removed. Five requests in total, no repeats and no load.
15. Header, redirect and proxy rules
- Where to look
- _headers and _redirects in the publish directory, the headers and redirects tables in netlify.toml, and the build command of each context.
- Production
- Each header rule with its path, and each redirect with its status and whether it is forced with an exclamation mark or force set to true. Every proxy rule (status 200 to another host) and whether it is signed.
- Deploy Previews
- Netlify says the headers and redirects tables cannot take context-specific settings. On this page's reading, a preview built from the same files proxies to the same hosts as production unless a build command changes the rules. Record each proxy target a preview reaches and whether it is a production backend.
- Branch deploys
- Any branch-deploy or branch-named build command that copies its own _headers file, and how those headers differ.
- Record and keep
- The rule list with each proxy target. For signed proxies, the variable name and whether its scope includes Runtime. Never its value.
16. Team members, two-factor sign-in and incident contacts
- Where to look
- Team settings > Members; each person's own User settings > Security > Two-factor authentication, read without selecting Enable or Disable; and Team settings > General > Primary Contacts, or the organisation settings where the team belongs to an organisation.
- Production
- The Owners, which Netlify requires at least one of, and the Developers with access to this project, who can change project visibility and Password Protection.
- Deploy Previews
- Reviewers and Git Contributors. Netlify's roles page says Git Contributors can open preview links that do not require a Netlify team login, SSO or other authentication they lack.
- Branch deploys
- Whether the team requires two-factor sign-in, which Netlify's user settings page ties to a Pro plan or higher, and whether a security incident contact is set.
- Record and keep
- The member list, dated, with each person's role and project access. Take out the names of people who are not part of the business before sharing it.
17. Audit log
- Where to look
- Team settings > Audit log, and the project's site audit log.
- Production
- Changes since the last review to visibility, Password Protection, environment variables, notifications and members, with who made each and when.
- Deploy Previews
- Changes to the settings read in rows 3 to 7, and who made them.
- Branch deploys
- Deploy deletions (Deploy deleted) and retention changes (Deploy retention has changed), which Netlify's manage deploys page says the team audit log records.
- Record and keep
- The filtered entries for the review period. Netlify lists the log on Pro and the top plan, with retention set by plan, and says variable changes made in netlify.toml are not captured in it.
18. Testing terms before any active test
- Where to look
- Netlify's Acceptable Use Policy, read on the day, and the terms of every service your functions, proxy rules and form integrations call.
- Production
- The policy's last-updated date. It allows security testing of your own sites and applications hosted on Netlify, provided the testing does not affect other users or Netlify's infrastructure.
- Deploy Previews
- Which context a test would target, whose values it carries (row 3), and which downstream services it would reach (rows 11 and 15).
- Branch deploys
- Netlify's own infrastructure needs Netlify's prior written permission to test, which the policy says may be requested at security@netlify.com. Record that no planned test targets it.
- Record and keep
- The policy URL and the date it was read, the owner's signed authorisation, and consent from each downstream service's owner.
What Netlify runs, and the deploy contexts it creates
Netlify security is easier to reason about once you count how many live copies of a site Netlify keeps.
For a project connected to a Git repository, Netlify builds the site from it, and its deploy overview describes every deploy as atomic: you always create a new deploy, and nothing goes live on the public URL until all of its changes are uploaded.
The production branch builds the site's main URL, and the deploy live there is the published deploy. A branch deploy is built from another branch and served at an address that starts with the branch name and two hyphens, such as staging--mysitename.netlify.app. A Deploy Preview is built from a pull request, a merge request or an agent run, at an address such as deploy-preview-42--mysitename.netlify.app.
Every successful deploy also gets a permalink that starts with its deploy ID, and Netlify says the content at that address never changes.
The predefined deploy contexts in Netlify's deploy overview are production, deploy-preview, branch-deploy, preview-server and dev, and a branch name can act as a context of its own. Each context can carry its own build command, environment variable values and plugin settings. Functions travel with the deploy: Netlify's functions overview says deployed functions are immutable, so a change on the production branch leaves the version inside a Deploy Preview or branch deploy as it was. Form detection, when it is switched on, parses each deploy's HTML for forms.
On this page's reading, one Netlify project is therefore several sites at once, each with its own code, functions and variable values and each reachable at its own address. The matrix on this page sets production, Deploy Previews and branch deploys side by side for each area, so an exposure shows up as a difference between columns.
Plan conditions come up in several places. Netlify's Password Protection page sets credit-based Free, Personal and Pro plans, where the UI uses project visibility, apart from Open Source plans, legacy (non-credit-based) plans and a plan Netlify's pages name after Pro, which this page calls the top plan.
The page says those plans keep the Password Protection settings. Every plan condition in this guide is as the cited Netlify page stated it on 15 November 2026. This guide stays with project and team settings.
What a framework does with a request belongs to guides such as the Next.js security guide, a key that has already leaked is the subject of the secrets exposure guide, and pipeline permissions are covered in the CI/CD security guide.
What Netlify says it secures, and what it leaves with the customer
Netlify's security page sets out what it calls a shared approach to cloud security.
It says customers are responsible for the security and compliance of their applications, including application architecture, data handling, response caching configuration, authentication mechanisms and TLS encryption, which it describes as enabled by default on Netlify. It says Netlify manages the security and compliance of the infrastructure, including encryption of data at rest and in transit within that infrastructure, vulnerability management, network security, and regular auditing and security testing of the infrastructure.
Netlify's documentation adds platform behaviour on top of that split. Its security overview says Netlify automatically detects distributed denial-of-service attacks and will rate limit and block malicious clients from connecting to sites on its servers. Its form submissions page says Netlify Forms automatically sanitises submissions, neutralising submitted code such as script tags.
Its Acceptable Use Policy draws a line around card data: Netlify Forms, Functions, logs and the other services it lists must not be used to collect, store, process or transmit payment card account data.
The settings in the rest of this guide are choices your own team makes: who may open a preview, which values a preview build receives, which forms send email where, and which backend a proxy rule points at. This page treats those choices as the place a review of your own account starts.
Who can open each deploy: visibility, passwords and team login
Netlify's deploy overview says preview URLs for Deploy Previews and branch deploys can be shared with anyone with the link unless password protection or team login protection is set up, and that Preview Server URLs need a Netlify login.
Which of those controls a project has depends on its plan.
Credit-based plans: project visibility
On credit-based Free, Personal and Pro plans, the Netlify UI replaces Password Protection with project visibility. A project is public, private or, on Pro only, protected by a shared password, and production deploys and previews are set separately. Private projects are enforced with Netlify login, and on Free and Personal plans Netlify says a private project can only be seen by the Team Owner.
Where a team starts depends on when it was created: Netlify's page says teams created on or after 28 July 2026 begin with Private for new projects, while teams created before then keep Public.
Netlify says making a project public exposes its production deploys to anyone or any bot that visits the URL, unless additional authentication was added, and that previews stay private unless their own visibility is changed too.
For integrations there is a limitation: Netlify says a private project cannot receive webhooks from services like Slack or Stripe.
Other plans: Password Protection
The top plan, Open Source and legacy plans keep Password Protection, which Netlify's page lists with basic password protection on all Pro plans and every option on the top plan. It can cover all deploys, or only Deploy Previews and branch deploys, and the page adds that protecting only "private deploys" with Password Protection settings is only available on the top plan.
Basic password protection shows a generic prompt and admits anyone who knows the shared password. Team login protection asks for a Netlify team login, and Netlify says it applies to Developers, Team Owners and Billing Admins only, so Git Contributors cannot sign in to deploys protected this way.
Team login can use single sign-on through an identity provider, in which case Netlify says the authorisation lasts for 1 hour.
A Developer can change a site's Password Protection at any time, and a site's own settings override the default a Team Owner sets for the team.
Search engines are a separate question
Netlify adds an X-Robots-Tag: noindex header to Deploy Previews and older branch deploys, but not to the most recent deploy of each branch, so an address like staging--mysitename.netlify.app can be crawled and indexed if a search engine finds it.
Netlify adds that the header is no assurance that preview URLs will stay protected or out of search results, and recommends a private project, which is a credit-based plan setting, or Password Protection for non-production deploys. The header is aimed at search engines.
Who can open the page is a separate setting: Netlify's deploy overview says preview links can be shared with anyone with the link unless password protection or team login protection is set up.
Permalinks, retention and old deploys that keep answering
Every successful deploy Netlify still holds has an address of its own.
Its manage deploys page says Netlify versions all deploys and that any deploy can be browsed on the Deploys tab and previewed from a unique URL. A Deploy Preview stays available until it is deleted, automatically or by a Developer or Team Owner. By default Netlify deletes deploys after 30 days, or 90 days on paid plans, but it does not automatically delete the published deploy, the most recent successful production deploy or the most recent successful deploy of each branch. On the top plan, Owners and Developers can adjust the retention period up to 365 days.
Old deploys are worth listing for a further reason. Netlify's functions overview says deployed functions are immutable, and its page on functions and environment variables says each deploy, Deploy Previews and branch deploys included, uses the variable values that were set when it was deployed.
On this page's reading, a permalink from last month can still run last month's functions with last month's values, including a credential you have since replaced in the settings, until that deploy is deleted.
Netlify mentions removing sensitive data as one reason to delete a deploy. Deletion needs a Developer or Team Owner, is permanent, takes away the deploy's URLs, deploy logs and the functions unique to it, and is logged in the team audit log as Deploy deleted. The deploy most recently published to the main URL cannot be deleted. The matrix lists old deploys and leaves any deletion to the owner.
Environment variables: contextual values, scopes and secrets
A Netlify environment variable has a key, one or more scopes and one or more contextual values.
Netlify's overview says that by default a variable is available to all scopes and has the same value in every deploy context. On this page's reading, that default is the first thing to check: unless someone set separate values, a Deploy Preview build and its functions receive the same value as production for every key they can read.
Separate values can be set for Production, Deploy Previews, Branch deploys, Preview server and Local development, and a Branch value can target one branch or a prefix such as release/*. Netlify says a Branch value is also used for the permalinks, Deploy Previews and branch deploys of that branch.
Scopes, which Netlify lists on Pro and the top plan, narrow where a value goes: Builds; Functions, which covers Functions, Edge Functions, Netlify Server and On-demand Builders; Runtime, which covers forms and signed proxy redirects; and Post processing, which covers snippet injection.
Values in netlify.toml, and shared team variables
Variables can also be declared per context in netlify.toml. Netlify's environment variable pages note that the file is stored in your repository, that variables declared there cannot be given scopes and take the Builds and Post processing scope, that they are not available to serverless functions, and that their changes are not captured in the team audit log.
A netlify.toml value also overrides a UI value that has the same key. Shared variables, on Pro and the top plan, reach every site in the team, and only Team Owners can read and edit their values.
On credit-based plans, Netlify sets the variables for common AI model providers automatically unless you supply your own keys. This page counts those in the inventory too.
Secret values and secret scanning
Marking a variable "Contains secret values" puts it under Netlify's Secrets Controller policy. A secret value is write-only once saved, has to be set for explicit deploy contexts and scopes, cannot take the post processing scope, and cannot have its flag removed. Only code running on Netlify's systems, such as functions and the build, reads the unmasked value.
The exception is the dev context: Netlify says a value set there does not have the policy applied, and that only the dev-context value is unmasked in the UI, CLI and API.
Flagging a value also switches on secret scanning from the next build. Scanning searches repository code and build output for the value in plaintext, base64-encoded and URI-encoded form, and only searches for secret values longer than four characters that are not booleans. If it finds one, it fails the build and writes the location to the deploy log.
Smart detection, on Personal, Pro and the top plan, looks for potential secrets without any flag. Both can be narrowed or switched off with variables of their own: SECRETS_SCAN_ENABLED set to false disables all scanning, SECRETS_SCAN_SMART_DETECTION_ENABLED set to false turns off smart detection alone, SECRETS_SCAN_OMIT_KEYS and SECRETS_SCAN_OMIT_PATHS exclude keys and paths, and SECRETS_SCAN_SMART_DETECTION_OMIT_VALUES safelists strings.
Each of these has a line in the secret-exposure review, because an exclusion added to quiet one false alarm keeps applying until someone removes it.
Values that end up in the browser
Scanning looks for values; it does not decide what a framework copies into the page. Netlify's framework page says sensitive values should not be copied into the build, because they are accessible to anyone inspecting the app files in the browser, and lists prefixes such as NEXT_PUBLIC_, GATSBY_ and REACT_APP_ that most frameworks require for a variable used inside the site.
It calls a function that reads the value at runtime the best option for keeping a sensitive value out of view. What to do once a key has been exposed is the subject of the secrets exposure guide.
Public repositories, forks and who can start a build
Repository visibility changes who can make Netlify build.
For a project connected to a public repository, Netlify's deploy overview says anyone who opens a pull request from a fork can produce a Deploy Preview, that those builds run code you have not reviewed and can access your environment variables, and that deploys from outside your Netlify team are always treated as untrusted. The untrusted deploys policy, available only for public repositories, decides what happens to them:
- "Require approval", the default: a team member with access to the project approves each untrusted deploy before it builds.
- "Build without sensitive variables": untrusted deploys build automatically, without the variables Netlify identifies as sensitive. Netlify always counts a variable marked "Contains secret values", and for other variables attempts to detect a secret from names such as PASSWORD, TOKEN, SECRET or API_KEY and from values in known credential formats. It says that detection is based on heuristics, and that to make sure a value is always treated as sensitive it is best to mark it.
- "Build without restrictions": untrusted deploys build like any other Deploy Preview, with every variable present. Netlify says to choose it only if you are comfortable potentially revealing your environment variables publicly.
Private repositories and trusted triggers
For private repositories, Netlify's Deploy Request Policy builds only changes from recognised authors, which Netlify says include Owners, Developers and Git Contributors, with bots from GitHub Marketplace also treated as recognised. When a non-team member merges a pull request that triggers a build, the deploy waits with the status Pending approval, and depending on the team's plan a Team Owner can require approval for every such request or auto-approve them. Build hooks sit outside the policy, and Netlify treats the deploys they trigger as trusted.
The repository decides a little more. Netlify says deploy logs for a site linked to a private repository are available to all site members, and that for a public repository you can control deploy log visibility. And netlify.toml lives in the repository, so on this page's reading every value it holds can be read by anyone who can read the repository, which for a public one is anyone. How CI services treat forks and pipeline tokens in general is covered in the CI/CD security guide.
Netlify Functions in every deploy context
Netlify's functions guides show a function answering at the path its config sets, such as /hello on the site's domain, and its functions overview says functions are version-controlled, built and deployed with the rest of the site.
Because deployed functions are immutable, each Deploy Preview and branch deploy carries its own copy, and the Functions list can be filtered to a branch or a Deploy Preview number to show it. On this page's reading, every preview address is one more place a function answers, behind whatever access controls the project applies to that deploy, such as visibility or Password Protection, plus any check the function makes on its caller itself.
What a preview's function can reach depends on its variables. On plans with scopes, a key needs the Functions scope to be readable at runtime, netlify.toml values are not available to functions, and of Netlify's read-only variables only URL, SITE_NAME and SITE_ID are available to them. On this page's reading, a function in a Deploy Preview reads the Deploy Preview value of each key, and by default that is the production value.
Team login protection and private projects add a useful signal: Netlify says functions and edge functions can then identify who made each request through context.user.
- Scheduled functions run on their schedule only for published deploys, and Netlify says they cannot be invoked directly with a URL. A "Run now" button on the Functions page invokes one, which is an action rather than a check, so the matrix leaves it alone.
- Event functions run on platform events, such as formSubmitted when a form submission is verified, or deploySucceeded. Netlify signs each platform event with a JSON web signature and verifies it before invoking the function, to prevent external requests.
- Netlify's function logs page says logs cover the published deploy, branch deploys and Deploy Previews, include console.log output, and are kept for at least 24 hours of function activity, rising to 7 days on certain plans. Log Drains, on the top plan, can send them to another service.
Where the function itself takes over
Whether a function checks who is calling, and what it returns to each kind of caller, is application code rather than a Netlify setting. The API security guide covers testing that; the matrix records which functions exist in which context and which values each one can read.
Netlify Forms: what is stored, and who hears about it
Netlify Forms works once form detection is on: the build parses each deploy's HTML for forms marked with a netlify or data-netlify attribute and handles their submissions.
Submissions appear in the Forms tab, where Netlify lists verified submissions by default and keeps the ones Akismet flags in a separate spam list. A honeypot field or a reCAPTCHA 2 challenge can be added, and Netlify rejects submissions that fail either outright, so they never reach the spam list.
Netlify says submission data is stored in its user database, and recommends that a form collecting personal information be managed by exporting submissions and deleting them regularly. Uploaded files are linked from the submission details, email notifications, CSV exports and the API, and after a form is deleted its uploads stay available by direct URL for 24 hours.
For uploads that contain personal information, Netlify recommends the Very Good Security integration, and its Acceptable Use Policy rules out payment card data in Forms altogether.
Notifications and integrations
Form notifications go to email, webhooks or a Slack workspace, for verified submissions to one form or to every form on the site. Netlify says each email recipient must be an active member of your Netlify team or an outside address that has confirmed it wants the notifications, that the requirement applies when a notification is created or edited, and, when its page was read on 15 November 2026, that confirmation was rolling out to teams gradually and might not yet be available for every team.
Beyond notifications, Netlify's pages describe a Zapier Zap triggered by a verified submission, n8n workflows built on its Netlify Trigger node, ChatGPT automations subscribed to form submission events, and functions with a formSubmitted handler, which fires when a submission is verified.
Netlify's own Zapier examples include creating Salesforce leads and Mailchimp subscribers from new submissions. On this page's reading, a submission can therefore change records well outside Netlify.
What the documentation leaves open about previews
The Netlify form pages read for this guide do not say whether a submission made on a Deploy Preview or branch deploy is listed with production's submissions, or whether it sets off the same notifications. The synthetic submission in the matrix answers that for your own site, with one invented record sent to a preview, after every notification and integration on the form has been listed and treated as live, and only where every email recipient, Slack channel, webhook destination and connected automation on that list belongs to you or your business.
Deploy notifications and outgoing webhooks
Deploy notifications, set in the project's notification settings, report events such as a deploy starting, succeeding, failing, being deleted or being locked, and an untrusted deploy request waiting, accepted or rejected.
Netlify lists email notifications on Pro and the top plan. An HTTP POST notification is an outgoing webhook carrying a JSON copy of the event, and if you give it a JWS secret, Netlify signs each request and sends the signature in the X-Webhook-Signature header, with iss set to netlify and a sha256 of the payload.
On this page's reading, the signature is what lets a receiver tell Netlify's notification from a forged one, so the matrix records whether each receiver checks it.
Netlify's deploy notifications page says GitHub commit statuses, pull request comments and commit checks are added to every new GitHub-connected site by default, and the pull request comment links to the Deploy Preview once it is ready. In a public repository, that comment can be read by anyone who can read the pull request, which is one more reason the preview's visibility setting matters.
GitLab notifications use a personal access token with the api scope, a credential the matrix records by name and owner only.
Custom headers, redirects and proxies
Headers come from a _headers file in the publish directory or headers tables in netlify.toml, and the limitations on Netlify's headers page decide what they cover.
Custom headers apply only to files Netlify serves from its own backing store, so a proxied response, or a URL handled by a function or edge function such as a server-rendered page, gets none of them, and Netlify says the function or proxied site should return any required headers.
And the rules are global for all builds: they cannot be scoped to a branch or deploy context, except by a build command that copies a different file into _headers for that context. Netlify also lists header names whose custom values are typically ignored, Set-Cookie among them, which it says may be overridden by Netlify cookie handling, and because netlify.app is on the Public Suffix List, a cookie can only be shared across subdomains on a custom domain.
Redirects follow the same pattern: a _redirects file or redirects tables in netlify.toml, with _redirects read first and the first matching rule winning, and Netlify's configuration reference says the redirects and headers tables, unlike keys such as build and plugins, cannot take context-specific settings.
A rule with status 200 is a rewrite, and a rewrite can proxy a path such as /api/* to another service straight from Netlify's CDN servers. On this page's reading, a Deploy Preview built from the same files proxies to the same backend as production, so a preview's /api/ path reaches whatever service production's rule points at unless a build step changes the rules.
- Shadowing: by default a rewrite does not replace a file that exists at the path. Appending an exclamation mark to the rule, or setting force to true in netlify.toml, makes it apply anyway.
- Signed proxy redirects, which must be set in netlify.toml: Netlify sends a JWS in an x-nf-sign header to the non-Netlify site on every proxied request, signed with a secret from an environment variable whose scope, where scopes can be set, must include Runtime. The signed document includes deploy_context. On this page's reading, a receiving service that checks it can tell a preview's request from production's.
- Custom headers added to a proxy rule in netlify.toml apply to the request Netlify sends on, not to the response your visitor receives.
- Netlify says paths handled by proxies or functions may not redirect from HTTP to HTTPS as expected, and recommends publishing only HTTPS URLs for them.
Checking what each address sends
Because header rules do not reach functions and proxies, the matrix reads the headers each kind of address actually returns, with one request per address. Choosing which security headers to send is outside this guide; the security misconfiguration guide covers headers that are set in one layer and missing in another.
Who is on the team, two-factor sign-in and the audit log
Netlify's roles page lists Owners, Developers, Publishers, Internal Builders, Git Contributors, Reviewers and Billing Admins, with role options varying by plan, and every team must have at least one Owner.
Owners and Developers can access and edit project configuration and change project visibility, and an Owner chooses which projects Developers, Publishers, Internal Builders and Reviewers can reach. Git Contributors have no access to the Netlify platform beyond triggering a deploy and opening preview links, and can open Deploy Preview and branch deploy links that do not require a Netlify team login, SSO or other authentication they lack.
Reviewers share feedback on previews through the Netlify Drawer, which Netlify's deploy overview says is on by default for Deploy Previews, and the roles page says a team on a credit-based plan needs Pro or higher to invite a Reviewer.
Two-factor sign-in is set per person in user settings, and Netlify's user settings page says that on a Pro plan or higher, an Owner of the team or of its parent organisation may encourage or require it. Netlify's security overview also asks a Team Owner to add at least one email address as a primary contact for security, abuse or fraud incidents, so Netlify can reach the team. A team that belongs to an organisation adds that contact in the organisation settings instead.
The team audit log, on Pro and the top plan, records actions by team members, filtered into team events and project events, and each project also has a site audit log. Netlify says how far back the log reaches depends on plan. Environment variable changes made in the UI, CLI or API, deploy deletions and changes to deploy retention all appear in it.
On this page's reading, that makes the log the place to look for what changed between two reviews, apart from changes to variables in netlify.toml, which Netlify says the log does not capture.
What Netlify's Acceptable Use Policy says about security testing
Netlify's Acceptable Use Policy, which showed a last-updated date of 4 November 2026 when read on 15 November 2026, applies to all use of the Netlify Services and website.
It says users must not attempt to undermine the security or integrity of computing systems or networks of Netlify, its partners or any other person, including attempting unauthorised access, vulnerability exploitation, or scanning or probing of systems. It then says users may perform security testing of their own sites and applications hosted on Netlify, provided the testing does not affect other users or Netlify's infrastructure, and that testing Netlify's own infrastructure requires Netlify's prior written permission, which may be requested at security@netlify.com.
The same policy says users must not interfere with or disrupt the Netlify Services, or create an undue burden on the website or the networks or services connected to it, and must not perform benchmark tests or analyses relating to Netlify Services without Netlify's express permission.
It also says users must not access the Netlify Services or website through automated means, such as scraping, crawling or generating automated searches or queries, other than through Netlify's API, CLI, SDKs, MCP server, Agent Runners and other documented integrations.
Netlify may update the policy on at least 30 days' notice. This page's advice is to read it on the day and record the date.
The policy speaks for Netlify only. A function, proxy rule or form integration can carry a test's requests on to a payment provider, a CRM or your own API, each with an owner and terms of its own. This page's advice is to list those downstream services before any active test and get each owner's consent, and to keep the synthetic submission in the matrix to a single record on a preview: one ordinary use of your own form, not a test of Netlify.
How to work through the deploy-context exposure matrix
Keep a separate copy for each project and work down the rows with the project open in the Netlify UI, signed in as someone whose role can read every setting.
Fill each column from what that context actually does. Where your plan lacks a control, write the plan and the Netlify page that says so in the cell, so that an empty cell never stands for a check nobody made.
- Rows 1, 12 and 14 touch a live deploy, always one of your own. Row 1 is one page view per kind of address in a private browser window, row 12 is a single form submission to a preview, and row 14 sends one header request to each of five addresses, with no repeats and no load. Every other row reads a setting, a list, a file, a log or a policy page.
- Rows 3 to 5 are the secret-exposure review. Record that a variable exists, its scopes, the contexts it reaches and whether it is flagged as secret. Read key names from the filtered list without expanding a variable, and leave the clipboard copy and netlify env:list alone: Netlify's page describes the clipboard copy and env:list --plain as ways to export variables in .env format.
- Never put a build hook URL, a shared password, a webhook secret, a personal access token or a variable value in the matrix. Write that it exists, what uses it and who can manage it.
- Where a row reads a file or log that can hold a secret, such as netlify.toml, a deploy log or a function log, record whether a secret is present and where, never its value, and keep the file off shared screens.
- Put a date on each screenshot. Before a copy goes to anyone outside the team, take out the names of people who are not part of the business.
- Repeat the review after a plan change, a new team member or Reviewer, a repository going public, a new form integration, or any change to visibility or Password Protection.
Running the synthetic submission
Row 12 is the only row that creates a record, so it carries its own limits. Finish row 11 first: list every email, webhook and Slack notification on the form, every Zapier, n8n or ChatGPT automation connected to the site and every function with a formSubmitted handler, and treat each one as live.
Go ahead only if every email recipient, Slack channel, webhook destination and connected automation on that list belongs to you or your business; if one reaches a client or anyone else, leave the row blank. Then open one form on a Deploy Preview or branch deploy of your own site and submit it once, with an invented name and message and an email address whose inbox you control.
Netlify's troubleshooting page says test submissions can be flagged as spam, and recommends a real email address over a fake one such as test@test.com.
Attach no file, submit only once and leave production alone. Afterwards, record where the submission appeared and which notifications and integrations acted on it, and list anything it created in another system so the owner can remove it.
What a review of your own Netlify project cannot show
What the matrix captures is configuration, plus a few responses from your own deploys.
It shows which addresses need a login, which builds receive which values, which forms send data where and which backends a proxy rule reaches. It does not show what a function does with a request that gets through: whether it checks who owns a record, returns more than the screen needs, or trusts a value the browser sent.
Nor does a clean secret scan settle the question, since Netlify describes scanning as searching for the values of flagged variables and, with smart detection, for potential secrets.
On this page's reading, a key that is neither flagged nor recognised by smart detection sits outside what either scan is described as finding.
The review also covers only what Netlify's shared approach assigns to customers. Netlify says it audits and security-tests its own infrastructure, and its security overview points to the Trust Center for compliance documents, some of which need an approved access request and an executed NDA before download. Assurance about the infrastructure has to come from Netlify's own documents; reading your settings cannot supply it.
And it is a snapshot. A function log holds only what its retention period keeps, any setting can be changed after you read it, and on plans that include it, the team audit log is the place to look for that change.
Where a Clever Ops assessment fits
This page is for information.
Netlify's own platform is not something Clever Ops tests: the Clever Ops methodology keeps a host's platform outside its method, and Netlify's Acceptable Use Policy requires Netlify's prior written permission for testing its own infrastructure.
Your own application on Netlify is another matter. If it is a custom web application or API, such as a Next.js, React or Node app, the matching Clever Ops service is the web application and API penetration test, whose scope asks for two test accounts in each role. Any active testing of your own application on Netlify takes place within that scoped assessment.
No request is sent until each target's owner has signed an authorisation and the host's testing policy has been checked. While testing runs, the request rate stays within an agreed limit, and work on a target pauses if a firewall starts blocking or your contact asks for a pause.
For a brochure or marketing site, the website security check is an external review of what anyone on the internet can see without logging in, including certificates and transport security and security headers.
Clever Ops will ask you to name the exact targets before testing, meaning domains, subdomains and API addresses, along with anything to be left alone. A finished matrix already names every address in each context, the previews that carry production values, and the services behind each form and proxy rule.
Load or denial-of-service work is not something Clever Ops takes on. A load-testing specialist handles it, once your host has given written approval. Where Clever Ops wrote or hosts the application itself, the engagement is called a security review instead of an independent penetration test, and its report records who built the application and who hosts it.
Clever Ops does not offer round-the-clock monitoring or emergency incident response. Should a key or the team account look misused, go to Netlify and an incident response specialist before anything else.
Frequently asked questions
It depends on the plan and the project's settings. Netlify's deploy overview says preview URLs for Deploy Previews and branch deploys can be shared with anyone with the link unless password protection or team login protection is set up. On credit-based plans, project visibility sets previews separately from production, and Netlify says teams created on or after 28 July 2026 start with new projects private while earlier teams keep a public default. Netlify adds an X-Robots-Tag: noindex header to Deploy Previews, and says that header is no assurance they stay protected or out of search results.
By default they get the same values. Netlify's environment variables overview says a variable has the same value for all deploy contexts unless you set different ones. You can give a key its own value for Deploy Previews, Branch deploys or a named branch, in the UI, CLI, API or netlify.toml. For projects on public repositories, the untrusted deploys policy decides whether a Deploy Preview from a fork by someone outside the team waits for approval, builds without sensitive variables, or builds with every variable present.
Netlify's Secrets Controller page says a variable marked "Contains secret values" is write-only once saved, and that only code running on Netlify's systems, such as functions and the build, reads the unmasked value. The flag cannot be removed, and the variable cannot take the post processing scope. The dev context is the exception, because its value is not covered by the policy. A value your build copies into the site's files is a separate matter: Netlify says such values are accessible to anyone inspecting the app files in the browser.
No. Netlify's headers page says custom headers apply only to files Netlify serves from its own backing store, so a proxied response or a URL handled by a function or edge function, such as a server-side rendered page, does not receive them, and the function or proxied site should return its own. The rules in _headers and netlify.toml are also global for all builds, and Netlify documents a build-command workaround for giving one deploy context different headers.
Netlify's Acceptable Use Policy, last updated 4 November 2026, says users may perform security testing of their own sites and applications hosted on Netlify, provided the testing does not affect other users or Netlify's infrastructure. Testing Netlify's own infrastructure needs Netlify's prior written permission, which the policy says may be requested at security@netlify.com. The policy also rules out creating an undue burden on the website or the networks or services connected to it, benchmark tests without express permission, and automated access to the Netlify Services or website outside Netlify's documented integrations. Services your site calls, such as a payment provider or a CRM, have owners and terms of their own.
Submissions appear in the site's Forms tab, verified ones by default and those Akismet flags in a spam list, and Netlify says submission data is stored in its user database. Notifications for verified submissions can go to email, webhooks or Slack, and Netlify says each email recipient must be a team member or an outside address that has confirmed it wants them, a requirement it applies when a notification is created or edited. Submissions can also feed a Zapier Zap, an n8n workflow or a function with a formSubmitted handler.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.