What sets us apart
Post-quantum encryptionOn by default. Even in the FIPS builds.
FIPS 140-3 validatedCMVP #5191. On public record at NIST, active through August 2029.
The proof, at a glance
One platform in place of a stack of tools.
Evidence a security reviewer can confirm today.
FIPS 140-3 (CMVP #5191)
VALIDATED
Validated cryptography with a public certificate number
FIPS 140-3 crypto module, CMVP certificate #5191
Post-quantum encryption
ON BY DEFAULT
On by default, even in the FIPS builds
The Console shows how many connections used post-quantum encryption, per service.
NIST SP 800-207
BUILT-IN
Fully aligned to the NIST Zero Trust standard
Zero Trust Architecture
Stoplight
BUILT-IN
Twelve controls, each marked In place, Not in place, or Not turned on. Export the evidence for any one.
12 Stoplight controls
CISA ZTMM
BUILT-IN
Measured pillar by pillar against the CISA Zero Trust Maturity Model
One of 5 Stoplight frameworks
DoD Zero Trust 2.0
COVERED
Shows what is in place, pillar by pillar
Measured against 5 frameworks, including DoD Zero Trust and CISA's Zero Trust model
DoD Impact Levels
DEPLOYED
One platform from unclassified to classified, no re-architecture
IL2 through IL6+
OWASP Core Rule Set
ON BY DEFAULT
Blocks known attack patterns before they reach your application, once blocking is on
WAF filter, inline on every proxy
OWASP LLM Top 10
DETECT MODE DEFAULT
Detects all ten OWASP LLM Top 10 risks
Detection for all 10 OWASP AI risks, plus sensitive data detection
SPIFFE / SPIRE
ACTIVE
Every workload proves its own identity, no shared secrets to leak
SPIRE deployed by the mesh controller, or bring your own
Forensic Audit Trail
ACTIVE
A record of every request
A JSON audit event for every request
Change log
ACTIVE
Every human change on record: who, what, and the before and after. Kept 395 days.
Settings change log
Platform self-check
BUILT-IN
Greymatter.io monitors its own parts and shows the evidence behind every status.
Platform view in the Console
User (Pillar 1 of 7)
NIST 800-207
An assessor sees verified identity behind every access, not a username and a guess
OIDC, PKI, and CAC or PIV with OCSP checks
Device (Pillar 2 of 7)
SPIFFE / SPIRE
Certificate management stops being a manual, error-prone job for your team
Cryptographic identity for each workload, with access limited to learned callers once strict mode is on
Application & Workload (Pillar 3 of 7)
CMVP #5191
SPIRE gives each workload its own identity
Per-workload cryptographic identity, Policy Enforcement Points
Data (Pillar 4 of 7)
FIPS 140-3
mTLS inside the mesh, TLS to the outside
mTLS encryption in transit, least-privilege access by policy
Network & Environment (Pillar 5 of 7)
NIST 800-207
Each port admits only the identities that actually call it
Learned access becomes the allowlist under STRICT
Visibility & Analytics (Pillar 6 of 7)
DoD Zero Trust
Security teams stop guessing what happened and see every step recorded as it happens
A record of every request
Automation & Orchestration (Pillar 7 of 7)
DoD Zero Trust
Enroll a namespace and its workloads join the mesh
Zero-touch tenant onboarding
Additional resources
Go deeper.
Deeper reading for anyone who wants more than a summary.
FAQ
Straight answers.
The questions a security review actually asks, answered directly, with no vendor hedging.

