Skip to main content

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 (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.
PIE checks are passive — they query recorded traffic logs and do not send any requests to your application.

Available PIE checks

IDNameWhat it detects
PIE-0038Test DELETE HTTP MethodWhether DELETE requests were sent to the application.
PIE-0051Try Path traversal attackRequests containing ../ path traversal sequences.
PIE-0116PHP Serialized Object InjectionIndicators of PHP object serialization payloads.
PIE-0144Test for /admin pathRequests targeting the /admin endpoint.
PIE-0172Test for .git fileRequests attempting to access .git directory files.
PIE-0197Test for SQL injectionsSQL injection pattern indicators in recorded requests.
PIE-0215Test JWT token for null algorithmJWT tokens with alg: none in recorded traffic.
PIE-0303Test for Log4Shell vulnerabilitiesLog4Shell JNDI lookup patterns in request data.

List all checks

Retrieve the full list of available PIE checks with descriptions:
curl https://admin.hackgate.io/api/pie/getChecks \
  -H "Authorization: Bearer <your-token>"
Response:
[
  {
    "id": "PIE-0038",
    "name": "Test DELETE HTTP Method",
    "description": "The DELETE HTTP method is used to remove resources from a server..."
  }
]

Run a check

Run a specific PIE check against your HackGATE’s recorded traffic for a given time range:
curl -X POST https://admin.hackgate.io/api/pie/runCheck \
  -H "Authorization: Bearer <your-token>" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "PIE-0172",
    "url": "example-yourorg.hackgate.net",
    "gte": "2024-01-01T00:00:00Z",
    "lte": "2024-01-31T23:59:59Z"
  }'
Response: "true" if the pattern was detected in traffic, "false" if not.
Run PIE checks at the end of a testing engagement to verify that researchers covered common vulnerability classes.
Last modified on May 9, 2026