Security

Denied by default, verified on every request.

Praxis authenticates and authorizes every request itself, accepts no data from its clients and reaches only the sources its catalog declares.

Controls

Security built into the platform, not bolted on.

  • Denied by default

    Every operation except the readiness probe requires a verified caller holding the right capability.

  • Your identity provider

    People sign in through the host application. Systems and agents present short-lived access tokens from your identity provider, verified against its published keys.

  • Least privilege

    Readers can read. Only the scheduler's service identity can ask the platform to synchronize, and a service holds exactly one capability.

  • Read-only knowledge

    No client can submit source data or change configuration. Callers save only their own watchlists and alert read state.

  • Confined egress

    Connectors reach only the exact origins the catalog declares, over HTTPS, without redirects and without credentials.

  • Browser protections

    An origin policy, protection against cross-site request forgery and credential-free cross-origin access guard every browser request.

  • Append-only audit trail

    Every data revision records its source, snapshot and the service identity that synchronized it. The revision log is never rewritten.

  • Minimal personal data

    No accounts, passwords or keys are stored. Logs never carry request bodies or credentials.

Shared responsibility

What the platform does, and what its host provides.

Hosted deployments include the host infrastructure. For a dedicated deployment, your team provides it.

  • Praxis provides

    Controls enforced on every request it serves.

    • Authentication and authorization of every request
    • Capability checks for reading and synchronizing
    • Origin, forgery and cross-origin policies
    • An egress allowlist drawn from the catalog
    • An append-only revision log
    • Connectors that hold no secrets
  • The host provides

    The infrastructure around the platform.

    • Identity: accounts, sign-in and token issuance
    • TLS termination
    • Rate limiting
    • Network controls that block private and metadata address ranges
    • Retention of access logs
    • Tenant isolation

Report a vulnerability. Report a suspected vulnerability privately through the contact page, and keep its details out of public channels until a fix is released. Contact the team

Bring your security reviewers.

Request access, or contact us for a security review of identity, egress, audit and personal data in your deployment.