Trust center
Ultraviolet Observability runs entirely in your environment. Your traces, logs, metrics, profiles and session replays are collected, stored and queried on infrastructure you control, and none of it is ever sent to us. It runs fully air-gapped if you want it to.
That changes the usual vendor security review. There is no hosted copy of your data to protect, breach or subpoena. What’s left to review is the software you run, and the small amount of account information we keep to license it. This section covers both.
At a glance
Section titled “At a glance”| Question | Answer |
|---|---|
| Where is my telemetry stored? | In the ClickHouse database the chart installs in your cluster, on your volumes. |
| Does any of it reach Ultraviolet? | No. Not in air-gapped mode, not in connected mode. |
| What does reach Ultraviolet? | In connected mode only: your license ID and node counts, for automatic renewal. See Data and connections. |
| Can Ultraviolet access my install? | No. There is no remote access, support tunnel or vendor account. |
| Can it run with no internet access? | Yes. Air-gapped installs are fully supported, including license renewal and verifying releases. |
| How do I know the software is ours and unmodified? | Every image and chart is signed, with an SBOM and build provenance you can check offline. See Verifying signed artifacts. |
| What does the node agent need? | Five Linux capabilities, read-only /sys and /proc, and read access to pods and nodes. See Sensor permissions. |
| How is access controlled? | Single sign-on with your identity provider, three roles, scoped API tokens and a full audit trail. See Security controls. |
In this section
Section titled “In this section”- Data and connections: every connection the product makes out of your environment, what each one carries, and the subprocessors behind our license service.
- Sensor permissions: what the node agent can access, what it records, and what it deliberately leaves out.
- Security controls: authentication, roles, audit, encryption in transit, and how the product limits its own access.
- Verifying signed artifacts: signatures, SBOMs and build provenance for every release.
- Third-party software: the open-source components we ship and their licenses.
- Reporting a vulnerability: how to reach us, and what to expect when you do.
Compliance
Section titled “Compliance”We don’t yet hold a SOC 2 report or an ISO 27001 certification, and we haven’t had a third-party penetration test. We’ll say so here when that changes.
Because the product runs in your environment, most of what those audits cover for a hosted service falls under your own controls: where data lives, who can reach it, how it’s backed up and how long it’s kept. Our side is the license service and how we build and sign releases, both described in this section.
If your review needs a completed security questionnaire, such as SIG Lite or CAIQ, ask us at security@uvobservability.com and we’ll fill it in.