Skip to content

3. Concepts

Explanation + the "why" behind Evidentia's design. Read these if you're extending Evidentia or evaluating whether it fits your environment.

Pages in this section

  • Architecture — 9-package workspace overview + data flow + extension points + design invariants. The foundational page for everything else.

  • Data model — SecurityFinding, ControlGap, CollectionContext, ComplianceStatus enum, OCSF mapping; the frozen-surface contract.

  • Catalog engine — how catalog YAMLs are loaded, validated, indexed; the _load_catalog_data ext-dispatch pattern; manifest regeneration.

  • Crosswalk engine — how crosswalks are loaded; the CrosswalkDefinition schema (including v0.10.6 provenance/verification/verification_note additive fields); OSCAL mapping back-matter.

  • Evidence integrity — CIMD envelope structure; signing keys; verification chain; WORM backend interface.

  • Frozen surfaces and stability — public-API contract; append-only MCP tool surface; semantic-versioning policy.

  • RBAC and multi-tenancy — multi-tenant primitives from v0.9.7 (data + decision layer); v0.11+ CLI/REST wiring direction.

  • Web console security — the standing security model for evidentia serve: the inherited controls and their default postures, the anonymous-by-default disclosure, what each console exposes, and the hardening checklist for a shared deployment.

Architecture → Data model → Catalog engine → Crosswalk engine → Evidence integrity → Frozen surfaces and stability → RBAC and multi-tenancy → Web console security.

After this section, jump to Reference for symbol-level detail or Compliance for framework-specific material.

All eight concept pages above are live.