Security is a product boundary, not a feature checkbox.
NetSeed is designed around separated planes, local key material, and site-side enforcement.
Design principles
- Control, transport, and site-side enforcement are separated so no one component needs the full access context.
- Private key material is generated and retained on the participating node or device.
- Access is scoped to services and policy decisions rather than inheriting a flat private network.
Operational security
Audit, device trust, revocation, policy controls, and security-event export are covered in Security Operations. This page describes the public security posture; product-specific controls depend on the deployed edition and agreement.
Report a vulnerability
Do not include exploit details in public channels. Send a concise report, affected component, reproduction steps, and a safe contact method to hello@netseed.info. We will coordinate follow-up privately.
Security questions
For architecture reviews, deployment questions, or customer security questionnaires, contact hello@netseed.info.