Our approach

Security is a design constraint for everything we build, not a layer added afterward. The practices below apply to the CyberAIX platform, our corporate environment, and the people who operate both.

Platform security

Encryption. Data is encrypted in transit using current TLS versions and at rest using industry-standard algorithms. Customer-managed keys are available for supported deployments.

Isolation. Each customer's data and configuration are logically isolated. Universal-collector and hybrid deployments keep telemetry inside the customer's network boundary until policy routes it outward.

Access control. Role-based access with least-privilege defaults, single sign-on integration, and multi-factor authentication for all administrative access.

Audit logging. Every configuration change, policy activation, and agent action is recorded with the actor, timestamp, and before and after state. Logs are available to customers and retained according to the service agreement.

Bounded automation. Autonomous agents act only within limits declared in configuration. Actions affecting compliance-designated destinations require human approval.

Secure development

  • Code review is required for every change.
  • Dependencies are scanned continuously and patched on a defined schedule based on severity.
  • Static and dynamic analysis run in the build pipeline.
  • Infrastructure is defined as code and reviewed like application code.
  • Production access is time-limited, logged, and requires justification.

Corporate security

  • Company devices are centrally managed with disk encryption, screen lock, and endpoint protection enforced.
  • All staff complete security awareness training on joining and annually.
  • Background checks are performed where permitted by local law.
  • Access to systems is provisioned by role and removed promptly on departure.

Vulnerability management

We welcome reports from security researchers. If you believe you have found a vulnerability in a CyberAIX product or website, contact us through the contact form and mark the message "Security". We ask that you give us reasonable time to investigate and remediate before public disclosure, and we commit to acknowledging reports promptly and keeping you informed of progress.

Incident response

We maintain a documented incident response plan that is tested regularly. Affected customers are notified without undue delay and in accordance with contractual and legal requirements, with details of the incident, its impact, and the steps taken.

Business continuity

Platform components are deployed redundantly across availability zones. Configuration and metadata are backed up on a defined schedule and restoration is tested periodically. Universal collectors buffer locally during connectivity loss so that telemetry is not lost.

Compliance

We align our controls with widely recognized security frameworks and undergo independent assessment. Customers can request our current assessment reports and control documentation through their account team, subject to a confidentiality agreement.

Questions

For security questionnaires, documentation requests, or to report a concern, use the contact form and mark the message "Security".