From 114fd52aecacf7f9cb27414d16eabc11fc44226b Mon Sep 17 00:00:00 2001 From: Sam Rose Date: Thu, 2 Oct 2025 13:21:12 +0100 Subject: [PATCH 1/3] Make the wording of the OWASP action documentation more approachable. --- traffic-policy/actions/owasp-crs-request.mdx | 32 ++++++++----------- traffic-policy/actions/owasp-crs-response.mdx | 31 ++++++++---------- 2 files changed, 27 insertions(+), 36 deletions(-) diff --git a/traffic-policy/actions/owasp-crs-request.mdx b/traffic-policy/actions/owasp-crs-request.mdx index d84ef140c0..f5c4eda3c5 100644 --- a/traffic-policy/actions/owasp-crs-request.mdx +++ b/traffic-policy/actions/owasp-crs-request.mdx @@ -1,35 +1,31 @@ --- title: OWASP CRS Request Action sidebarTitle: OWASP CRS Request -description: The OWASP CRS Request Traffic Policy action enables OWASP CRS for use with ModSecurity or compatible web application firewalls. +description: Block common web attacks with the `owasp-crs-request` action in Traffic Policy --- import ActionExamples from "/snippets/traffic-policy/actions/owasp-crs-request/examples/index.mdx"; import ActionVariablesDescription from "/snippets/traffic-policy/common/action-variables-description.mdx"; -import { YouTubeEmbed } from "/snippets/YouTubeEmbed.jsx"; +import { YouTubeEmbed } from "/snippets/TrafficPolicy.jsx"; import { ConfigField } from "/snippets/ConfigTable.jsx"; import { ConfigChildren } from "/snippets/ConfigChildren.jsx"; -The **OWASP CRS Request** Traffic Policy action enables OWASP (Open Worldwide Application -Security Project) CRS (previously Core Rule Set), a set of generic attack detection -rules for use with ModSecurity or compatible web application firewalls. It aims to protect -web applications from a wide range of attacks, including the -[OWASP Top Ten](https://owasp.org/www-project-top-ten/), with a minimum of false alerts. -CRS provides protection against many common attack categories, including SQL Injection, -Cross Site Scripting, Local File Inclusion, etc. - -The `owasp-crs-request` action only enables rule processing on _incoming_ HTTP requests to your -endpoint. In addition to this action, we also recommend you enable the [OWASP CRS Response -action](/traffic-policy/actions/owasp-crs-response/) to analyze _outgoing_ HTTP responses from your endpoint. - - -## Video walkthrough - -The following video walks you through ngrok's OWASP CRS request and response actions in Traffic Policy, which let you add web application firewall protection directly to your ngrok endpoints without changing your existing infrastructure. +[OWASP](https://owasp.org/) stands for the Open Web Application Security +Project, an online community that, among other things, maintains annual lists of +the most critical web application security risks. The [OWASP Core Rule +Set](https://owasp.org/www-project-modsecurity-core-rule-set/) (CRS) is a set of +attack detection rules that we expose for you to use in your Traffic Policies. +It includes protections against attacks like SQL Injection, Cross Site +Scripting, Local File Inclusion, and many others. +The `owasp-crs-request` action enables rule processing on incoming HTTP +requests to your endpoint. We recommend you also enable the [OWASP CRS Response +action](/traffic-policy/actions/owasp-crs-response/) to block attacks where +it's the response that is malicious. + ### Configuration Reference This is the [Traffic Policy](/traffic-policy/) configuration diff --git a/traffic-policy/actions/owasp-crs-response.mdx b/traffic-policy/actions/owasp-crs-response.mdx index 90165b08df..7d22f3615f 100644 --- a/traffic-policy/actions/owasp-crs-response.mdx +++ b/traffic-policy/actions/owasp-crs-response.mdx @@ -1,7 +1,7 @@ --- title: OWASP CRS Response Action sidebarTitle: OWASP CRS Response -description: The OWASP CRS Response action enables OWASP Core Rule Set (CRS) to analyze outgoing HTTP responses from your endpoint and protect against common web attacks. +description: Block common web attacks with the `owasp-crs-response` action in Traffic Policy --- import ActionVariablesDescription from "/snippets/traffic-policy/common/action-variables-description.mdx"; @@ -10,25 +10,20 @@ import { YouTubeEmbed } from "/snippets/YouTubeEmbed.jsx"; import { ConfigField } from "/snippets/ConfigTable.jsx"; import { ConfigChildren } from "/snippets/ConfigChildren.jsx"; -The **OWASP CRS Response** Traffic Policy action enables OWASP (Open Worldwide Application -Security Project) CRS (previously Core Rule Set), a set of generic attack detection -rules for use with ModSecurity or compatible web application firewalls. It aims to protect -web applications from a wide range of attacks, including the -[OWASP Top Ten](https://owasp.org/www-project-top-ten/), with a minimum of false alerts. -CRS provides protection against many common attack categories, including SQL Injection, -Cross Site Scripting, Local File Inclusion, etc. +[OWASP](https://owasp.org/) stands for the Open Web Application Security +Project, an online community that, among other things, maintains annual lists of +the most critical web application security risks. The [OWASP Core Rule +Set](https://owasp.org/www-project-modsecurity-core-rule-set/) (CRS) is a set of +attack detection rules that we expose for you to use in your Traffic Policies. +It includes protections against attacks like SQL Injection, Cross Site +Scripting, Local File Inclusion, and many others. -The `owasp-crs-response` action only enables rule processing on _outgoing_ HTTP responses from your -endpoint. In addition to this action, we also recommend you enable the [OWASP CRS Request -action](/traffic-policy/actions/owasp-crs-request/) to analyze _incoming_ HTTP requests to your endpoint. + -## Video walkthrough - -The video below walks you through ngrok's OWASP CRS request and response actions in Traffic Policy, which let you add web application firewall protection directly to your ngrok endpoints without changing your existing infrastructure. - - - - +The `owasp-crs-response` action enables rule processing on incoming HTTP +requests to your endpoint. We recommend you also enable the [OWASP CRS Request +action](/traffic-policy/actions/owasp-crs-request/) to block attacks where +it's the response that is malicious. ### Configuration Reference From 2a14efc127045a3b0598538db11d0b342617fe06 Mon Sep 17 00:00:00 2001 From: Sam Rose Date: Thu, 2 Oct 2025 13:23:05 +0100 Subject: [PATCH 2/3] Fix small copy-paste error. --- traffic-policy/actions/owasp-crs-response.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/traffic-policy/actions/owasp-crs-response.mdx b/traffic-policy/actions/owasp-crs-response.mdx index 7d22f3615f..c2330f5953 100644 --- a/traffic-policy/actions/owasp-crs-response.mdx +++ b/traffic-policy/actions/owasp-crs-response.mdx @@ -23,7 +23,7 @@ Scripting, Local File Inclusion, and many others. The `owasp-crs-response` action enables rule processing on incoming HTTP requests to your endpoint. We recommend you also enable the [OWASP CRS Request action](/traffic-policy/actions/owasp-crs-request/) to block attacks where -it's the response that is malicious. +it's the request that is malicious. ### Configuration Reference From 305a26995630169e5a57b3581cf50d419730ef44 Mon Sep 17 00:00:00 2001 From: Shaquil Hansford Date: Thu, 2 Oct 2025 13:30:26 -0400 Subject: [PATCH 3/3] Update traffic-policy/actions/owasp-crs-request.mdx Co-authored-by: SG <212444234+sg-writer@users.noreply.github.com> --- traffic-policy/actions/owasp-crs-request.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/traffic-policy/actions/owasp-crs-request.mdx b/traffic-policy/actions/owasp-crs-request.mdx index f5c4eda3c5..8118d56b7b 100644 --- a/traffic-policy/actions/owasp-crs-request.mdx +++ b/traffic-policy/actions/owasp-crs-request.mdx @@ -1,7 +1,7 @@ --- title: OWASP CRS Request Action sidebarTitle: OWASP CRS Request -description: Block common web attacks with the `owasp-crs-request` action in Traffic Policy +description: Block common web attacks with the `owasp-crs-request` action in Traffic Policy. --- import ActionExamples from "/snippets/traffic-policy/actions/owasp-crs-request/examples/index.mdx";