rune-audit

Auditing and compliance tracking for the RUNE platform.

rune-audit collects, verifies, and reports on security and compliance evidence across the RUNE ecosystem. It verifies SLSA Level 3 build provenance, manages VEX (Vulnerability Exploitability eXchange) documents, and generates IEC 62443 evidence matrices.

Architecture

rune-audit
  collect      Gather SBOMs, CVE scans, VEX documents from all repos
  vex          Manage and validate OpenVEX documents
  compliance   IEC 62443 evidence matrix and gap analysis
  slsa         SLSA Level 3 provenance verification
  report       Full, summary, and delta audit reports
  config       Display current configuration

Evidence sources: GitHub Attestations API, SBOM files, CVE scan results, OpenVEX documents.

Outputs: Rich terminal tables, Markdown reports, JSON exports.

Installation

pip install rune-audit

Or for development:

git clone https://github.com/lpasquali/rune-audit.git
cd rune-audit
pip install -e ".[dev]"

Quick Start

# Verify SLSA L3 provenance for a single repo
rune-audit slsa verify rune --tag v0.0.0a2

# Verify SLSA across all ecosystem repos
rune-audit slsa verify-all --tag v0.0.0a2

# Show IEC 62443 evidence matrix
rune-audit compliance matrix

# Show compliance gaps
rune-audit compliance gaps

# Validate VEX documents
rune-audit vex validate

# List VEX statements
rune-audit vex list

# Generate full audit report
rune-audit report full

# Show configuration
rune-audit config show

External OSS projects (compliance-config & packs)

For non-RUNE repositories, use compliance-config.yaml and builtin packs (rune-audit init, rune-audit sr2 verify --pack …). Documentation lives in rune-docs: External projects (rune-docs#227–#232).

Multi-repo SR-2 matrix (HTML / JSON / Markdown): rune-audit sr2 dashboard --base-path .. (see rune-docs#212).

Supported Evidence Types

Configuration

Optional YAML config file: rune-audit.yaml

Compliance Context

• IEC 62443-4-1 ML4: This repository aligns with IEC 62443-4-1 Maturity Level 4 secure development requirements.
• SLSA Level 3: Build provenance is verified against all five SLSA L3 requirements (provenance exists, signed, trusted builder, version-controlled source, isolated build).

Documentation

Full documentation is consolidated in rune-docs.

License

Apache License 2.0. See LICENSE.