Integrations
Core42
How Telonic runs inside your own Core42 cloud environment, with every component in your environment and your own encryption keys.
On this page
Core42 is a UAE-based provider of cloud and AI infrastructure, including sovereign cloud services (cloud services designed to keep data and operations under national control). If your organisation has already chosen Core42 for its workloads, Telonic can be deployed into your own Core42 environment. Every Telonic component runs inside that environment, and stored data can be encrypted with keys you manage. Only operational health signals, which contain no customer data, are sent to Telonic, and you can switch them off.
What running in your own Core42 environment means
| Aspect | How it works |
|---|---|
| Where it runs | Every Telonic component runs inside your Core42 environment. The location is recorded in your agreement |
| Where processing happens | All processing for your deployment runs in the region you choose, unless you explicitly choose a language model provider outside it |
| Encryption | Connections use TLS (Transport Layer Security, the standard encryption for data in transit) version 1.2 or higher. Stored data is encrypted with AES-256 (the Advanced Encryption Standard, using 256-bit keys) |
| Your keys | You can use customer-managed keys (encryption keys your organisation creates and controls) |
| What reaches Telonic | Operational health signals only, containing no customer data. You can switch them off |
| Backups | Backups and disaster recovery copies are encrypted and stay in the same country as your deployment |
How it connects
Your cloud team provides the environment and grants the access described below. Telonic deploys and runs the software there, and the computing capacity your deployment needs is sized with your team during implementation. Your agents connect to your other systems from inside your own environment, over routes your network team controls.
Telonic engineers reach your deployment only when you approve it. Access is limited to named engineers, working from the UAE or your chosen country, and is time-limited and logged. If you later decide to move to another hosting option, the move is carried out as a migration agreed with you in advance: data is moved encrypted and never leaves the countries your agreement permits.
Running Telonic in an environment you have already approved means the deployment sits inside the controls your organisation has accepted for that environment. Whether that meets a particular regulator's or procurement body's requirement is for your own teams to decide. See Data protection in the UAE and Saudi Arabia.
Permissions
| Permission | Needed for | Default |
|---|---|---|
| Deploy and update Telonic components in the resources set aside for them | Installing, updating and supporting your deployment | Each access needs your approval, and is time-limited and logged |
| Use of your encryption keys | Encrypting stored data | Only if you choose customer-managed keys |
| Send operational health signals to Telonic | Monitoring the health of your deployment | On. You can switch it off |
| Access to other resources in your environment | Not needed | Not requested |
Telonic can only reach what you have granted, and only when you approve it.
In practice
An Abu Dhabi property developer has approved Core42 for systems that hold customer data.
- Its cloud team sets aside resources in the developer's Core42 environment and grants deployment access for the installation window.
- Telonic deploys the agent, which connects to the developer's CRM (the system that holds its customer records) and maintenance system from inside the same environment.
- The security team sets customer-managed keys and reviews the operational health signals before deciding whether to keep them on.
- For each later update, the developer approves the access, and every session is logged.
What your team controls
- The environment and network routes.
- The encryption keys, and whether to use them.
- Whether operational health signals are sent, and each approval of engineer access.
Related
- Cloud hostingIntegrations
- Hosting and data residencySecurity and data protection
- EncryptionSecurity and data protection
- Data protection in the UAE and Saudi ArabiaLegal and compliance
- What we need from your IT teamIntegrations
Product names and logos are trademarks of their owners. Their mention shows systems Telonic connects to and does not imply partnership or endorsement.