[WIP-NOT-READY]Feat/crs ruleset

[gauravakto]

TL;DR: OWASP CRS Ruleset is too slow for our needs, making it infeasible.

Problem: Build robust policy filters. Attempted Solution: Use OWASP CRS Regexes as-is. Details: Regex Rule Tested: RuleId 932330 (RCE-Regexes) Iterations: 1,000 Test Results: Small Payload: "curl -X POST http://example.com/ -d 'id=1; ;"env | grep u"'" Speed: ~76k ops/sec Large Payload: Insperity sample request Speed: ~80 ops/sec Time: 12 sec for 1,000 iterations Note: Hangs at 10,000 requests Libraries Used: java.util.regex Google RE2 – expected to be faster, but 2-3x slower.

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
18819192	Triggered	Generic High Entropy Secret	0d9ef06ca15276768aefa6604a00112d701bdaef	apps/threat-detection/src/main/java/com/akto/threat/detection/utils/CRSEvaluator.java	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}