Overview
The suppression system allows you to manage false positives in your AI security workflow. When RAXE detects a threat that you’ve verified as safe, you can suppress it to prevent future alerts.Suppressions should be used sparingly. Before suppressing, verify it’s a true false positive and consider if the detection rule needs updating.
Configuration
Suppressions are configured in.raxe/suppressions.yaml:
Required Fields
Optional Fields
Patterns
Patterns support wildcards with family prefixes:Valid Family Prefixes
Actions
Instead of fully suppressing a detection, you can override its action:SDK Usage
Inline Suppression
Context Manager
CLI Usage
Scan with Suppression
Manage Suppressions
Best Practices
Be Specific
Use exact rule IDs when possible. Avoid broad wildcards.
Set Expirations
Temporary suppressions should have expiration dates.
Document Reasons
Provide clear reasons for audit compliance.
Review Regularly
Schedule quarterly reviews of active suppressions.
Example: Good vs. Bad Reasons
Troubleshooting
Suppression Not Working
- Check pattern syntax:
raxe suppress list - Verify file location:
ls -la .raxe/suppressions.yaml - Check for expiration: Expired suppressions are automatically skipped
Invalid Pattern Error
Ensure patterns have valid family prefixes:Missing Reason Error
All suppressions require a reason field:What’s Next
Policies
Configure enforcement policies
Troubleshooting
Common issues and solutions
