Client-controlled runtime
The product retains its own local configuration, audit trail, licence state and operational workflow.
Web and DNS security
Cybstyx Phylaxis Orama Web Shield
Web and DNS security filtering, policy enforcement, URL reputation, internet control, and web evidence. The product is positioned as a client-controlled security engine with professional deployment, audit and integration boundaries.
Core responsibility
What this product is built to handle.
DNS/web policy, categories, overrides and filtering evidence
- DNS and web policy
- Categories and allow/block lists
- Reputation events
- Override approvals
- Proxy/DNS service health, reports, and audit
Deployment and control model
Roles: Super Admin, Web Security Admin, Operator, Reviewer, Auditor, Service Account
Authentication: Local RBAC with MFA; optional Eidon SSO; filtering service authentication.
Linked with: Optional Unified Cyber Security Command Center adapter, Eidon identity, Nomion, Chronyx timeline, Tekmerion evidence, Keraunix response, Nyxara feeds, and Kleidion secrets.
Boundary: Filtering continues with cached policy if Unified Cyber Security Command Center or external reputation feeds are offline.
Cybstyx model
Standalone product, optional ecosystem connection
The product should be strong alone first. Integration improves visibility and coordination, but it must not become an uncontrolled dependency.
Command-center option
SecOwl can receive approved events and show posture or evidence if the client enables the adapter.
Bounded integration
Products may connect to identity, evidence, licence, secrets or timeline services when policy allows.
Every action has context
Administrative changes, service events and proof exports should remain auditable.