Skip to main content

Now accepting design partners.

Request a demo
Request a demo

Security

Built to be inspected.

How REAEGIS handles identity, isolation, data and audit, and where it can run.

Request a demoSee how evidence is verified

REAEGIS / security model

Four layers
  1. IdentityOpenID Connect with PKCE.
    SAML 2.0. CAC and PIV.
  2. ApplicationToken check, rate limit,
    tenant isolation.
  3. DataEncrypted at rest.
    Row-level security.
  4. AuditSigned with Cosign.
    Anchored in Rekor.

Four layers,
each with a job.

Sign-in, request handling, storage and the audit record, each drawn the way it works.

Identity

LAYER 01

Sign-in runs through your identity provider.

User

CAC, PIV or SSO

signs in

Your identity provider

SAML 2.0, OIDC

token

REAEGIS

OIDC with PKCE

  • OpenID Connect with PKCE
  • SAML 2.0
  • CAC and PIV

Application

LAYER 02

The API gateway checks every request before it reaches a tenant.

Request

API gateway

  • Validates token
  • Rate-limits
  • Isolates tenant
Tenant ATenant B

lanes never cross

  • Token validation
  • Rate limiting
  • Tenant isolation
  • Dedicated tenants available

Data

LAYER 03

Each row belongs to one tenant, and the database enforces it.

Rows by tenant, as tenant A reads them
tenant_idrecordtenant A reads
tenant-aFinding 0482visible
tenant-bRedactedblocked
tenant-aPOA&M item 0117visible
tenant-bRedactedblocked
  • Encrypted at rest
  • Evidence in object storage
  • Retention you set
  • PostgreSQL
  • Encryption at rest
  • Row-level security
  • Configurable retention

Audit

LAYER 04

Every event is signed, then anchored where it can be checked.

Event

any action

signed

Cosign signature

CHRONICLE

anchored

Rekor log

index 142907113

sha256:9f2c41d07be3…a41e

Verified

Inside an air gap, the log is internal.

  • Cosign
  • Sigstore Rekor
  • CHRONICLE

The approver is never
the initiator.

Enforced in the data layer, not only in policy.

INITIATOR

ISSO

Starts the remediation for a finding.

request

PREPARES

REAEGIS

Builds the change on an isolated branch.

for approval

APPROVER

Maya Reyes

A different person approves the change.

Initiator tries to approveRejected

Both actions recorded

CHRONICLE

  • 14:05:12ZSignedRemediation startedISSO
  • 14:19:05ZSignedChange approvedMaya Reyes
  • AC-5 Approver is not the initiator
  • CM-3 Change recorded

REAEGIS never holds
your eMASS key.

The sync runs from an agent inside your boundary, with a PKI credential you own.

outside

REAEGISholds no key
POA&M status and results

authorization boundary

In-boundary agent

runs in your environment

Your PKI credential

customer-owned

The key never leaves the boundary.

syncs
eMASSDoD system of record
Crosses the boundary
POA&M status and results
Stays inside
Your PKI credential and its key
REAEGIS holds
No eMASS credential

Other ways to reach eMASS

  • Export files for manual upload
  • Direct API where network policy allows

Three boundaries.
You choose where
REAEGIS runs.

Compare the three models

REAEGIS cloud

REAEGIS runs outside and connects to your pipeline.

Runs in
REAEGIS cloud
Crosses the boundary
Findings and pull requests
Sign-in
SAML 2.0, OpenID Connect

In your boundary

REAEGIS runs inside, next to your pipeline.

Runs in
Your IL4 or IL5 environment
Crosses the boundary
Nothing
Sign-in
CAC and PIV

Air-gapped

REAEGIS runs inside. The network link is cut.

Runs in
Your enclave
Crosses the boundary
A signed update kit, inbound only
Sign-in
CAC and PIV

Security statement.

How we handle data, how it is protected, where REAEGIS stands on FedRAMP, and how to report a problem.

Data handling

Each customer’s findings, evidence and records belong to that customer. Every row in the database carries its tenant, and the database enforces that one tenant can never read another’s data.

Access inside REAEGIS is role based and least privilege, and every sign-in, approval and change is written to a signed audit record. In an in-boundary or air-gapped deployment, the platform and its data stay inside your boundary. Retention and deletion follow your organization’s agreement.

Data in the hosted service is stored in data centers in the United States.

Encryption in transit and at rest

In transit: every connection to REAEGIS and to this site uses TLS. Plain HTTP is redirected to HTTPS, and sign-in uses OpenID Connect with PKCE, SAML 2.0 or CAC and PIV through your identity provider.

At rest: the database, object storage, backups and cluster volumes are encrypted with managed encryption keys, and credentials and keys are held in a managed secrets store, never in code or configuration files. Evidence records are also signed with Cosign, so any change to them is detectable.

FedRAMP alignment

REAEGIS is built against the NIST SP 800-53 Rev 5 controls that FedRAMP baselines draw on: identity and access, audit and accountability, configuration management, and system and communications protection are designed in, not added later. It can run inside your own authorization boundary, so it inherits the controls you already operate.

Alignment is not authorization. This statement does not claim a FedRAMP authorization for REAEGIS, and your Authorizing Official makes every authorization decision for your system.

Responsible disclosure

If you believe you have found a vulnerability in REAEGIS or this site, report it to security@reaegis.com. Include what you found, where, and the steps to reproduce it. We acknowledge reports within three business days and keep you informed until the issue is resolved.

Test only against your own account, do not access or change other people’s data, and do not run denial of service, social engineering or physical tests. Give us reasonable time to fix an issue before disclosing it. We will not pursue action against research done in good faith within these rules.

Open about status.

Where to check on the service, what is committed, and where to report a problem.

Uptime commitment

Professional
99.9%
Enterprise
99.99%

Committed uptime, by plan.

Authorization status of REAEGIS

Aligned to NIST SP 800-53 Rev 5

Built against the controls FedRAMP draws on. No FedRAMP authorization is claimed; see FedRAMP alignment.

Authorization is not a destination. It is a system property.

Request a demo and we will walk one finding from detection to signed evidence.

Request a demoSee the platform

  • Federal programs

    Invitation only, with CAC and PIV.

    Request access

  • Commercial teams

    Self-register with single sign-on.

    Create a workspace

  • Pricing

    Plans start at $2,500 per month. In-boundary and air-gapped deployments are scoped per program.

    See pricing