BlogCassandra

Cassandra Support Under DORA: What the Contract Must Say

Scott Sternloff

By Scott Sternloff, Senior Enterprise Architect

LinkedIn · Updated · 4 min read

On this page

Short answer

If a financial entity runs Cassandra and buys support for it, DORA Article 30 sets minimum contract content and Article 28(8) requires an exit strategy for services that support critical or important functions. This article turns those clauses into questions for a Cassandra support contract: scope, locations, service levels, incident help, audit rights and exit. It is an engineering reading of the regulation text, not legal advice.

# Cassandra Support Under DORA: What the Contract Must Say

If a financial entity runs Cassandra and buys support for it, DORA (Regulation (EU) 2022/2554, in application since 17 January 2025) sets minimum contract content in Article 30 and requires an exit strategy in Article 28(8) for services that support critical or important functions. This article turns those clauses into questions for a Cassandra support contract. It is an engineering reading of the regulation text, not legal advice: whether a given contract is an ICT service, and whether a function is critical or important, is for your legal and compliance teams.

Does a Cassandra support contract fall under DORA?

It can. DORA defines ICT services as digital and data services provided through ICT systems to users on an ongoing basis (Article 3), and an ICT third-party service provider as an undertaking providing them. Article 28(1)(a) leaves the financial entity "fully responsible" for its obligations even when it uses such providers. Article 28(3) requires a register of information covering all contractual arrangements for ICT services, which means a support contract belongs in the register if your counsel treats it as in scope.

Article 30 has two layers. Paragraph 2 applies to all ICT services contracts; paragraph 3 adds more where the service supports a critical or important function. A Cassandra ring behind payments, trading or customer-facing availability is the usual example.

What does Article 30(2) require in every contract?

Paragraph 2 lists nine elements. Mapped to Cassandra support:

Article 30(2)Question for a Cassandra support contract
(a) Description of services, subcontracting conditionsWhich versions, distributions and deployment types are covered? May the provider subcontract engineers, and under what conditions?
(b) Locations of service and data processingWhere do engineers work from, and where do logs, heap dumps and diagnostics go? Is advance notice promised before locations change?
(c) Availability, authenticity, integrity, confidentialityHow is access to your nodes controlled and recorded? What happens to diagnostic bundles?
(d) Access, recovery and return of data on insolvency or terminationWhat does the provider hold of yours at the end, and in what format is it returned?
(e) Service level descriptionsWritten response targets per severity, and how changes are notified
(f) Assistance during an ICT incident at no extra cost or a cost fixed ex anteIs incident response inside the fee, or billed by the hour after the fact?
(g) Cooperation with competent and resolution authoritiesIs that stated in the contract?
(h) Termination rights and minimum noticeNotice periods and triggers
(i) Participation in security awareness and resilience trainingWill provider staff take part where you require it?

What does Article 30(3) add for critical or important functions?

Paragraph 3 adds six requirements: full service levels with "precise quantitative and qualitative performance targets", notice and reporting duties when something may affect the provider's ability to deliver, business contingency plans and security measures the provider implements and tests, cooperation in the entity's threat-led penetration testing, rights of access, inspection and audit for the entity and its authority, and exit strategies with a mandatory adequate transition period.

For Cassandra this turns vague promises into testable ones:

  • Targets: "response targets from 15 minutes, by plan" is a number, but DORA asks whether you can monitor it. Ask for response and update intervals per severity and how misses are reported.
  • Contingency: who covers if the named engineer is unavailable, and across which time zones? Ask for a 24/7 rota, not a business-hours queue.
  • Audit: ask what an on-site or remote audit looks like for a small provider, and how Article 30(3)(e) rights are exercised without exposing other clients.
  • Exit: a transition period only helps if runbooks, access lists and cluster knowledge are written down and handed back.

What should an exit plan for a Cassandra estate contain?

Article 28(8) requires exit strategies that let the entity leave without disrupting business, limiting regulatory compliance or harming service quality to clients, and plans that are "sufficiently tested and reviewed periodically". For a support contract the plan is smaller than for a platform, but it should still exist:

  1. An inventory of clusters, versions, keyspaces, drivers and the people with access.
  2. Runbooks for repair, compaction, node replacement and upgrade written so another team can use them.
  3. Access revocation steps and a transition period in the contract.
  4. A named alternative: another provider, or in-house operation, and what it would take.

Article 29 asks you to weigh concentration risk, including whether a provider is "not easily substitutable". Cassandra's open source licence (Apache 2.0) and the fact that several providers support it make substitution a design choice you can document.

Where does AceMQ stand?

AceMQ provides 24/7 Cassandra support across the Americas, EMEA and APAC with response targets from 15 minutes, by plan, and quote replies within 1 hour. Support typically runs $24,000-72,000 a year (USD), by SLA, scope and deployment. AceMQ gives no legal advice.

Sources

  • Regulation (EU) 2022/2554 (DORA), Articles 3, 28, 29, 30 and final provisions, EUR-Lex: eur-lex.europa.eu/eli/reg/2022/2554/oj/eng (HTML text via CELEX:32022R2554), read 17 Nov 2026.

Frequently Asked Questions

Does DORA apply to my Cassandra support contract?

Only your legal team can say. DORA covers ICT services supplied to financial entities, and Article 30 applies to those contracts; stricter terms apply when the service supports a critical or important function.

When did DORA start to apply?

17 January 2025, per the regulation's final provisions.

What must the contract say about service levels?

Article 30(2)(e) requires service level descriptions; for critical or important functions Article 30(3)(a) requires precise quantitative and qualitative targets that let you monitor and correct.

Do we need an exit plan for a support provider?

For services supporting critical or important functions, Article 28(8) requires exit strategies, and Article 30(3)(f) requires a transition period in the contract.

Can a smaller provider meet audit rights?

Article 30(3)(e) requires access, inspection and audit rights, and allows agreeing alternative assurance levels where other clients' rights are affected. Ask how the provider would deliver each.

Scott Sternloff

Author

Scott SternloffSenior Enterprise Architect

Senior Enterprise Architect at AceMQ. Writes the technical coverage here: RabbitMQ, Kafka and Redis architecture, clustering and migrations.

Talk to an engineer

Need a hand with Cassandra?

Senior engineers who run it in production. Get a quote or a free consultation, no sales pitch.

Free Consultation

Get Expert Eyes on Your Cassandra Environment

Whether you're troubleshooting a production incident, planning a migration, or want a second opinion on your architecture — our team is ready. No pitch, just answers.

Email Us