# SSX360 SSX360 is the hosted control plane for Agent Authorization Authority: portable, offline-verifiable Ed25519 authorization records for commits, MCP tools, and agent runs — plus Scroll Gate CI, evidence-pack export, and consultative Authorization Pilots for regulated teams. Tagline: They receipt the model call. We receipt everything the machine does. Positioning locks: - Notary, not watchtower — proof you own; NHI control planes rent a dashboard. - Hardware leash (SE050) — possession-factor root of authorization in validation / pilot, not GA. - FS AI RMF / CRI door — evidence aligned to Govern / Map / Measure / Manage; readiness language only, never certification. Commercial model: - Matrix Scroll SDK: Free (Apache-2.0) — local signing, MCP Trust Scanner, tool pinning / rug-pull defense - Authorization Pilot, Ledger Pilot, Snapshot, Enterprise: by consultation — no public self-serve checkout - Primary CTA: Request Pilot Consultation → https://ssx360.com/contact?intent=pilot - Book 30 min: https://ssx360.com/book ## Capabilities - Signed commit-time provenance (Matrix Scroll Protocol) - Scroll Gate CI enforcement - Offline-verifiable evidence packs (ssx360.evidence-pack.v1) - Framework mapping: FS AI RMF, PCI DSS v4.0.1 Req 6.5.1, DORA, EU AI Act Article 12 readiness ## Rug-pull / tool-pinning defense AI agent tools can change after approval. Matrix Scroll takes a cryptographic snapshot at authorization; any edit (one character) fails verification before the agent runs the tool. Drift exits with code 2 and fails CI — zero cloud dependency. Free, open source, offline: `pip install "matrixscroll==0.6.0"` ## Cryptographic Ledger framing (Jul 2026 deck) - AI authorization blindspot: GPG signs commit metadata as if a human wrote agent-generated logic — no proof of which tool generated the lines. - Triple contrast: Inventory is not authorization · Activity is not accountability · Portable cryptographic proof. - Solution stack: Sign (Matrix Scroll Protocol) → Govern (SSX360 Control Plane) → Prove (SE050 hardware — pilot/preview, not GA). - Envelope anatomy: commit-envelope.v1.json — actor_type, tool, signature.value — verify offline at ssx360.com/verify. - Provenance showdown: Sigstore proves a key built an artifact in CI; Matrix Scroll proves who authorized the agent before push. - Evidence transformation engine: Layer 1 Protocol (Sign) · Layer 2 Governance · Layer 3 Hardware (Prove). - Financial workflows: fraud/AML, credit/lending, KYC/KYB, payments — authorization records, not certification. - Privacy firewall: repo contents stay local; only envelope metadata crosses to SSX360. You own the proof; you do not rent it. ## Hardware developer workflow (BRD alignment) Objective: secure developer workflow where a hardware security device authenticates developers, tracks authorized agent activity, enforces policy, and provides audit visibility. Public workflow (pilot / preview — SE050 not GA): 1. Device authentication — USB-C connect, physical button press, fleet enrollment, session authorization, possession factor 2. Policy enforcement — merge gate controls, organization rules, instant revocation on incident 3. Cryptographic signing — commits, pull requests, and agent actions recorded with identity and timestamp 4. Audit-ready evidence — SIEM export, Prometheus/Grafana monitoring stack; offline evidence packs for assessors Repository roles (enterprise pilots): - Project manager — repository permissions, merge approvals - Developer — hardware-authenticated sessions on assigned repos - Security / GRC — audit log review, compliance readiness checks (not certification) Audit event categories: hardware auth, enrollment/revocation, commits/PRs/merges, policy violations, security events. ## Active R&D (honest scope) - SE050 secure-element: PoC bench-validated Jul 2026 — firmware validation / pilot, not GA - Post-quantum overlays: optional ML-DSA / SLH-DSA for software signers - SIEM / enterprise monitoring - SOC 2 Type I readiness targeted Q3–Q4 2026 — readiness only, never “SOC 2 certified” ## FS AI RMF funnel (SEO + generative discovery) Primary hub: https://ssx360.com/fs-ai-rmf Funnel pages: - FS AI RMF overview: https://ssx360.com/fs-ai-rmf - FS AI RMF controls mapping: https://ssx360.com/fs-ai-rmf/mapping - Free FS AI RMF questionnaire: https://ssx360.com/fs-ai-rmf/checklist ### FS AI RMF — common questions (honest scope) Q: What is FS AI RMF? A: The Financial Services AI Risk Management Framework — a voluntary CRI/FSSCC framework with control objectives for AI systems. SSX360 maps a scoped SDLC / change-management slice for agent-assisted code, not the full framework. Q: Does SSX360 certify FS AI RMF compliance? A: No. We produce offline-verifiable evidence aligned to specific control objectives. Not certification, attestation, or regulator endorsement. Never say “compliant” or “required by.” Q: How is this different from Sigstore? A: Sigstore proves a commit was signed by a key. SSX360 proves who authorized which agent to act, packaged as a portable offline-verifiable evidence record. Q: How is this different from NHI (Oasis, Astrix)? A: NHI control planes govern access in a dashboard you rent. SSX360 produces portable proof you own — the record survives without our platform. Geographic focus: United States fintech, regulated banking innovation teams, and payment infrastructure companies evaluating agentic AI controls. Commercial links: - Homepage: https://ssx360.com/ - Book a 30-min call: https://ssx360.com/book - Pilot consultation: https://ssx360.com/contact?intent=pilot - Agent authorization docs: https://ssx360.com/docs/agent-authorization - MCP Trust Scanner (live): https://matrixscroll.com/scan - FS AI RMF hub: https://ssx360.com/fs-ai-rmf - Trust model: https://ssx360.com/trust - Enterprise brief: https://ssx360.com/enterprise - Engagements: https://ssx360.com/pricing - Design partner: https://pilot.ssx360.com - Docs: https://ssx360.com/docs - Browser verifier: https://ssx360.com/verify Open protocol: - Matrix Scroll: https://matrixscroll.com/ - PyPI: https://pypi.org/project/matrixscroll/ - GitHub SDK: https://github.com/SSX360/matrixscroll Important scope (Honest limits): - SSX360 stores identity, billing, policy, and audit metadata — not private source code. - Emulated software signing (Ed25519) ships today. Production hardware signing is preview/roadmap only — NXP SE050 PoC bench-validated Jul 2026, not GA until productized. - Evidence exports map to DORA, PCI DSS v4.0.1 Req 6.5.1, FS AI RMF, NIST SSDF, EU AI Act Article 12 readiness. They do not constitute certification, SOC 2 attestation, or customer endorsements. - FS AI RMF coverage is a scoped SDLC / change-management slice — not all control objectives. - We govern agents, not people — no keystroke or productivity surveillance.