Security & Data Protection

Technical and organizational controls protecting customer assets on the Vioro platform

Operated by Cyze AS in Norway (Org. No. 932 904 500), Vioro is engineered for security-conscious DevOps, platform, and compliance teams. We combine a zero-access monitoring architecture with application-layer field encryption, strict access governance, and European data residency.

This overview summarizes our technical and organizational measures (TOMs) for vendor security reviews. Formal contractual commitments are detailed in our Privacy Policy, Data Processing Agreement (DPA), and Sub-Processors Registry.

Zero-Access Architecture

Most security and observability vendors expand your attack surface by requiring privileged agents, runtime SDKs, or repository tokens. Vioro eliminates vendor blast radius by operating purely from the outside:

  • Zero server agents or plugins: Nothing is installed inside your containers, virtual machines, or CMS instances.
  • Zero injected client scripts: Vioro never injects third-party JavaScript snippets into your production pages or checkout flows.
  • Zero credentials or source access: Continuous monitoring requires no read access to private Git repositories, CI/CD secrets, or cloud IAM roles.

Data Protection & Cryptography

Transport Security

All external traffic between browsers, customer integrations, and Vioro platform endpoints is encrypted over HTTPS using TLS 1.3. Legacy protocol versions (TLS 1.0, 1.1, and 1.2) are rejected, and plaintext HTTP requests are strictly redirected to HTTPS.

Application-Layer Field Encryption

Sensitive customer records are encrypted at the application layer prior to database persistence using ChaCha20-Poly1305 (Authenticated Encryption with Associated Data, AEAD). Unlike standard volume-level disk encryption, application-layer AEAD ensures both confidentiality and cryptographic tamper detection: plaintext values for protected fields are never written to storage, and every high-availability database replica and automated backup snapshot stores ciphertext only.

Protected Data CategoryScope
Monitored Asset InventoryTarget domain names (FQDNs), display labels, and operational notes
Vulnerability & Health FindingsScan outputs, detected software inventories, and structured security event records
Alerting & Delivery EndpointsNotification recipients, routing configurations, and alert thresholds
Organization & User IdentityUser names, email addresses, organization records, and identity provider subject mappings

Encryption keys use per-record key derivation with support for key rotation.

Access Control & Authorization

  • Strict organization and resource scoping: Every authenticated platform request is bound to verified identity and organization permissions, isolating domain configurations, alert routes, and extended vulnerability findings to authorized organization members.
  • Strong administrative authentication: Privileged administrative access follows strict least-privilege governance, enforcing multi-factor authentication (backed by FIDO2 / WebAuthn hardware security keys on supported control planes) and cryptographic key-based authentication for server access.
  • Private network isolation: Internal services, management interfaces, and backing data stores run exclusively on isolated private networks and are unreachable from the public internet.

European Infrastructure & Operational Resilience

Vioro operates under Norwegian jurisdiction (Cyze AS) and hosts core compute, storage, and monitoring infrastructure exclusively on 100% European-owned providers within the EU/EEA, keeping customer security posture data outside the reach of the US CLOUD Act. See our Sub-Processors Registry for full provider and data-flow disclosures.

  • High availability & backups: Core databases run in replicated high-availability topologies backed by redundant storage and automated daily backups.
  • Network resilience: Upstream DDoS mitigation protects public ingress endpoints against volumetric and protocol-layer attacks.
  • Self-hosted observability: Platform health, performance metrics, and error telemetry are processed exclusively on Vioro-operated European infrastructure rather than third-party APM or error-tracking services.

Secure Engineering & Vulnerability Management

  • Systems-grade Rust engineering: Core backend services and inspection engines are built in Rust, combining strict compile-time safety with predictable, high-throughput concurrency. Untrusted external responses and JavaScript bundles are inspected statically without headless-browser execution risks, keeping multi-tenant monitoring fast and deterministic.
  • Automated CI security gates: Every build must pass automated static analysis, license compliance checks, and dependency vulnerability audits against public security advisory databases before deployment.
  • Regular security assessments: CompTIA PenTest+ certified security engineers conduct regular architecture reviews and internal penetration testing aligned with the OWASP Top 10.

Probe Ethics & Domain Authorization

Vioro performs outbound checks strictly within clear ethical and rate-limited boundaries. Standard passive checks (HTTPS availability, TLS certificate validation, HTTP security header inspection, and client-side JavaScript bundle analysis) issue non-invasive HTTP(S) requests clearly identified by the VioroBot user agent.

Extended security diagnostics and deeper perimeter hygiene checks require explicit domain ownership verification before activation. Supported verification methods include:

  • DNS TXT record on the target zone
  • HTML <meta> verification tag served on the target origin
  • Standards-compliant /.well-known/security.txt token (RFC 9116)

Domain verifications are re-validated daily; extended security checks pause automatically if ownership verification lapses.

Incident Response & Responsible Disclosure

In the event of a confirmed security incident or personal data breach, Cyze AS follows a documented incident response workflow:

  1. Containment & root-cause analysis: Isolate affected components, preserve forensic evidence, and remediate the underlying issue.
  2. Regulatory notification: Notify the Norwegian Data Protection Authority (Datatilsynet) within 72 hours where required under GDPR Art. 33.
  3. Customer notification: Notify affected customers without undue delay, and within 72 hours, in accordance with our Data Processing Agreement.

Reporting a Vulnerability

If you identify a potential security vulnerability in Vioro, please report it to (also published at /.well-known/security.txt). We acknowledge responsible disclosures within 5 business days and coordinate remediation transparently with reporters.


Last updated: 2026-11-04