PIE (Penetration Investigation Engine) checks are automated security checks that analyze traffic recorded by your HackGATE. Instead of performing active attacks, PIE checks query the traffic logs to detect whether specific attack patterns were attempted by researchers during the testing period.Documentation Index
Fetch the complete documentation index at: https://docs.hackgate.io/llms.txt
Use this file to discover all available pages before exploring further.
PIE checks are passive — they query recorded traffic logs and do not send any requests to your application.
Available PIE checks
| ID | Name | What it detects |
|---|---|---|
| PIE-0038 | Test DELETE HTTP Method | Whether DELETE requests were sent to the application. |
| PIE-0051 | Try Path traversal attack | Requests containing ../ path traversal sequences. |
| PIE-0116 | PHP Serialized Object Injection | Indicators of PHP object serialization payloads. |
| PIE-0144 | Test for /admin path | Requests targeting the /admin endpoint. |
| PIE-0172 | Test for .git file | Requests attempting to access .git directory files. |
| PIE-0197 | Test for SQL injections | SQL injection pattern indicators in recorded requests. |
| PIE-0215 | Test JWT token for null algorithm | JWT tokens with alg: none in recorded traffic. |
| PIE-0303 | Test for Log4Shell vulnerabilities | Log4Shell JNDI lookup patterns in request data. |
List all checks
Retrieve the full list of available PIE checks with descriptions:Run a check
Run a specific PIE check against your HackGATE’s recorded traffic for a given time range:"true" if the pattern was detected in traffic, "false" if not.
