Security pack
Shared responsibility
Security is shared: some of it is ours, some is your company's.
| Area | IMS Creator | Your company |
|---|---|---|
| The service: servers, network, encryption, patching, backups, monitoring | ✔ | |
| The application's security, testing and updates; keeping companies apart | ✔ | |
| Incident response, and telling you within 72 hours | ✔ | Telling us of anything suspicious; your own notifications |
| Who has an account, and their roles | ✔ Your company admins invite, approve and remove people, and review roles | |
| Approved email domains | Checking a domain belongs to you when we approve it by hand | ✔ Approving and verifying your domains; removing those you no longer use |
| Authenticators | Offering them, and asking for the code first | ✔ Requiring them for everyone (recommended), and keeping recovery codes safe |
| The break-glass account | Sealing and issuing its password | ✔ Keeping it in your safe, and reviewing every use |
| The audit log | Keeping it complete and tamper-evident | ✔ Reviewing it, or exporting it to your own monitoring |
| Claude | Sealing your key, using it only for your work, alerting on unusual use | ✔ Your agreement with the provider, its region and data settings, spend limits, revoking keys |
| What goes into documents | Processing it only to provide the service | ✔ Deciding what your documents contain, and reviewing what Claude proposes before approving it |
| Plugins | Reviewing, signing and sandboxing them | ✔ Choosing which to install, and the permissions you consent to |
| Your people's devices and browsers | ✔ Kept up to date and protected | |
| Leaving | Exporting your information, then deleting it, and confirming | ✔ Asking for the export, and keeping it |