Skip to main content

Now accepting design partners.

Request a demo

Request a demo

See one finding go from detection to signed evidence.

Tell us about your authorization path. We reply within one business day.

Request a demo

Required
Required
Required
Compliance targetRequired, choose one
EnvironmentRequired, choose one
TimelineRequired, choose one

Prefer email?team@reaegis.com

ORION-1 / FINDING 0482

SI-2
  1. 14:02Finding detected in api-gatewayADVERSARIUS
  2. 14:21Pull request #482 approved and mergedARE
  3. 14:31Fix verified, gate passesRAMPART
  4. 15:04Evidence signed and anchoredCHRONICLE

What the demo covers.

Three parts, in this order.

  1. Part 1: A walkthrough of the loop

    One finding, from scan to signed evidence.

    ORION-1 / finding 0482

    Stage 6 of 8

    Vulnerability in container base image

    api-gatewaySI-2RA-5
    1. Find
    2. Fix
    3. Build
    4. Push
    1. Verify
    2. Deploy
    3. Confirm
    4. ATO
  2. Part 2: Your frameworks, your boundary

    Mapped to your authorization path and deployment model.

    AUTHORIZATION PATH

    • NIST SP 800-53 Rev 5
    • FedRAMP Rev 5 and 20x
    • CMMC Levels 1 to 3
    • NIST SP 800-171 Rev 2 and Rev 3
    • DoD RMF
    • IL2 to IL5

    DEPLOYMENT MODEL

    • REAEGIS cloud
    • In your boundary
    • Air-gapped
  3. Part 3: An honest scoping conversation

    What REAEGIS does not do.

    • Does not replace eMASSeMASS stays the system of record
    • Does not replace penetration testingTest findings are tracked, not produced
    • Personnel, physical and training controlsRemain human work

Bring the people who own the decision.

  • ISSO or ISSM

    Owns the POA&M and the evidence

    Sees a POA&M item close with its evidence chain attached.

    0117POA&M item 0117Evidence chain attachedClosed
  • Authorizing Official or delegate

    Owns the risk decision

    Sees the readiness score and the signed package behind a decision.

    82Readiness 82 of 100Signed evidence packageSigned
  • Engineering lead

    Owns the pipeline and the fix

    Sees the pull request, the approval gate and the checks on each push.

    Pull request #482Reviewer is not the authorApproved

After the demo.

Now accepting design partners for federal and commercial programs.

  1. STEP 01

    Scoping call

    We agree the system, the frameworks and the boundary in scope.

    Scope agreed
  2. STEP 02

    Design partner pilot on one system

    REAEGIS runs against one system. Your people approve each change.

    One system in pilot
  3. STEP 03

    Rollout

    More systems follow when the pilot meets the criteria you set.

    More systems

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

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

  • 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