Category: Security, Privacy, and Data

By default: logs are not encrypted at the application level. Reasons: minimal overhead; high performance; simplicity of integration. Recommended approach: disk encryption (LUKS); strict host access control; network and service isolation. If required, encryption should be implemented at the infrastructure level rather than within the […]

Types of stored data: Suricata events (Flow, DNS, HTTP, TLS, etc.); aggregated statistics; AI analysis results and anomaly labels; internal system states. Retention period: configurable by the administrator; determined by Redis cleanup policies; not hardcoded into the system. By default, the system does not assume […]

Yes. The system is designed to operate: in closed network segments; in isolated (air-gapped) environments; without internet access. The only requirement is local administrative access to the host.

No. Suri Oculus is a fully on-premise system: no SaaS components; no mandatory cloud services; no external network dependencies. Even AI analysis is performed locally.

No. Suri Oculus: does not send telemetry; does not use external APIs; does not transmit data to the developer or third parties. All data remains within your infrastructure.