ourfault

Security

What protects the telemetry you send, what does not exist yet, and how to reach us about a vulnerability.

Report a vulnerability

Write to security@ourfault.dev. Describe what you found and how to reproduce it, and leave customer data out. security.txt lists the same contact.

If we become aware of a breach of security affecting your data, we tell your workspace owners without undue delay, and no later than 72 hours after we become aware of it. That is the commitment in the data retention policy, and this page adds nothing to it.

What protects your data

  • Tokens are hashed

    An ingest token is hashed with SHA-256 and looked up by the hash.

  • Payloads stay out of logs

    A log line holds identifiers, counts and codes. Bodies, messages, stack traces and attribute values never reach one.

  • No passwords

    People sign in with GitHub. There is no password store and no password endpoint.

  • Encrypted in transit

    The ingest endpoint accepts HTTPS only. The ingest and portal distributions require TLS 1.2 or newer.

  • A firewall at the edge

    In production, ingest sits behind a web ACL with per-address and per-origin rate limits and AWS's common and known-bad-input rule sets.

  • Browser keys are origin-bound

    A browser key is meant to be public. It names the origins that may use it, and a request from any other origin is refused.

Data is held in eu-north-1 on AWS. The diagnosis model runs in eu-central-1 on Bedrock. Triage and some judgements go to TypeSafe, which hosts in the United States, as the data retention policy sets out.

What is not there

  • No certification

    ourfault holds no SOC 2 or ISO 27001 certification.

  • No third-party test

    No outside penetration test has been run yet.

  • One operator

    One person builds and runs ourfault.

Each control and where it lives

Show the list
  • Token hashing: docs/INGEST.md, step Authenticate.
  • Point-in-time recovery on the ingest data, identity and auth tables: IngestStack.cs, IdentityTable.cs, AuthStack.cs. Tables use DynamoDB's default encryption at rest.
  • Portal and landing buckets block public access, use S3-managed encryption and refuse non-TLS requests: PortalStack.cs.
  • HTTPS-only viewers and a TLS 1.2 minimum: IngestEdge.cs, PortalStack.cs.
  • Web ACL rules: EdgeStack.cs. Dev has none.
  • Regions and the Bedrock region: Deployment.cs, Pipeline.cs.
  • Log allowlist: AuthLogTests.cs, docs/INGEST.md.
  • Secrets live in AWS Secrets Manager and are created without a value: SecretsStack.cs, pinned by SecretsStackTests.cs.
  • Deploys request a GitHub OIDC token and assume an AWS role: .github/workflows/deploy.yml.
  • GitHub sign-in, no local logins: docs/AUTH.md.
  • Browser key origins: docs/INGEST.md, Browsers.