Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Add example Injection Protection plugin log #8286

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

cloudjumpercat
Copy link
Contributor

Description

Added an example Injection Protection plugin log.

Testing instructions

Preview link:

Checklist

Signed-off-by: Diana <[email protected]>
@cloudjumpercat cloudjumpercat added the review:general Review for general accuracy and presentation. Does the doc work? Does it output correctly? label Dec 17, 2024
@cloudjumpercat cloudjumpercat requested a review from a team as a code owner December 17, 2024 16:21
Copy link

netlify bot commented Dec 17, 2024

Deploy Preview for kongdocs ready!

Name Link
🔨 Latest commit 3c9b4f9
🔍 Latest deploy log https://app.netlify.com/sites/kongdocs/deploys/6761a4f01cfe4e00092d2688
😎 Deploy Preview https://deploy-preview-8286--kongdocs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
9 paths audited
Performance: 93 (🟢 up 4 from production)
Accessibility: 92 (no change from production)
Best Practices: 98 (🟢 up 8 from production)
SEO: 99 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify site configuration.

@@ -81,6 +81,12 @@ Logs are automatically collected when you enable the Injection Protection plugin
* [UDP Log](/hub/kong-inc/udp-log/)
* [{{site.konnect_short_name}} Advanced Analytics](/konnect/analytics/) <!--though i'm not sure if they will do anything with them yet-->

The following is an example of the information that is logged by the Injection Protection plugin:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The following is an example of the information that is logged by the Injection Protection plugin:
Here's a sample log entry created by the Injection Protection plugin.

Slight rephrase to make it sound less formal + shorten the sentence.

```
threat detected: 'sql', action taken: log_only, found in path_and_query, query param value: foo: insert into test
```

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Where:
* The plugin detected a SQL injection threat
* It created a log entry but took no other actions
* The threat was found in the request path or query
* The inserted snippet is `foo: insert into test`

I'd add something like this to give the log message a tiny bit of context. Not sure if I got it all correct, so please double-check.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
review:general Review for general accuracy and presentation. Does the doc work? Does it output correctly?
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants