Skip to main content

Now accepting design partners.

Request a demo

Remediation

Fixed by pull request. Approved by a person.

REAEGIS prepares the fix, opens the pull request in your repository, and proves the result. A reviewer who is not the author approves every change.

ORION-1 / pull request #482

Approved

Rebuild api-gateway
on a hardened image

Opened by REAEGIS for finding 0482

SI-2GitHuborion-1/api-gateway

Dockerfile

Removed: FROM node:20.11.0Added: FROM registry1.dso.mil/…/nodejs20:20.11.1

Why this fix

Rebuilds on a hardened, signed base image from Iron Bank. No application code changes.

Approval gate

Prepared by
REAEGIS
Reviewer
Maya Reyes
Merged
14:21

Enforced

AC-5 Reviewer is not the authorCM-3 Change recorded

The same finding,
two ways to close it.

Finding 0482, a vulnerable container base image, followed from the first alert to a closed POA&M item.

Manual

By hand

Each step is a hand-off.
Nothing links one to the next.

  1. Scanner alert

    INBOX

    Arrives by email or dashboard

  2. Ticket

    TICKET

    Opened and assigned by hand

  3. Manual patch

    SHELL

    Applied by an engineer

  4. Screenshot as evidence

    PNG

    Pasted into a document

  5. Spreadsheet
    POA&M update

    XLSX

    Row edited by hand

  6. Re-typed into the system of record

    MANUAL ENTRY

    Entered again, field by field

Ends withA screenshot and a spreadsheet row

Signed at every step

With REAEGIS

Each step is an event in one signed record.

  1. Finding mapped to controls

    FINDING 0482 · SI-2 · RA-5

    GrypeAXIOM
  2. Fix prepared

    Hardened image, isolated branch

    Iron BankARE
  3. Pull request opened

    #482 · orion-1/api-gateway

    REAEGISGitHub
  4. Reviewer approves

    Maya Reyes, not the author

    Maya Reyes, reviewerAC-5
  5. Three checks pass

    Finding absent. Nothing new.
    Gate passes.

    3 of 3RAMPART
  6. POA&M item closes
    with signed evidence

    ITEM 0117 · ANCHORED IN REKOR

    SigstoreCHRONICLE

Ends withOne signed record, anchored in Rekor

Code or infrastructure.
Each fix takes
its own path.

A vulnerable package and a misconfigured cluster are not fixed the same way. Each one goes to the right repository, the right checks, and the right approver.

Code remediation

Packages, base images,
application flaws

Application repository
  1. 01

    Finding

    TrivyGrypeSemgrep

    Vulnerable package or base image

    FINDING 0482 · SI-2

  2. 02

    Change

    REAEGISGitHub

    Pull request to the
    application repository

    Dockerfile
    Removed:FROM node:20.11.0
    Added:FROM registry1.dso.mil/…/nodejs20:20.11.1
  3. 03

    Check

    ChainguardIron Bank

    Rebuilt on a hardened image

    Re-scanned before review

  4. 04

    Approval

    Maya Reyes, reviewerAC-5

    Maya Reyes approves

    Reviewer is not the author

  5. 05

    Verification

    RAMPARTPHAROS

    Re-scan passes. Gate clears.

    Confirmed in production

Infrastructure remediation

Cloud settings, cluster policy, STIGs

Infrastructure repository
  1. 01

    Finding

    CheckovOpenSCAPTenable

    TLS 1.0 enabled at ingress

    FINDING 0519 · SC-8

  2. 02

    Change

    REAEGISGitHub

    Pull request to the
    infrastructure repository

    ingress.tf
    Removed:min_protocol_version = "TLSv1_0"
    Added:min_protocol_version = "TLSv1_2"
  3. 03

    Check

    TerraformKubernetes

    Plan and policy check before apply

    1 TO CHANGE · 0 TO DESTROY

  4. 04

    Approval

    Change control board memberChange control board memberChange control board memberCM-3

    Change control board approves

    Boundary change recorded

  5. 05

    Verification

    RAMPARTPHAROS

    Applied. Drift cleared.

    Confirmed on the next sync

One signed record, whichever path the fix took

CHRONICLE

  • POA&M item closed
  • Evidence signed
  • Anchored in Rekor

Three checks pass, or the finding stays open.

Every fix is verified before its POA&M item can move. Each result is signed.

  1. PASS

    Check 01: Original finding absent
    from the re-scan

    14:02Finding 0482PRESENT

    14:31Finding 0482ABSENT

  2. PASS

    Check 02: No new findings introduced

    14:0241 open findingsBASELINE

    14:3140 open findings0 NEW

  3. PASS

    Check 03: The gate that failed now passes

    14:02VULNERABILITYFAIL

    14:29VULNERABILITYPASS

Scanners that run the checks

GrypeSemgrepCheckovTrivyOSV-ScannerTrufflehogNative audit

Fails closed. A failed check stops the pipeline and is recorded by CHRONICLE.

What it takes to close a POA&M item.

Five conditions, each with its own evidence. Then two phases: fix verified, production confirmed.

ORION-1 / POA&M / item 0117

Closed

Base image vulnerability, api-gateway

POA&M ITEM 0117 · FINDING 0482

SI-2RA-5

  • Change approved by a second person

    Met

    Approval record. The reviewer is not the author.

    Maya Reyes, reviewerAC-5

    Evidence produced: sha256:71c0…e9a4Time: 14:19

  • Pull request merged

    Met

    Merge commit on the protected branch.

    #482

    Evidence produced: sha256:b3f8…02d7Time: 14:21

  • Build succeeds

    Met

    Build log and image digest.

    Evidence produced: sha256:0e6a…7c15Time: 14:24

  • Gate passes on the remediated branch

    Met

    Gate result, signed.

    RAMPART

    Evidence produced: sha256:d95b…48f0Time: 14:29

  • Three verification stages pass

    Met

    Re-scan results from all three stages.

    Evidence produced: sha256:4a27…bb61Time: 14:31

5 of 5 conditions met

Any unmet condition keeps the item open

Closes in two phases

  1. Phase 114:31Fix verified
  2. Phase 215:04Production confirmed

The ISSO validates the closure

Evidence chain

Signed
  • FINDING
  • REMEDIATION
  • VERIFICATION
  • APPROVAL RECORD
  • GATE PASS
sha256:9f2c41d07be3…a41eRekor index 1429071132026-10-08 15:04:20Z

Works with the network cable cut.

In an air-gapped deployment, a deterministic rule engine handles most findings inside the enclave.

RULE ENGINE COVERAGE

About 80%

of findings handled by the rule engine
in air-gapped deployments,
with no external service

ENCLAVE BOUNDARY · AIR-GAPPED

Inbound onlyCAC and PIV

  1. Finding
  2. REAEGIS

    Deterministic rule engineNo external service
  3. Fix
  4. Internal log
  • Rule engine, no external service
  • Remaining findings

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