Exploit2Impact

Security

Designed assuming exposure to the Internet.

Exploit2Impact is designed to run behind a trusted reverse proxy and TLS. The threat model considers credential attacks, tenant escape, injection, SSRF, secret disclosure, audit tampering, queue abuse and supply chain compromise.

Identity and access control

  • Password login (bcrypt), TOTP 2FA and revocable sessions
  • OIDC/SSO with state, nonce and PKCE; optional OAuth2 token introspection
  • API keys with scope, expiry, rotation and deletion
  • SCIM 2.0 that cannot assign the admin role
  • Admin, Auditor and User roles with granular permissions

Tenant isolation

  • Membership and privileges verified before accessing simulations, reports, audit, jobs and artifacts
  • Global administrators explicitly configured and kept to a minimum
  • Tenant-bound confirmation for destructive operations, against cross-tenant deletion

Data and secrets protection

  • Secrets and signing keys from the environment or a secret manager, never from repository files
  • Encryption of sensitive fields and redaction of secrets in logs and configuration
  • Encrypted backups; artifacts with restrictive permissions or S3/KMS encryption
  • Fail-closed behaviour in production if critical services are not operational

Audit and integrity

  • Structured events in an append-only hash chain, with serialized append per tenant
  • Integrity verification and audit bundle export with optional signature
  • Signed checkpoints kept in write-once mode (local or S3 Object Lock)
  • Tracking of logins, simulations, administration and API key usage

Outbound integration security

  • SSRF protection for outbound calls and webhooks
  • HTTPS destinations with configurable allowlist and redirects disabled
  • Webhooks with HMAC-signed payload, 256 KiB limit and secret encrypted at rest
  • Timeouts, circuit breakers and limits on threat intelligence sources

Deployment and readiness

  • Container-ready with PostgreSQL, Redis, workers and a dedicated scheduler
  • Liveness and readiness endpoints that do not expose secrets
  • Optional Prometheus metrics and OpenTelemetry tracing
  • Global, per-IP and per-user rate limiting; CORS with explicit origins

Supply-chain security

  • Dependency audit, CycloneDX SBOM and image scanning
  • Verifiable release manifest
  • Release blocked if the Git working tree is not clean
  • Backup and restore verified in CI on ephemeral services

Verified quality

  • 233 automated tests in the latest quality gate
  • 92% coverage of security-critical modules
  • Ruff and Pyright with no errors; dependency scan with no known vulnerabilities at the time of the check

Responsible disclosure

Found a vulnerability?

If you believe you have found a security issue, write to us with the minimum details needed to reproduce it. Please do not include personal data or credentials.

Security reports

Send a message to exploit2impactcareers@gmail.com with the subject "Security report". To protect the data of a real environment, we do not publish configuration values, hosts or keys on this site.

Do you have specific security requirements?

Let's talk: we will outline the deployment topology and the controls available.

Contact us