Information-defense application
Protection that reports what is actually protected.
Citadel coordinates network and endpoint defenses around an approved information journey, keeping configured architecture, observed state, deployment, and qualification separate.
The system in context
Information defense architecture.

What it delivers
Capability, made specific.
DNS and destination controls
Abuse defense and bounded containment
Privacy-minimized evidence logging
Endpoint posture and screen-capture defense
Optional two-hop infrastructure defense
Deployment and commercial shape
Fit the operating environment.
Embedded network and endpoint defense
Standalone one-gateway mode
Optional two-hop deployment
Backend/platform or managed-service form
Current evidence boundary
What can be said now.
Evidence is mixed and assigned ring by ring. Current governed records identify stronger evidence for Rings 1–6 and 8, while Rings 7, 9, and 10 retain specific deployment or qualification boundaries. Citadel must not be described as wholly deployed, universally qualified, or independently certified.
Portfolio publications
Written about the system, in public.
These are the existing Iberion and Meridian articles most directly related to this capability. They establish the portfolio’s published problem framing and architectural thesis; they are first-party publications, not independent certification.
Standards and external context
Independent sources behind the problem space.
These standards, official references, and research sources provide external context. They do not independently verify Iberion implementation, deployment, performance, or qualification.
Continue exploring