AscendBridge™: provenance is what crosses
Every classified-bound pipeline automates cleanly until it reaches the boundary. Then a person carries an artifact across and the chain of custody dies. Why that no longer works, and how to build the crossing as engineering rather than ceremony.
The engineering talent, the tooling and the iteration speed all live on the low side. The mission lives on the high side. Every organization delivering classified-bound software solves the same problem, and most solve it the same way: build low, then carry the result across by hand.
That crossing is usually the only manual step left in an otherwise automated pipeline, and it is where the chain of custody breaks. Once an artifact moves on burned media against a tribal checklist, the high side cannot prove what it received, the low side cannot prove what it sent, and the evidence the pipeline generated so carefully stops at the boundary.
The deliverable is the artifact plus a provable chain of custody. If provenance does not cross, nothing useful crossed.
Why this stopped being an inconvenience
Hand-carried promotion has been awkward for years. In 2026 it became a compliance problem.
FedRAMP's Consolidated Rules for 2026 took effect on 4 July, and its Vulnerability Detection and Response and Vulnerability Evaluation and Reporting rules carry a 7 December 2026 adoption deadline with certification revocation named as the consequence. CISA's Binding Operational Directive 26-04, issued 10 June 2026, reprioritizes remediation around public exposure and known exploited status rather than severity score alone. DoD's Cybersecurity Risk Management Construct, announced September 2025 as the successor to the legacy RMF, contemplates withdrawing an authorization the moment risk thresholds break.
You cannot continuously demonstrate the state of a system you deploy to by hand every two weeks.
A manual crossing forces a choice between two bad answers. Either the high side reports on what it believes it is running, an assertion rather than evidence, or it re-derives that state independently, duplicating the entire scanning and attestation apparatus inside the enclave at cleared-labor rates.
Where the cost sits
Cleared engineering is the most expensive input in federal software. The instinct is to economize on headcount; the savings are in economizing on what has to be done cleared at all.
In our delivery experience, true high-side work is a minority of the effort on a typical mission application. The rest is application code that could have been built low, duplicated tooling, manual promotion ceremony, and re-testing to re-establish a state that was already known on the other side of the boundary.
The rule is not “never build high.” It is never build high what could have been built low, in our experience 80% or more of a typical mission application. That figure is a delivery observation, not a published benchmark.
Why the common approaches fail
| Approach | Failure mode |
|---|---|
| Build everything high-side | Cleared-only labor for all work, starved tooling, iteration in days rather than minutes: the most expensive software you will ever ship, and the slowest |
| Ad hoc manual transfer | Every promotion is a one-off event: burned media, tribal checklists, no provenance. Findings surface high, where fixes are slowest |
| Shadow parallel stacks | A second toolchain maintained by hand drifts from the first. Parity drifts and “it worked low” stops predicting anything |
| Trusting the manifest nobody checks | A signed artifact whose signature is never re-validated inside the enclave is a signed artifact in name only |
The pipeline
Four layers, each with explicit interfaces and its own evidence surface. The layering matters because the high side is frequently the part you are least free to change, and the design has to survive that.
Foundation: map before you design. Cloud topology, enclave separation, identity and access, CI/CD maturity, artifact management, current authorization status, and, critically, what the high side will permit. The most common discovery is that the high side already contains most of what the pipeline needs (a registry, an orchestrator, a logging stack), installed for other purposes and usable with configuration rather than procurement.
Orchestration: gated approvals across domains. CI/CD spanning classification domains with gated approvals and secure relay through the cross-domain solution. The gates are where human judgement belongs; everything around them is mechanized so that judgement is visible.
Security overlay: enforced at every stage. Isolation, access control, artifact validation and signing enforced at each stage rather than inspected afterwards. This is the difference between a control you can demonstrate and one you can describe.
Monitoring: on both sides. A promotion that fails should be as legible as one that succeeds, and an incident on the high side should trace back to the low-side commit that introduced it.
What crosses, and what it carries
| Travels with the artifact | What it lets you prove |
|---|---|
| Cryptographic signature | What arrived is what was built, unaltered |
| Software bill of materials | Exactly what is inside it, component by component, at deploy time |
| Scan results and policy attestations | It passed the gates, and which gates those were |
| Build provenance: source, commit, pipeline | Which code, built by which pipeline, from which commit |
| Manifest re-validated in the enclave | The high side verified independently rather than trusting the label |
Re-validation is not optional. A signature checked only on the low side proves the artifact was correct before it crossed. The whole point of the boundary is that the two sides do not trust each other by default; verification inside the enclave is what converts a manifest from paperwork into evidence.
Parity: making “works low” mean something
The unspoken premise of building low is that low-side results predict high-side behavior. That premise is only as good as the parity between the two environments, and parity decays silently. A package updated on one side, a configuration drift, a version pin nobody carried across, and the low-side test suite is testing a different system.
Environment definitions expressed as code and promoted through the same pipeline as the application; base images built once, low, and promoted rather than rebuilt independently; drift detection on both sides reported to the same place; and an explicit registry of what is legitimately different.
How engagements are structured
Three tiers, distinguished by how much of the work Ausper carries. Every tier begins with the same foundation assessment, because designing against an unmapped high side is how pipelines get built twice.
Tier 1: Blueprint + Initial Consulting. Foundation assessment across both domains, target pipeline architecture and gate model, identity and approval model, gap register with sequencing. You execute; we advise at defined checkpoints.
Tier 2: Blueprint + Advisory. Everything in Tier 1, plus named advisors on a working cadence, policy and manifest schema design, review before each accreditation gate, and a parity and drift strategy.
Tier 3: Full Execution. Everything in Tier 2, plus pipeline implementation on both sides, signing, manifest and re-validation wiring, monitoring and incident-response integration, and an operator handover.
What AscendBridge™ is not
- Not a cross-domain solution. An accredited CDS moves data across the boundary. AscendBridge™ orchestrates around whichever one your program is authorized to use.
- Not a way around a CDS or its accreditation. Nothing here substitutes for the approval process that governs the boundary.
- Not an authorization. It produces the evidence an authorization depends on.
- Not the end of cleared labor. It reduces how much of the work has to be done cleared.
- Not a fix for a high side you cannot change. Where the enclave is fixed, the design adapts to it. The foundation assessment finds that out in week one.
Ten questions before you start
- Which accredited cross-domain solution serves your program, and who owns its accreditation?
- How does an artifact cross today, and could you reconstruct any given crossing six months later?
- Does anything verify a signature on the high side, or is the manifest taken on trust?
- What fraction of your codebase requires the high side to build?
- Do low and high run the same base images, and would you know if they diverged?
- Who is authorized to approve a promotion, and is that enforced or conventional?
- When a vulnerability is disclosed, how long before you know whether the high side is affected?
- Can you produce an SBOM for what is currently deployed high, without asking anybody?
- Is your high-side deployment state derived from evidence, or from a record somebody maintains?
- If an authorizing official asked to see the last ten promotions, what would you show them?
Common questions
What is AscendBridge™?
What crosses the boundary, and what carries it?
Why not develop on the high side and avoid the transfer entirely?
Sources
- DoD Instruction 8540.01, Cross Domain Policy: governs how cross-domain solutions are authorized and deployed, and recognizes access, transfer and multilevel solution types.
- NSA and the National Cross Domain Strategy and Management Office, Raise the Bar: security requirements for the design, development, assessment and deployment of cross-domain solutions.
- ODNI, Intelligence Community Directive 503: risk management for IC information technology systems.
- NIST, SP 800-53 Rev. 5 and SP 800-218, Secure Software Development Framework.
- CNSSI 1253, Security Categorization and Control Selection for National Security Systems.
- FedRAMP, Consolidated Rules for 2026 and the VDR/VER notice; CISA, BOD 26-04; DoD Cybersecurity Risk Management Construct.
The 80% build-low figure and the effort split above are Ausper delivery observations, not published research.
Related reading
Get the 11-page whitepaper
Everything on this page, in depth: the four layers, what travels with an artifact and what each item lets you prove, the parity problem, a ten-question readiness instrument, engagement tiers, and nine cited sources. Name, title and business email. No charge.
Get access
Name, title, and business email. We’ll email you a one-time access code, then the PDF unlocks on this page.
How does an artifact cross today?
And could you reconstruct any given crossing six months later? The answer to that one question is usually the whole engagement.
Talk to Ausper