KeyHasp

Security

Built to be trusted with access.

KeyHasp holds the keys that remove people from your tools, so it is narrow by design: the smallest credentials, every company isolated, and a record of everything it does.

Credentials

Scoped keys, never root.

Each connector gets one credential, limited to user management.

  • Only what user management needs

    For GitHub, KeyHasp is a GitHub App with only the Members permission. It has no Administration permission and no access to your code.

  • Short-lived tokens

    The GitHub App signs a token valid for 9 minutes and exchanges it for an installation token valid for one hour. No long-lived personal token is involved.

  • Kept in Secrets Manager

    Tool credentials live in AWS Secrets Manager, encrypted per company. They are never stored in KeyHasp's database and never appear in logs, responses or audit events.

Tenant isolation

Every company, walled off.

KeyHasp runs as a cloud service on AWS. Each company is its own tenant, isolated in the database itself, not only in the application.

  • Isolated in the database

    Every row belongs to one company, and the database enforces it with row-level security. A request can only ever see its own company's data.

  • Encrypted per company

    Each company's tool credentials are encrypted with keys bound to that company, so one company's credentials can never be read in another's context.

  • Private infrastructure

    The functions run in private subnets. The PostgreSQL database on RDS is private and requires TLS with full verification.

  • 1tenant per company
  • 0credentials shared between companies
  • 0KeyHasp passwords

Sign-in

No passwords. Sessions that end.

  • Your identity provider

    People sign in with their company account through your identity provider, using the authorization-code flow with PKCE. Only verified emails on your domain are accepted.

  • Matched by id, not email

    A sign-in is matched to a person by their stable directory id, never by email address, and the person must be active.

  • Short, revocable sessions

    Sessions live on the server, last at most 8 hours or 2 idle hours, and use an HttpOnly, Secure cookie. Every request checks the person is still active, so leaving the directory ends the session.

  • No open admin endpoint

    The first administrator cannot be created through a public endpoint.

Mass-termination guard

A bad sync can't offboard everyone.

A directory sync that would offboard more than three people or 20% of the company, whichever is larger, or that returns an empty listing while people are active, is aborted without changes and recorded.

Audit

A record nobody can rewrite.

  • Append-only

    Audit events and offboarding reports can only be added to: the database blocks updates and deletes.

  • Every write to a tool

    Each change records the tool, the operation, the target, the outcome, who did it and a correlation id. Credentials never appear in the record.

  • Reports that stay as issued

    An offboarding report is immutable once issued. When an open task is resolved later, the resolution is appended, not edited in.

Compliance

SOC 2, in progress.

SOC 2Audit in progress

KeyHasp is going through its SOC 2 audit. The report has not been issued yet; until it is, this page describes the controls in place today.

Offboarding you can trust, without the SSO tax.