[Docs] Remove app security survey (cloudflare#25327)

db-cloudflare · web-flow · commit ba9783b41c37 · 2025-09-22T17:52:07.000+01:00
diff --git a/src/content/docs/api-shield/get-started.mdx b/src/content/docs/api-shield/get-started.mdx
@@ -9,7 +9,6 @@ sidebar:
 
 import { GlossaryTooltip, Render, Steps } from "~/components"
 
-<Render file="survey" product="waf" />
 
 This guide will help you set up API Shield to identify and address API security best practices.
 
diff --git a/src/content/docs/api-shield/index.mdx b/src/content/docs/api-shield/index.mdx
@@ -11,7 +11,6 @@ head:
 
 import { Description, Feature, Plan, RelatedProduct, Render } from "~/components"
 
-<Render file="survey" product="waf" />
 
 <Description>
 Identify and address your API vulnerabilities.
diff --git a/src/content/docs/api-shield/management-and-monitoring/endpoint-management/index.mdx b/src/content/docs/api-shield/management-and-monitoring/endpoint-management/index.mdx
@@ -9,8 +9,6 @@ sidebar:
 
 import { GlossaryTooltip, Plan, Steps, Tabs, TabItem, Render } from "~/components"
 
-<Render file="survey" product="waf" />
-
 <Plan type="all" />
 
 Monitor the health of your <GlossaryTooltip term="API endpoint">API endpoints</GlossaryTooltip> by saving, updating, and monitoring performance metrics using API Shield’s Endpoint Management.
diff --git a/src/content/docs/api-shield/security/index.mdx b/src/content/docs/api-shield/security/index.mdx
@@ -6,9 +6,8 @@ sidebar:
 
 ---
 
-import { DirectoryListing, Render } from "~/components"
+import { DirectoryListing } from "~/components"
 
-<Render file="survey" product="waf" />
 
 Cloudflare offers the following features to help secure your APIs:
 
diff --git a/src/content/docs/api-shield/security/jwt-validation/index.mdx b/src/content/docs/api-shield/security/jwt-validation/index.mdx
@@ -8,7 +8,6 @@ sidebar:
 
 import { GlossaryTooltip, Steps, Tabs, TabItem, Render } from "~/components"
 
-<Render file="survey" product="waf" />
 
 <GlossaryTooltip term="JSON web token (JWT)">JSON web tokens (JWT)</GlossaryTooltip> are often used as part of an authentication component on many web applications today. Since JWTs are crucial to identifying users and their access, ensuring the token’s integrity is important.
 
diff --git a/src/content/docs/api-shield/security/schema-validation/index.mdx b/src/content/docs/api-shield/security/schema-validation/index.mdx
@@ -6,9 +6,8 @@ sidebar:
 
 ---
 
-import { GlossaryDefinition, GlossaryTooltip, Plan, Steps, Tabs, TabItem, Render } from "~/components"
+import { GlossaryDefinition, GlossaryTooltip, Plan, Steps, Tabs, TabItem } from "~/components"
 
-<Render file="survey" product="waf" />
 
 <Plan type="all" />
 
diff --git a/src/content/docs/bots/bot-analytics.mdx b/src/content/docs/bots/bot-analytics.mdx
@@ -10,8 +10,6 @@ head:
 
 import { GlossaryTooltip, Render } from "~/components";
 
-<Render file="survey" product="waf" />
-
 ## Business and Enterprise
 
 Business and Enterprise customers without Bot Management can use **Bot Analytics** to dynamically examine bot traffic. These dashboards offer less functionality than Bot Management for Enterprise but still help you understand bot traffic on your domain.
diff --git a/src/content/docs/bots/get-started/bot-fight-mode.mdx b/src/content/docs/bots/get-started/bot-fight-mode.mdx
@@ -11,8 +11,6 @@ head:
 
 import { Tabs, TabItem, Steps, Render } from '~/components';
 
-<Render file="survey" product="waf" />
-
 Bot Fight Mode is a simple, free product that helps detect and mitigate bot traffic on your domain. When enabled, the product:
 
 - Identifies traffic matching patterns of known bots
diff --git a/src/content/docs/bots/get-started/bot-management.mdx b/src/content/docs/bots/get-started/bot-management.mdx
@@ -11,8 +11,6 @@ learning_center:
 
 import { Tabs, TabItem, Steps, Render } from '~/components';
 
-<Render file="survey" product="waf" />
-
 Bot Management for Enterprise is a paid add-on that provides sophisticated bot protection for your domain. Customers can identify automated traffic, take appropriate action, and view detailed analytics within the dashboard.
 
 This Enterprise product provides the most flexibility to customers by:
diff --git a/src/content/docs/bots/get-started/super-bot-fight-mode.mdx b/src/content/docs/bots/get-started/super-bot-fight-mode.mdx
@@ -11,7 +11,6 @@ head:
 
 import { Render, Tabs, TabItem, Steps } from "~/components"
 
-<Render file="survey" product="waf" />
 
 Super Bot Fight Mode is included in your Pro, Business, or Enterprise subscription. When enabled, the product:
 
diff --git a/src/content/docs/bots/index.mdx b/src/content/docs/bots/index.mdx
@@ -10,8 +10,6 @@ head:
 
 import { CardGrid, Description, Feature, LinkTitleCard, Plan, RelatedProduct, Render } from "~/components"
 
-<Render file="survey" product="waf" />
-
 <Description>
 
 Identify and mitigate automated traffic to protect your domain from bad bots. 
diff --git a/src/content/docs/ddos-protection/advanced-ddos-systems/concepts.mdx b/src/content/docs/ddos-protection/advanced-ddos-systems/concepts.mdx
@@ -10,8 +10,6 @@ head:
 
 import { GlossaryTooltip, Render } from "~/components";
 
-<Render file="survey" product="waf" />
-
 ## Prefixes
 
 Advanced DDoS Protection protects the IP prefixes you select from sophisticated DDoS attacks. A prefix can be an IP address or an IP range in CIDR format. You must add prefixes to Advanced DDoS Protection so that Cloudflare can analyze incoming <GlossaryTooltip term="data packet">packets</GlossaryTooltip> and offer protection against sophisticated TCP DDoS attacks.
diff --git a/src/content/docs/ddos-protection/get-started.mdx b/src/content/docs/ddos-protection/get-started.mdx
@@ -6,9 +6,7 @@ sidebar:
 
 ---
 
-import { Steps, Render } from "~/components"
-
-<Render file="survey" product="waf" />
+import { Steps } from "~/components"
 
 ## Free, Pro, and Business plans
 
diff --git a/src/content/docs/ddos-protection/index.mdx b/src/content/docs/ddos-protection/index.mdx
@@ -8,9 +8,7 @@ head:
     content: Overview
 ---
 
-import { Description, Feature, FeatureTable, GlossaryTooltip, Plan, RelatedProduct, Render } from "~/components"
-
-<Render file="survey" product="waf" />
+import { Description, Feature, FeatureTable, GlossaryTooltip, Plan, RelatedProduct } from "~/components"
 
 <Description>
 
diff --git a/src/content/docs/page-shield/detection/index.mdx b/src/content/docs/page-shield/detection/index.mdx
@@ -9,8 +9,6 @@ head: []
 description: Learn more about Page Shield's detection features.
 ---
 
-import { DirectoryListing, Render } from "~/components";
-
-<Render file="survey" product="waf" />
+import { DirectoryListing } from "~/components";
 
 <DirectoryListing />
diff --git a/src/content/docs/page-shield/get-started.mdx b/src/content/docs/page-shield/get-started.mdx
@@ -11,8 +11,6 @@ description: Learn how to get started with client-side resource monitoring.
 
 import { Tabs, TabItem, Render, Steps } from "~/components";
 
-<Render file="survey" product="waf" />
-
 ## Activate client-side resource monitoring
 
 To enable client-side resource monitoring:
diff --git a/src/content/docs/page-shield/how-it-works/index.mdx b/src/content/docs/page-shield/how-it-works/index.mdx
@@ -10,9 +10,7 @@ description: Page Shield tracks resources (such as scripts) loaded by your
   malicious resources.
 ---
 
-import { GlossaryTooltip, Render } from "~/components";
-
-<Render file="survey" product="waf" />
+import { GlossaryTooltip } from "~/components";
 
 Page Shield helps manage client-side resources loaded by your website visitors, including scripts, their connections, and [cookies](https://www.cloudflare.com/learning/privacy/what-are-cookies/). It can trigger alert notifications when resources change or are considered malicious.
 
diff --git a/src/content/docs/page-shield/index.mdx b/src/content/docs/page-shield/index.mdx
@@ -11,9 +11,7 @@ description: Page Shield is a comprehensive client-side security and privacy
   browsing environment.
 ---
 
-import { Description, Feature, FeatureTable, Plan, Render } from "~/components";
-
-<Render file="survey" product="waf" />
+import { Description, Feature, FeatureTable, Plan } from "~/components";
 
 <Description>
 
diff --git a/src/content/docs/page-shield/policies/index.mdx b/src/content/docs/page-shield/policies/index.mdx
@@ -7,9 +7,7 @@ description: Use Page Shield policies to define the resources (scripts) allowed
   on your applications.
 ---
 
-import { GlossaryTooltip, Render } from "~/components";
-
-<Render file="survey" product="waf" />
+import { GlossaryTooltip } from "~/components";
 
 :::note
 Only available to Enterprise customers with a paid add-on.
diff --git a/src/content/docs/security/index.mdx b/src/content/docs/security/index.mdx
@@ -16,10 +16,8 @@ import {
 	LinkTitleCard,
 	RelatedProduct,
 	Stream,
-	Render,
 } from "~/components";
 
-<Render file="survey" product="waf" />
 
 The application security dashboard is your starting point to better understand the security posture of your web applications, and to configure rules to protect them.
 
diff --git a/src/content/docs/waf/account/custom-rulesets/index.mdx b/src/content/docs/waf/account/custom-rulesets/index.mdx
@@ -4,9 +4,6 @@ title: Custom rulesets
 sidebar:
   order: 2
 ---
-import { Render } from "~/components";
-
-<Render file="survey" product="waf" />
 
 :::note
 This feature requires an Enterprise plan with a paid add-on.
diff --git a/src/content/docs/waf/account/index.mdx b/src/content/docs/waf/account/index.mdx
@@ -6,9 +6,6 @@ sidebar:
   group:
     label: Account-level configuration
 ---
-import { Render } from "~/components";
-
-<Render file="survey" product="waf" />
 
 :::note
 This feature requires an Enterprise plan with a paid add-on.
diff --git a/src/content/docs/waf/account/managed-rulesets/index.mdx b/src/content/docs/waf/account/managed-rulesets/index.mdx
@@ -7,8 +7,6 @@ sidebar:
 
 import { Render, Tabs, TabItem, Details, APIRequest } from "~/components";
 
-<Render file="survey" product="waf" />
-
 :::note
 This feature requires an Enterprise plan with a paid add-on.
 :::
diff --git a/src/content/docs/waf/account/rate-limiting-rulesets/index.mdx b/src/content/docs/waf/account/rate-limiting-rulesets/index.mdx
@@ -5,9 +5,7 @@ sidebar:
   order: 3
 ---
 
-import { GlossaryTooltip, Render } from "~/components";
-
-<Render file="survey" product="waf" />
+import { GlossaryTooltip } from "~/components";
 
 A rate limiting rule defines a <GlossaryTooltip term="rate limiting">rate limit</GlossaryTooltip> for requests matching an expression, and the action to perform when that rate limit is reached. At the account level, rate limiting rules are always grouped into rate limiting rulesets, which you then deploy.
 
diff --git a/src/content/docs/waf/analytics/index.mdx b/src/content/docs/waf/analytics/index.mdx
@@ -7,9 +7,7 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing, Render} from "~/components";
-
-<Render file="survey" product="waf" />
+import { DirectoryListing } from "~/components";
 
 Refer to the following pages for more information on the available analytics dashboards for Cloudflare security products:
 
diff --git a/src/content/docs/waf/concepts.mdx b/src/content/docs/waf/concepts.mdx
@@ -7,8 +7,6 @@ sidebar:
 
 import { GlossaryTooltip, Render } from "~/components";
 
-<Render file="survey" product="waf" />
-
 <Render file="waf-intro" product="waf" />
 
 :::note[What is a Web Application Firewall?]
diff --git a/src/content/docs/waf/custom-rules/index.mdx b/src/content/docs/waf/custom-rules/index.mdx
@@ -7,8 +7,6 @@ sidebar:
 
 import { Render, FeatureTable } from "~/components";
 
-<Render file="survey" product="waf" />
-
 <Render file="custom-rules-intro" product="waf" />
 
 Custom rules are evaluated in order, and some actions like _Block_ will stop the evaluation of other rules. For more details on actions and their behavior, refer to the [actions reference](/ruleset-engine/rules-language/actions/).
diff --git a/src/content/docs/waf/detections/index.mdx b/src/content/docs/waf/detections/index.mdx
@@ -14,11 +14,8 @@ import {
 	Tabs,
 	TabItem,
 	Steps,
-	Render,
 } from "~/components";
 
-<Render file="survey" product="waf" />
-
 Traffic detections check incoming requests for malicious or potentially malicious activity. Each enabled detection provides one or more scores — available in the [Security Analytics](/waf/analytics/security-analytics/) dashboard — that you can use in rule expressions.
 
 Cloudflare currently provides the following detections for finding security threats in incoming requests:
diff --git a/src/content/docs/waf/detections/leaked-credentials/index.mdx b/src/content/docs/waf/detections/leaked-credentials/index.mdx
@@ -7,9 +7,7 @@ sidebar:
     label: Leaked credentials
 ---
 
-import { Type, Render } from "~/components";
-
-<Render file="survey" product="waf" />
+import { Type } from "~/components";
 
 The leaked credentials [traffic detection](/waf/detections/) scans incoming requests for credentials (usernames and passwords) previously leaked from [data breaches](https://www.cloudflare.com/learning/security/what-is-a-data-breach/).
 
diff --git a/src/content/docs/waf/detections/malicious-uploads/index.mdx b/src/content/docs/waf/detections/malicious-uploads/index.mdx
@@ -7,9 +7,8 @@ sidebar:
     label: Malicious uploads
 ---
 
-import { GlossaryTooltip, Type, Render } from "~/components";
+import { GlossaryTooltip, Type } from "~/components";
 
-<Render file="survey" product="waf" />
 
 The malicious uploads detection, also called uploaded content scanning, is a WAF [traffic detection](/waf/concepts/#detection-versus-mitigation) that scans content being uploaded to your application.
 
diff --git a/src/content/docs/waf/get-started.mdx b/src/content/docs/waf/get-started.mdx
@@ -5,9 +5,7 @@ sidebar:
   order: 2
 ---
 
-import { Stream, Details, GlossaryTooltip, Tabs, TabItem, Steps, Render } from "~/components";
-
-<Render file="survey" product="waf" />
+import { Stream, Details, GlossaryTooltip, Tabs, TabItem, Steps } from "~/components";
 
 The Cloudflare Web Application Firewall (Cloudflare WAF) checks incoming web and API requests and filters undesired traffic based on sets of rules called rulesets.
 
diff --git a/src/content/docs/waf/index.mdx b/src/content/docs/waf/index.mdx
@@ -19,8 +19,6 @@ import {
 	Stream,
 } from "~/components";
 
-<Render file="survey" product="waf" />
-
 <Description>
 
 Get automatic protection from vulnerabilities and the flexibility to create custom rules.
diff --git a/src/content/docs/waf/managed-rules/check-for-exposed-credentials/index.mdx b/src/content/docs/waf/managed-rules/check-for-exposed-credentials/index.mdx
@@ -7,8 +7,6 @@ sidebar:
 
 import { GlossaryTooltip, Render } from "~/components";
 
-<Render file="survey" product="waf" />
-
 Many web applications have suffered <GlossaryTooltip term="credential stuffing" link="https://www.cloudflare.com/learning/bots/what-is-credential-stuffing/">credential stuffing</GlossaryTooltip> attacks in the recent past. In these attacks there is a massive number of login attempts using username/password pairs from databases of <GlossaryTooltip term="leaked credentials">exposed credentials</GlossaryTooltip>.
 
 Cloudflare offers you automated checks for exposed credentials using Cloudflare Web Application Firewall (WAF).
diff --git a/src/content/docs/waf/managed-rules/index.mdx b/src/content/docs/waf/managed-rules/index.mdx
@@ -12,8 +12,6 @@ head:
 
 import { FeatureTable, Render, RuleID } from "~/components";
 
-<Render file="survey" product="waf" />
-
 <Render file="waf-managed-rules-intro" product="waf" />
 
 ## Available managed rulesets
diff --git a/src/content/docs/waf/managed-rules/payload-logging/index.mdx b/src/content/docs/waf/managed-rules/payload-logging/index.mdx
@@ -5,9 +5,7 @@ sidebar:
   order: 11
 ---
 
-import { GlossaryTooltip, Render } from "~/components";
-
-<Render file="survey" product="waf" />
+import { GlossaryTooltip } from "~/components";
 
 The WAF allows you to log the request information that triggered a specific rule of a managed ruleset. This information is known as the payload. Payload information includes the specific string that triggered the rule, along with the text that appears immediately before and after the match.
 
diff --git a/src/content/docs/waf/managed-rules/waf-exceptions/index.mdx b/src/content/docs/waf/managed-rules/waf-exceptions/index.mdx
@@ -8,10 +8,6 @@ head:
     content: Create WAF exceptions
 ---
 
-import { Render } from "~/components";
-
-<Render file="survey" product="waf" />
-
 Create an exception to skip the execution of WAF managed rulesets or some of their rules. The exception configuration includes an expression that defines the skip conditions, and the rules or rulesets to skip under those conditions.
 
 ## Types of exceptions
diff --git a/src/content/docs/waf/rate-limiting-rules/best-practices.mdx b/src/content/docs/waf/rate-limiting-rules/best-practices.mdx
@@ -8,8 +8,6 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="survey" product="waf" />
-
 The following sections cover typical rate limiting configurations for common use cases. You can combine the provided example rules and adjust them to your own scenario.
 
 The main use cases for rate limiting are the following:
diff --git a/src/content/docs/waf/rate-limiting-rules/index.mdx b/src/content/docs/waf/rate-limiting-rules/index.mdx
@@ -8,8 +8,6 @@ tableOfContents: false
 
 import { Render } from "~/components";
 
-<Render file="survey" product="waf" />
-
 Rate limiting rules allow you to define rate limits for requests matching an expression, and the action to perform when those rate limits are reached.
 
 In the [new security dashboard](/security/), rate limiting rules are one of the available types of [security rules](/security/rules/). Security rules perform security-related actions on incoming requests that match specified filters.
diff --git a/src/content/docs/waf/tools/index.mdx b/src/content/docs/waf/tools/index.mdx
@@ -7,9 +7,8 @@ sidebar:
     hideIndex: true
 ---
 
-import { DirectoryListing, Render } from "~/components";
+import { DirectoryListing } from "~/components";
 
-<Render file="survey" product="waf" />
 
 The Cloudflare WAF offers the following additional tools:
 
diff --git a/src/content/docs/waf/tools/ip-access-rules/index.mdx b/src/content/docs/waf/tools/ip-access-rules/index.mdx
@@ -5,9 +5,7 @@ sidebar:
   order: 2
 ---
 
-import { GlossaryTooltip, Render } from "~/components";
-
-<Render file="survey" product="waf" />
+import { GlossaryTooltip } from "~/components";
 
 Use IP Access rules to <GlossaryTooltip term="allowlist">allowlist</GlossaryTooltip>, block, and challenge traffic based on the visitor's IP address, Autonomous System Number (ASN), or country.
 
diff --git a/src/content/docs/waf/tools/lists/index.mdx b/src/content/docs/waf/tools/lists/index.mdx
diff --git a/src/content/docs/waf/tools/scrape-shield/index.mdx b/src/content/docs/waf/tools/scrape-shield/index.mdx
diff --git a/src/content/partials/waf/survey.mdx b/src/content/partials/waf/survey.mdx

Original file line number	Diff line number	Diff line change
`@@ -9,7 +9,6 @@ sidebar:`
`9`	`9`
`10`	`10`	`import { GlossaryTooltip, Render, Steps } from "~/components"`
`11`	`11`
`12`		`-<Render file="survey" product="waf" />`
`13`	`12`
`14`	`13`	`This guide will help you set up API Shield to identify and address API security best practices.`
`15`	`14`
Original file line number	Diff line number	Diff line change
`@@ -8,7 +8,6 @@ sidebar:`
`8`	`8`
`9`	`9`	`import { GlossaryTooltip, Steps, Tabs, TabItem, Render } from "~/components"`
`10`	`10`
`11`		`-<Render file="survey" product="waf" />`
`12`	`11`
`13`	`12`	`<GlossaryTooltip term="JSON web token (JWT)">JSON web tokens (JWT)</GlossaryTooltip> are often used as part of an authentication component on many web applications today. Since JWTs are crucial to identifying users and their access, ensuring the token’s integrity is important.`
`14`	`13`
Original file line number	Diff line number	Diff line change
`@@ -11,7 +11,6 @@ head:`
`11`	`11`
`12`	`12`	`import { Render, Tabs, TabItem, Steps } from "~/components"`
`13`	`13`
`14`		`-<Render file="survey" product="waf" />`
`15`	`14`
`16`	`15`	`Super Bot Fight Mode is included in your Pro, Business, or Enterprise subscription. When enabled, the product:`
`17`	`16`