Built so a leaked key is not a disaster
A vulnerability service should be careful with its own access. Here is how API access is protected.
Keys are stored as hashes
Only a SHA-256 hash of each key is stored. The key is shown once, when it is created, and cannot be recovered afterwards, only replaced.
Every key is locked to IP addresses
A key works only from the addresses or ranges you list. Requests from anywhere else are refused, even with a valid key. Open-to-everyone ranges are rejected.
Encrypted in transit
All traffic uses HTTPS with TLS 1.2 or newer, and the site sends HSTS so browsers keep using it.
Everything is logged
Requests, refusals, key changes and settings changes are recorded per API user, which makes misuse easy to spot and investigate.
More controls
- Rate limits apply per API user, with a separate flood limit per IP at the edge. Over the limit you get
429and aRetry-Afterheader. - Read-only API. Only
GETrequests are accepted; the public API cannot change any data. - Instant revocation. Keys, or a whole API user, can be switched off or deleted at any time and the change takes effect immediately.
- Closed administration. The management area is not public: it requires a secret entry link and a password, uses signed, HttpOnly session cookies and stores passwords with scrypt.
- No secrets in logs. Keys, passwords and entry tokens are never written to our logs.
Reporting a vulnerability
If you find a security problem in Patchgrid, please tell us through the contact form (choose “Other”) and describe what you found. Please give us a reasonable time to fix it before sharing details publicly.