Release identity and native validation.
This page is the public home for validation Zwall publishes and for how Enterprise release identity is designed to work. Rows fill when a named program is accepted. It is not a compliance logo wall.
What public certification means here
Zwall validates specific topologies and kernels natively. We do not publish reconstructed secondary witnesses, SHA files as customer theater, or internal verdict labels.
Native validation program (schema)
| Signal | How shown |
|---|---|
| Native environments validated | Rows on this page, not screenshots of labs |
| Upgrade paths validated | Named path, not a percentage |
| Rollback paths validated | Named contract |
| Production release identity | Release ID / component hashes at customer-safe granularity |
| Independently reproducible build | Yes/No with date, not a score |
| eBPF ABI / schema version | Version identifiers, not filenames |
| Supported kernel range | Link to Supported Platforms |
| Latest validation date | ISO date |
Current public state
No certified matrix is published yet.
No public native-validation digest is published yet. Enterprise signed-release design is described on Admission and Identity. Community remains a source build. This page does not claim that Zwall is production-certified.
What will never appear as a substitute
We do not use SOC 2, ISO 27001, HIPAA, GDPR certified, pentest-unless-named, PPS, or SLA as substitutes for native release validation.