Security controls
Each control below is one we run today. “Last verified” is the date we last confirmed it still works as described.
| Category | Control | Status | Last verified |
|---|---|---|---|
| Data protection | Connector credentials and other stored secrets are encrypted before they are stored. | Implemented | 2026-11-18 |
| Application | Passwords are never stored in readable form; only salted one-way hashes are kept. | Implemented | 2026-11-18 |
| Application | Sign-in sessions use protected cookies and expire automatically. | Implemented | 2026-11-18 |
| Application | Access inside a workspace is role-based, and workspace data is scoped to the signed-in member's organisation. | Implemented | 2026-11-18 |
| Application | API tokens are stored as hashes; the full token is shown once at creation. | Implemented | 2026-11-18 |
| Customer-facing | Outbound webhooks are signed so receivers can verify them. | Implemented | 2026-11-18 |
| Application | Outbound requests made on behalf of users are restricted from reaching internal addresses. | Implemented | 2026-11-18 |
| Customer-facing | Sensitive actions are written to a per-workspace audit log that workspace admins can read. | Implemented | 2026-11-18 |
| Process | Active scanning (port and vulnerability checks) only runs against domains whose control was proved with a DNS record. | Implemented | 2026-11-18 |
| Process | Domain owners can ask us to stop scanning; blocked, unverified domains are refused for free and prospect scans. | Implemented | 2026-11-18 |
| Data protection | Workspace admins can schedule deletion; after a grace period the workspace's data and stored scan evidence are purged. | Implemented | 2026-11-18 |
| Customer-facing | Account data export and account erasure are available in the product; privacy requests are logged against a 30-day response target. | Implemented | 2026-11-18 |
| Data protection | Free-scan results that are not converted into an account are deleted after 30 days by default. | Implemented | 2026-11-18 |
| Infrastructure | The service sits behind web application protections. | Implemented | 2026-11-18 |
| Infrastructure | All traffic to the application is encrypted in transit. | Implemented | 2026-11-18 |
| Infrastructure | Stored data is encrypted at rest, kept on restricted networks, and backed up automatically. | Implemented | 2026-11-18 |
| Infrastructure | Software images are scanned for known vulnerabilities before release. | Implemented | 2026-11-18 |
| Infrastructure | The web app is served with browser security protections enabled. | Implemented | 2026-11-18 |
| Process | Dependencies are audited for known vulnerabilities on every change, and update pull requests are raised automatically. | Implemented | 2026-11-18 |
| Process | We publish a vulnerability disclosure policy and a security.txt file. | Implemented | 2026-11-18 |