Workspace / Overview
connecting to GitHub
Endpoint CBOM + AI-BOM

One tile per endpoint.
One mosaic of every cipher and every model.

Endpoint CBOM and AI-BOM with baseline drift and downgrade alerts, signed attestations, and SIEM-native rules verified on a real manager.

19SIEM rules
CDX 1.6schema validated
Ed25519DSSE attestations
...latest release (live)
Real-time

Live data

Both panels fetch fresh data every time you open this page and refresh on their own. The left one reads the public GitHub API for this project. The right one runs a real cryptographic probe on your own browser, the same idea the collector applies to an endpoint.

Project pulse (GitHub API)

loading
Latest releaseloading...

Unauthenticated public API, refreshed every 2 minutes. If GitHub rate limits this network, values show as unavailable instead of stale numbers.

Your browser crypto posture

probing
Proberunning...

Runs locally and sends nothing anywhere. It tests what this browser can actually do, and flags algorithms a quantum computer would break.

Real tool output

Sample CBOM and drift alert viewer

These files were produced by running tesserabom 0.3.0 twice on a controlled demo endpoint: a baseline scan, then a second scan after a TLS server dropped from 1.3 to 1.2, a certificate was replaced by a weaker one, a model was added, and an MCP server launch command changed. Nothing here is hand-written. Paths were rewritten to /opt/demo and the host renamed. Pick a tab, or replay the alert stream the SIEM would receive.

loading sample

Baseline scan

Second scan (drift detected)

Inventories

Two inventories auditors keep asking for

Which cryptography is really running here, and how ready is it for post-quantum migration? Which AI models and MCP servers are on these machines? The SIEM gives you excellent telemetry, and the 4.14.x release notes searched in November 2026 show no native answer to either.

C

CBOM

Certificates, TLS endpoint posture, SSH key exchange and crypto libraries, flagged for quantum vulnerability. CycloneDX 1.6.

AI

AI-BOM

Local model files (hashed, header-checked), MCP server configs, and local AI runtimes. Credentials are never read, only key names.

Δ

Drift and downgrade

A baseline remembers every asset. Alerts fire on changes, and on downgrades such as TLS 1.3 falling to 1.2.

✓

Signed attestations

Each BOM can be wrapped in a DSSE envelope signed with Ed25519, so an inventory can be proven untampered.

Pipeline

How it works

A collector runs on each endpoint, writes the BOMs, and prints one JSON line per finding. The SIEM reads those lines through the command wodle and applies 19 rules tagged for PCI DSS, DORA and NYDFS lookups.

Scancertificates, TLS, SSH, models, MCP
Comparebaseline drift and downgrades
AttestCycloneDX plus DSSE signature
AlertSIEM decoder, rules, dashboards
Install

Quick start

pip install .

tesserabom keygen --dir /etc/tesserabom
tesserabom scan --out /var/lib/tesserabom/out \
  --baseline /var/lib/tesserabom/baseline.json \
  --sign-key /etc/tesserabom/tesserabom-signing.key \
  --tls-port 443

tesserabom verify out/cbom.dsse.json --pub /etc/tesserabom/tesserabom-signing.pub
tesserabom diff old/cbom.json new/cbom.json

SIEM content (decoder, rules, agent snippet) is in the siem/ folder and in each release as a zip. scripts/logtest_docker.sh repeats the manager test.

Landscape

How it differs

Found in a November 2026 search that was broad but not exhaustive: to our knowledge, no open-source project combines endpoint collection, CBOM plus AI-BOM, a downgrade baseline, signed attestations and SIEM-native rules. This is not a claim to be first.

ProjectOverlapsDoes not do
CBOMkit, Sonar CryptographyCycloneDX CBOMSource and image scanning only. No AI-BOM, drift, signing or SIEM.
cdxgenBOMs, MCP and model discovery at build timeNot a continuous endpoint monitor. No SIEM content.
AC-ScannerCBOM with run comparisonRemote scanner, AGPL-3.0. No AI-BOM, signing or SIEM.
Trusera ai-bom, agent-bomAI-BOM from models and MCP configsNo CBOM, SIEM content or signed BOMs.
Community shadow-AI rulesSIEM rules for unapproved AIDetection only. No BOM output or signing.
Transparency

Honest limits

  • Post-quantum TLS status depends on what the probing client can negotiate.
  • SSH status uses sshd -T only as root.
  • tesserabom never launches MCP servers, so it pins the configured launch spec but cannot see a server change what it advertises.
  • Attestations use Ed25519, a classical signature.
  • The 5.x series and a remote agent reporting to a separate manager are untested.
  • Compliance tags are lookup aids, not statements of compliance.