From d381280297c52e8ec205f44c6a7cefc8e0222ced Mon Sep 17 00:00:00 2001 From: Dave Jong Date: Fri, 2 Oct 2026 11:17:12 +0200 Subject: [PATCH 1/2] Document site protection logs for JavaScript apps --- .../Protection/app-protection-overview.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/src/content/docs/Patchstack App/Site Dashboard/Protection/app-protection-overview.md b/src/content/docs/Patchstack App/Site Dashboard/Protection/app-protection-overview.md index 3ec0cfd5..7dff6648 100644 --- a/src/content/docs/Patchstack App/Site Dashboard/Protection/app-protection-overview.md +++ b/src/content/docs/Patchstack App/Site Dashboard/Protection/app-protection-overview.md @@ -10,7 +10,7 @@ sidebar: --- _Site protection overview and security solutions are available for all Patchstack paid plan users._ -**_Protection settings and modules are available for WordPress sites only._** +Protection is also available in the site view for JavaScript / Node.js apps connected with `@patchstack/connect`. Available modules and controls depend on the site's platform, plan, and your permissions. The **Protection overview** subpage is found at **Sites** > **yoursite.com** > **Protection** in Patchstack App. @@ -19,8 +19,22 @@ On the **Protection overview** subpage you can: * See where your site got attacks from * See how have the hackers tried to attack your site +The screenshot below shows the WordPress view; JavaScript / Node.js apps have different module and log filters. + ![](@images/patchstack-site-protection-overview.png) +## JavaScript / Node.js apps + +Open **Sites → your app → Protection** in the full Patchstack dashboard. The **Firewall logs** section shows blocked requests reported by your runtime guard. Use the date range and URL search to narrow the results, then click a row for request details. + +The log filters are **All rules**, **NPM vulnerability rules**, and **Custom rules**. Use **All rules** to include logs from runtime hardening rules as well. WordPress hardening and Community IP blocklist filters are not shown for these apps. + +Module membership does not prove that a running app has fetched or enforced its rules. An empty log table only means that no matching block logs were received for the selected filters; it does not prove that the app is safe or reporting successfully. A failed log request is shown separately, with a retry option. + +For monitoring-only matches and per-rule activity, follow **rule detections** to **Attack surface**. Detection counts and firewall logs measure different things and need not match. The embedded view remains a simplified summary; use the full dashboard for the log table. + +The remaining module descriptions and screenshots below describe the WordPress view. + ## Protection modules Patchstack firewall consists of three types of protection modules, which can be toggled on and off for any protected site. These protection modules also show the number of your sites are attached to each module. From 33c8cb6c1724fbadc17cae50184c41235cfd77cc Mon Sep 17 00:00:00 2001 From: Dave Jong Date: Fri, 2 Oct 2026 12:31:04 +0200 Subject: [PATCH 2/2] Clarify firewall origins when client IP is unavailable --- .../Site Dashboard/Protection/app-protection-overview.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/content/docs/Patchstack App/Site Dashboard/Protection/app-protection-overview.md b/src/content/docs/Patchstack App/Site Dashboard/Protection/app-protection-overview.md index 7dff6648..236226f3 100644 --- a/src/content/docs/Patchstack App/Site Dashboard/Protection/app-protection-overview.md +++ b/src/content/docs/Patchstack App/Site Dashboard/Protection/app-protection-overview.md @@ -29,6 +29,8 @@ Open **Sites → your app → Protection** in the full Patchstack dashboard. The The log filters are **All rules**, **NPM vulnerability rules**, and **Custom rules**. Use **All rules** to include logs from runtime hardening rules as well. WordPress hardening and Community IP blocklist filters are not shown for these apps. +If the runtime cannot provide a client IP, the origin reads **IP unavailable** without a country flag. A flag is shown only when both an IP and country information are available. + Module membership does not prove that a running app has fetched or enforced its rules. An empty log table only means that no matching block logs were received for the selected filters; it does not prove that the app is safe or reporting successfully. A failed log request is shown separately, with a retry option. For monitoring-only matches and per-rule activity, follow **rule detections** to **Attack surface**. Detection counts and firewall logs measure different things and need not match. The embedded view remains a simplified summary; use the full dashboard for the log table.