Skip to main content
Security

A security platform
must be secure itself.

Cisodium is built by security practitioners for security teams. We hold our own platform to the standard our customers use it to meet: here is how we protect it, and how to tell us if you find a weakness.

How we protect the platform

Six layers, one programme.

Security programme

We run our own information security management system in Cisodium.

  • Our risks, controls, policies, assets, vulnerabilities and incidents live in the same platform our customers use.
  • Controls are mapped to ISO/IEC 27001 and the other frameworks the platform supports. We do not claim certifications we do not hold; ask us for the current status of audits.
  • Everyone who works for us is bound by confidentiality and completes security awareness training.

Hosting and infrastructure

The hosted platform runs in the European Union.

  • Amazon Web Services in Frankfurt, Germany, with backup copies in a second EU region (Ireland).
  • Hardened, regularly patched hosts; administrative access only through restricted, key-based access.
  • Signing keys and secrets are held in managed key services and secret stores, never in source code.
  • Need full control? Run Cisodium on your own infrastructure, including isolated networks.

Data protection and isolation

Your data is encrypted and kept apart from every other customer's.

  • Encryption in transit with TLS 1.2 or higher, and encryption at rest.
  • A dedicated deployment per customer or, in shared environments, database row-level security between organisations.
  • Integration credentials are stored encrypted and used only to call the systems you connect.
  • We process customer data only on your instructions, under our Terms of Service and Data Processing Agreement.

Identity and access

You decide who sees and changes what, and every action is recorded.

  • Single sign-on with SAML 2.0 and OpenID Connect (for example Microsoft Entra ID, Okta, Google or Duo) and multi-factor authentication.
  • Role-based access control, with roles mapped from your directory groups.
  • An activity log of user and administrator actions that you can review.
  • Our staff access customer environments only when needed, with least privilege, and that access is logged.

Secure development and releases

Every change is reviewed, tested and shipped in a verifiable way.

  • Code review before every merge, and automated tests on the code.
  • Dependencies are monitored for known vulnerabilities; critical and high findings are fixed first.
  • On-premises releases and the endpoint agent are cryptographically signed, and installations verify the signature before applying an update.

Monitoring, backup and response

We watch the service, keep recoverable copies and have a plan for incidents.

  • Hosts and services are monitored for availability and security events, with alerts to our team.
  • Encrypted automatic backups on a rolling cycle of up to 90 days, with tested restores.
  • A documented incident response process. If an incident affects your data, we notify you without undue delay, as our agreements and the law require.
Vulnerability disclosure

Found a weakness? Tell us first.

We welcome reports from security researchers and treat them seriously. If you act in good faith and follow this policy, we consider your research authorised.

How to report

Email security@cisodium.com and include:

  • the affected service, URL or product version
  • a description of the issue and its impact
  • steps to reproduce, with any proof-of-concept code, requests or screenshots
  • how to contact you, and whether you want to be credited

What we commit to

  • Acknowledge your report within 3 business days.
  • Share our initial assessment within 10 business days and keep you informed.
  • Aim to fix critical issues within 30 days and others within 90 days.
  • Credit you once it is fixed, if you wish. We do not run a paid bug bounty.

In scope

  • cisodium.com and its subdomains, including the hosted platform and sign-in service
  • The Cisodium platform software, including on-premises releases
  • Cisodium endpoint and collection agents

Out of scope

  • Denial of service, load testing and spam
  • Social engineering, phishing and physical attacks
  • Third-party services we use (report those to the provider)
  • Scanner output without demonstrated impact, missing headers on pages without sensitive content, and self-XSS

Rules of engagement

  • Test only accounts and data you own or are allowed to use. Never access, change or delete other people's data; if you reach it by accident, stop and tell us.
  • Do only what is needed to show the issue, and do not degrade the service for others.
  • Keep the issue confidential until it is fixed and we have agreed a disclosure date; we aim for coordinated disclosure within 90 days.

Safe harbour

If you follow this policy, we will not take legal action against you or report you to law enforcement for your research, and if a third party does, we will make clear that your research was authorised. This policy does not cover third-party systems or customers' on-premises installations without their permission.

For customers

Security documents, on request.

Reviewing Cisodium for your organisation? Ask us for the documents your security and procurement teams need.

  • Data Processing AgreementGDPR Article 28 terms for customer dataOn request
  • List of sub-processorsWho processes customer data, and whereOn request
  • Security questionnaire answersStandard questionnaires and your ownOn request
  • Architecture and data flowsHosting, isolation and integration designUnder NDA

Questions about security?

Customers write to support@cisodium.com; everyone else to sales@cisodium.com.