Halo Knox
Govern every data source individually.
Not all data carries the same risk, so Halo doesn’t treat it the same. With Halo Knox, the customer’s IT team sets the governance level for each data source, based on what that source requires. In the strictest setting, Sealed, Crisp sees nothing: no access to the software, no access to the data. Other sources can be opened to trusted consultants, or to Crisp support, when the IT team decides.
Choose the level of control
Three levels, set per data source
The customer’s IT team picks the class for each source and can change it at any time.
Halo Knox
Sealed
Customer only
- The customerFull access
- Their consultantsNo access
- CrispSynthetic demo data only
Highest control. Crisp never has access to the data.
Halo Knox
Delegated
Customer and consultants
- The customerFull access
- Their consultantsAccess the customer grants
- CrispNo access
Bring in trusted consultants. Crisp stays out.
Halo Knox
Supported
Customer, consultants, and Crisp
- The customerFull access
- Their consultantsAccess the customer grants
- CrispAccess the customer grants
Where Crisp support and optimization add the most value.
Halo Knox Sealed
Halo runs in your cloud. Crisp sees nothing.
Halo is one of many programs your IT team already runs inside its own environment. The data owner’s data flows to the customer, the customer controls access, and Crisp stays on the outside.
Customers run Halo inside their own cloud. With Sealed, Crisp has no accounts, no connections, and no access to the software or the data. It’s the model banks, telecoms, and pharmaceutical companies already use with vendor software.
Customer’s cloud
Software installed and run by the customer. Halo is one of many.
Data governance
Access control, lineage and auditing
- Only the customer has access to the data
- The customer holds credentials, network controls and encryption keys
- Access is governed by the cloud platform, not the vendor
- No Crisp or contractor accounts, VPN or support tunnels
- Crisp supports with synthetic data only
- The customer’s IT admin approves everything sent to Crisp
What Crisp can’t do
- Log in. Crisp has no accounts in the environment
- Connect by VPN or support tunnel
- See, query, or store the data
- Install anything without the customer choosing to
What Crisp can do
- Receive a bug report, only if the customer’s administrator sends it
- Ship updates the customer installs when ready
- Reproduce and fix issues on synthetic data
- Provide audit evidence for security reviews
Example
One data estate, three levels
Most customers run a mix: Sealed for the most sensitive data, Delegated for consultant work, and Supported where Crisp adds the most value.
5 Sealed3 Delegated2 Supported
- Partner data 1Sealed
- Partner data 2Sealed
- Partner data 3Delegated
- Internal data 1Supported
- Internal data 2Sealed
- Internal data 3Delegated
- Syndicated data 1Supported
- Syndicated data 2Delegated
- Data source 1Sealed
- Data source 2Sealed
Governed by your cloud
Who holds the controls
Sign-in, data access, audit, keys, and network all run on the customer’s own cloud platform and are managed by the customer’s IT team. Pick a cloud to see the tools behind each answer.
| The question | The answer | How, on Databricks |
|---|---|---|
| Who can sign in? | Only people the customer’s own identity system approves, with multi-factor authentication. | Single sign-on and MFA through the customer’s identity provider. Automated workloads use service principals, not shared passwords. |
| Who sees which data? | Access is set down to individual rows and columns, and sensitive fields are masked. | Unity Catalog privileges, row filters, and column masks, plus tag-based rules that apply across a whole catalog. |
| Who touched what? | Every access is recorded, and the customer can trace data end to end. | Column-level lineage and audit logs, available as system tables. |
| Who holds the keys? | The customer. Data is encrypted with keys the customer controls. | Customer-managed keys. |
| Where can it connect from? | Only trusted networks, with private connectivity available. | IP access lists and private connectivity. |
Governed by Databricks Unity Catalog, managed by the customer’s own IT team.
| The question | The answer | How, on Snowflake |
|---|---|---|
| Who can sign in? | Only people the customer’s own identity system approves, with multi-factor authentication. | Single sign-on and MFA through the customer’s identity provider, with roles and service users for automated workloads. |
| Who sees which data? | Access is set down to individual rows and columns, and sensitive fields are masked. | Horizon access policies: row access policies and masking policies, plus tag-based rules. |
| Who touched what? | Every access is recorded, and the customer can trace data end to end. | Access history and lineage, available to query. |
| Who holds the keys? | The customer. Data is encrypted with keys the customer controls. | Customer-managed keys. |
| Where can it connect from? | Only trusted networks, with private connectivity available. | Network policies and private connectivity. |
Governed by Snowflake Horizon, managed by the customer’s own IT team.
| The question | The answer | How, on Google Cloud |
|---|---|---|
| Who can sign in? | Only people the customer’s own identity system approves, with multi-factor authentication. | Single sign-on and MFA through the customer’s identity provider, with IAM roles and service accounts for automated workloads. |
| Who sees which data? | Access is set down to individual rows and columns, and sensitive fields are masked. | BigQuery row-level and column-level security, with policy tags, managed through Dataplex. |
| Who touched what? | Every access is recorded, and the customer can trace data end to end. | Dataplex lineage and Cloud Audit Logs. |
| Who holds the keys? | The customer. Data is encrypted with keys the customer controls. | Customer-managed encryption keys in Cloud KMS. |
| Where can it connect from? | Only trusted networks, with private connectivity available. | VPC Service Controls and private connectivity. |
Governed by Google Cloud Dataplex and BigQuery, managed by the customer’s own IT team.
Proof
Evidence for your security team
Crisp supports the data owner’s own review of the deployment.
SOC 2 Type II
Crisp provides its SOC 2 Type II report.
ISO 27001 and 27017
Crisp is certified, and provides the certificate.
Vendor risk assessments
Crisp completes vendor risk assessments and supports review by the data owner’s security team.
Questions data owners ask
Can each data source have a different level?
Yes. The customer’s IT team sets Sealed, Delegated, or Supported for each source, based on that source’s governance requirements, and can change it at any time.
With Sealed, can Crisp employees see our data?
No. Crisp has no accounts, VPN connections, or support tunnels into the customer’s environment, and no credentials to it.
What leaves the environment?
Only bug reports. A report describes a fault in terms of code, configuration, schema, and error behavior, with no data. It goes to the customer’s IT administrator first, and only the administrator can send it to Crisp.
How can we verify this?
Everything runs in the customer’s own cloud, so the customer’s audit logs show who and what accessed the data. Crisp also provides its SOC 2 Type II report and ISO certificates.
What if Crisp has a security incident?
Crisp doesn’t host, receive, store, or query the data, so there is no copy of it at Crisp.
How does Crisp fix problems it can’t see?
On synthetic data. Crisp reproduces issues and tests on data that mirrors the structure of the customer’s feeds without containing any of their values.
Your data. Your rules. Your class.
Talk to us about running Halo in your own environment.