Security
Practices


Last revised October 2026

1. Scope

This page describes how Kyber Technologies Inc. (“Kyber”) thinks about security for https://kybertechnologies.us and, at a high level, for Atlas, Command, and Sentinel. Product deployments are governed by the customer agreement, any security exhibit, and the operator’s own authorization to operate.

2. The public Site

The marketing Site is hosted on Cloudflare. Traffic to the Site is served over HTTPS. We keep the attack surface small: the Site does not host customer telemetry, SCADA data, or production control paths.

Demo and contact forms are designed so you can send a message without uploading operational datasets. Do not paste credentials, keys, network diagrams that are restricted, or other sensitive artifacts into a public form.

3. Product security posture

Kyber builds software and hardware that sit on or beside critical infrastructure. Our design intent is:

  • Least privilege and explicit authorization for any action that changes grid, facility, or edge state.
  • Separation between the public Site and systems that ingest telemetry or issue commands.
  • Edge execution on Sentinel so control decisions can stay on the installation when that is the right architecture.
  • Auditability — operators should be able to see what Atlas inferred, what Command proposed, and what Sentinel executed.

4. What we do not claim here

This page is not a SOC 2 report, FedRAMP package, or authority to operate. If you need a questionnaire, architecture review, or controlled documentation for a procurement, request it through the Trust Center or a demo conversation. We will not invent certifications we have not completed.

5. Your obligations on the Site

You may not probe, scan, or attempt to break the Site except under a written authorization from Kyber. You may not use the Site to store or transmit malware, or to interfere with other visitors. We investigate suspected abuse and will work with law enforcement when warranted.

6. Vulnerability reports

If you believe you have found a security issue in the Site or in a Kyber product you are authorized to test, email kybertechnologies.inc@gmail.com with “Security” in the subject. Include enough detail to reproduce the issue and avoid accessing data that is not yours. We will acknowledge good-faith reports.

7. Incidents

If Kyber becomes aware of a security incident that affects personal information collected through the Site, we will take steps to contain it and notify affected people and regulators as required by law. Product incidents are handled under the applicable customer agreement.

8. Related documents

See the Trust Center for how to request a review, the Privacy Statement for Site data, and the Terms of Use for acceptable use. All four are linked from Documents in the footer.