Integration
Evidence Proof Map
Pick a framework and an obligation. Apeiris shows you the controls that address it, the exact evidence that would substantiate each one, its blocking posture, and how strong the mapping is — plus, where coverage is only partial, the stated gap. Composed live from the published coverage manifests and the domain control matrices; it invents nothing. This is a planning aid, not a compliance determination.
How to read a proof chain
- supported
- Apeiris controls directly address this obligation (coverage verdict:
direct). - partial
- Partial coverage — the gap note says what Apeiris does and does not reach.
- fit
- How strongly a single control maps to the obligation: direct · supporting · partial · adjacent.
- anchored
- The framework's taxonomy was captured from its primary text and the cited id is validated in CI. asserted = cited but not yet ingested as an anchor.
- automated
- How each required evidence artifact is verified — automated (machine-collectable: logs, tests, config, monitoring) · human review · third-party audit or certification · attested document. The "Machine-collectable" count above is how much of the fabric a machine can gather. From the typed evidence-artifact map.
Verdicts come from the human-curated coverage manifests; per-control evidence, objective, and fit are read live from the control matrices, and each evidence artifact is typed by how it is verified. "Mapped" is not "satisfied": a mapping states a relationship — the evidence is what a consumer must actually produce.