Skip to content

Security Practices

The practices below are what we operate today.

Each customer’s data is scoped to that customer in the application’s data-access code, not just hidden in the interface. Regression tests check that a request from one customer’s account cannot read another customer’s records. See Data Isolation for the limits.

  • Every API request requires a bearer token.
  • Accounts carry roles (company administrator, team member) that limit what each user can do.
  • Platform administration surfaces are restricted to GovConHouse staff (super_admin).
  • Transport encryption everywhere: HTTPS for the web surfaces and TLS for data connections.
  • Per-endpoint rate limiting with backoff signaling to absorb abusive traffic.
  • An audit trail records sensitive actions.
  • Application errors and exceptions are monitored with alerting.
  • The platform’s health endpoints report degraded state rather than failing silently.

If you believe you have found a security issue, see Vulnerability disclosure.