Skip to content

Commit 7768199

Browse files
sylwangmjang
andcommitted
Update content/nginx-one/nap-integration/add-signature-sets.md
Co-authored-by: Mike Jang <[email protected]>
1 parent 09f53a2 commit 7768199

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

content/nginx-one/nap-integration/add-signature-sets.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,8 @@ A **signature set** is a collection of attack signatures with a specific name an
1818

1919
For example, you might have sets for SQL Injection Signatures, Cross-Site Scripting Signatures, or Buffer Overflow Signatures.
2020

21-
### Signature Exception
21+
### Signature exception
22+
2223
A **signature exception** allows you to explicitly enable or disable individual attack signatures within a set. This gives you granular control over your policy. For example:
2324
- If a signature in a set causes false positives (blocking legitimate traffic), you can create an exception to disable just that signature while keeping the rest of the set active.
2425
- If you want to enable blocking for one specific attack signature rather than an entire set, you can create an exception to enable just that signature.

0 commit comments

Comments
 (0)