---
title: "Who secures what in the cloud, and what happens when something breaks"
updated: "2026-11-17"
url: "https://www.etheon.com/company/news/who-secures-what-in-the-cloud"
authors: "Etheon"
published: "2026-11-17"
type: "news"
---

# Who secures what in the cloud, and what happens when something breaks

Your cloud provider runs the hardware; we set up the network and identity and build the code; your team decides access and holds the keys if you choose.

Your cloud provider, our engineers and your team, each with a clear part. The provider runs the data centres and the hardware, we set up the network and identity and build the code, and your team decides who gets access and holds the keys if you choose. The industry calls this division the shared responsibility model. When something breaks, five steps run from the alert to a written review.

## Who is responsible for what?

| Area | Your cloud provider | Etheon sets up | Your team owns | Leads |
| --- | --- | --- | --- | --- |
| Data centres and hardware | Runs them | No part | No part | Your cloud provider |
| Network and firewall | The building blocks | Designed and set up | Approves changes | Etheon |
| Identity and access | The identity service | Roles and single sign-on | Who gets access | Etheon |
| Encryption and keys | The key service | Encryption on by default | Holds the keys, if you choose | Your team |
| Application code | No part | Built, tested and reviewed | Accepts each release | Etheon |
| Data and backups | Storage | Backups, restores tested | What is kept, and how long | Your team |
| Compliance evidence | Its own reports | Evidence for your auditor | The audit itself | Etheon |

## Who holds the keys?

Your team, if you choose. Encryption is on by default, and your provider runs the key service.

## What do you set up from the first commit?

Identity and single sign-on, encryption keys, tenant isolation, data residency and audit logs, so a security review starts from controls that already exist.

- Identity and access set up.
- Encryption keys under your control.
- Audit logs and the evidence for your review.

## What happens when something breaks?

Five steps, from the alert to the review:

1. Alert: monitoring raises an alert to the engineer on call.
2. Acknowledge: a person takes it and says so in your channel.
3. Contain: a circuit breaker, a fallback or a rollback limits the harm.
4. Restore: the service is back; we confirm with you.
5. Review: a written review of what happened, why, and what changes.

## What keeps the systems up once they are live?

The logs, metrics and alerts that watch your systems, the runbooks that say what to do, on-call response during the engagement, and a written review after every incident, so the same failure is less likely to happen again.

- Dashboards and alerts.
- Runbooks.
- Incident reviews.

## Which certifications sit behind it?

We hold [SOC 2 Type II, ISO 27001 and CSA STAR](https://www.etheon.com/company/trust#security): our own certifications; your audit stays yours. We set up the controls and the logging an auditor looks for, and gather the evidence from your systems. The audit itself stays between you and your auditor.

The division and the incident steps are drawn on our [Cloud page](https://www.etheon.com/services/cloud#who-secures-what), and our controls on [Trust](https://www.etheon.com/company/trust#compliance). Tell us your use case and timeline. We reply within one business day.