{"id":195173,"date":"2026-03-12T10:26:00","date_gmt":"2026-03-12T14:26:00","guid":{"rendered":"https:\/\/testing.news-you-need.com\/index.php\/2026\/03\/12\/delaware-supreme-court-expands-cyber-liability-exposure-for-saas-managed-service-providers-shumaker-loop-kendrick-llp\/"},"modified":"2026-03-12T10:45:11","modified_gmt":"2026-03-12T14:45:11","slug":"delaware-supreme-court-expands-cyber-liability-exposure-for-saas-managed-service-providers-shumaker-loop-kendrick-llp","status":"publish","type":"post","link":"https:\/\/testing.news-you-need.com\/index.php\/2026\/03\/12\/delaware-supreme-court-expands-cyber-liability-exposure-for-saas-managed-service-providers-shumaker-loop-kendrick-llp\/","title":{"rendered":"Delaware Supreme Court Expands Cyber Liability Exposure for SaaS &#038; Managed Service Providers | Shumaker, Loop &#038; Kendrick, LLP"},"content":{"rendered":"<p><a href=\"https:\/\/www.jdsupra.com\/legalnews\/delaware-supreme-court-expands-cyber-2724618\/\">Delaware Supreme Court Expands Cyber Liability Exposure for SaaS &#038; Managed Service Providers | Shumaker, Loop &#038; Kendrick, LLP<\/a><\/p>\n<p><a href=\"https:\/\/www.jdsupra.com\/legalnews\/delaware-supreme-court-expands-cyber-2724618\/\">https:\/\/www.jdsupra.com\/legalnews\/delaware-supreme-court-expands-cyber-2724618\/<\/a><\/p>\n<p>Publish Date: <a href=\"publish_date]\">2026-03-12 10:26:00<\/a><\/p>\n<p>Source Domain: <a href=\"www.jdsupra.com\">www.jdsupra.com<\/a><\/p>\n<p>Author: <a href=\"\"><\/a><\/p>\n<p> Using an unordered list, summarize the following article with between 4 and 8 key points. <\/p>\n<p>What the Blackbaud decision means for managed service providers (MSPs) and the clients who rely on them<\/p>\n<p>A recent decision by the Delaware Supreme Court in Travelers Casualty and Surety Company of America v. Blackbaud, Inc. materially shifts the litigation landscape for cybersecurity incidents involving Software as a Service (SaaS) providers and MSPs.<\/p>\n<p>Key takeaways:<\/p>\n<p>\tLower pleading burden for plaintiffs (including insurers)<br \/>\n\tLess emphasis on proximate cause at early stages<br \/>\n\tAggregated claims allowed across multiple customers<br \/>\n\tHigher litigation costs and increased settlement pressure<br \/>\n\tExpanded expectations around what constitutes &#8220;commercially reasonable&#8221; cybersecurity<\/p>\n<p>Bottom line: Cyber incidents are now significantly more likely to survive early dismissal and proceed into expensive discovery.<\/p>\n<p>What Happened<\/p>\n<p>Blackbaud, a SaaS provider hosting sensitive donor data, experienced a ransomware attack exposing highly sensitive personal and financial information.<\/p>\n<p>Its customers (nonprofits and educational institutions):<\/p>\n<p>\tConducted their own investigations<br \/>\n\tIncurred legal, forensic, and notification costs<br \/>\n\tSubmitted claims to their insurers<\/p>\n<p>The insurers then:<\/p>\n<p>\tPaid millions in claims<br \/>\n\tSued Blackbaud as subrogees and assignees<\/p>\n<p>The trial court dismissed the claims twice.<\/p>\n<p>The Delaware Supreme Court reversed, holding that the insurers had adequately pled a breach of contract claim and could proceed.<\/p>\n<p>1. Why This Case Matters (Especially for MSPs)<\/p>\n<p>This decision is not just about Blackbaud\u2014it is about how courts will treat cyber risk allocation across vendors and customers going forward.<\/p>\n<p>Aggregated Claims Are Now Fair Game<\/p>\n<p>What the Court Said<\/p>\n<p>The Court allowed insurers to:<\/p>\n<p>\tBring claims on behalf of 97 customers<br \/>\n\tUse common allegations<br \/>\n\tAvoid individualized pleadings at the outset<\/p>\n<p>Why This Matters<\/p>\n<p>For MSPs and SaaS providers, a single incident can now result in:<\/p>\n<p>For Customers<\/p>\n<p>The easier path to recovery is through:<\/p>\n<p>\tInsurance<br \/>\n\tCoordinated litigation<\/p>\n<p>This significantly increases claim scale and leverage.<\/p>\n<p>2. Proximate Cause Is No Longer a Barrier at the Pleading Stage<\/p>\n<p>The Critical Shift<\/p>\n<p>The lower court dismissed the case for failure to tightly link:<\/p>\n<p>\tSpecific contract provisions \u2192 specific damages<\/p>\n<p>The Supreme Court rejected that approach.<\/p>\n<p>The New Standard<\/p>\n<p>The Court held:<\/p>\n<p>\tProximate cause is typically a fact question<br \/>\n\tPlaintiffs only need to show a reasonable inference of causation<br \/>\n\tDetailed causation analysis can wait until discovery or trial<\/p>\n<p>Why This Is a Big Deal<\/p>\n<p>This is one of the most important aspects of the decision:<\/p>\n<p>Plaintiffs no longer need to prove exactly how each failure caused each dollar loss at the motion to dismiss stage. Instead, they can allege, &#8220;Your security failures led to our response costs.&#8221;<\/p>\n<p>Practical Impact<\/p>\n<p>\tMore cases survive dismissal<br \/>\n\tDiscovery costs increase significantly<br \/>\n\tSettlement pressure rises earlier<\/p>\n<p>For MSPs: You will be forced into fact-intensive litigation sooner<\/p>\n<p>For customers: Lower barrier to pursue recovery<\/p>\n<p>3. &#8220;Commercially Reasonable Security&#8221; is Getting Defined\u2014by Courts<\/p>\n<p>The Court relied heavily on alleged failures that are increasingly viewed as baseline cybersecurity expectations.<\/p>\n<p>The opinion highlights failures such as:<\/p>\n<p>\tNot storing sensitive data on obsolete, unpatched servers<br \/>\n\tLack of multi-factor authentication (MFA)<br \/>\n\tFailure to encrypt sensitive data<br \/>\n\tIgnoring internal security warnings<br \/>\n\tWeak access controls enabling lateral movement<br \/>\n\tExcessive data retention<br \/>\n\tFailure to implement security patches<br \/>\n\tInadequate incident response planning<\/p>\n<p>Emerging Legal Standard for MSPs &#038; SaaS Providers<\/p>\n<p>Courts are implicitly defining &#8220;commercially reasonable security&#8221; to include the following baseline expectations:<\/p>\n<p>\tMFA (especially for remote\/admin access)<br \/>\n\tEncryption of sensitive data (at rest and in transit)<br \/>\n\tPatch management and vulnerability remediation<br \/>\n\tNetwork segmentation and access controls<br \/>\n\tLogging, monitoring, and detection capabilities<br \/>\n\tFormal incident response plans<br \/>\n\tData minimization and retention controls<\/p>\n<p>These are no longer &#8220;best practices&#8221;\u2014they are becoming litigation benchmarks.<\/p>\n<p>4. Litigation Costs Will Increase\u2014Significantly<\/p>\n<p>Because of this decision:<\/p>\n<p>Cases Will:<\/p>\n<p>\tSurvive motions to dismiss<br \/>\n\tMove into expensive discovery<br \/>\n\tRequire:<\/p>\n<p>\t\tForensic analysis<br \/>\n\t\tExpert testimony<br \/>\n\t\tContract-by-contract evaluation<\/p>\n<p>For MSPs:<\/p>\n<p>\tDefense costs increase, even in weak cases<br \/>\n\tInsurance carriers more likely to:<\/p>\n<p>\t\tSubrogate<br \/>\n\t\tAggressively pursue recovery<\/p>\n<p>For Customers:<\/p>\n<p>\tGreater leverage in:<\/p>\n<p>\t\tVendor disputes<br \/>\n\t\tContract renegotiations<br \/>\n\t\tClaims recovery<\/p>\n<p>5. Courts Are Rejecting &#8220;Burden Shifting&#8221; to Customers<\/p>\n<p>A key factual theme:<\/p>\n<p>Blackbaud:<\/p>\n<p>\tProvided a &#8220;toolkit&#8221;<br \/>\n\tInstructed customers to:<\/p>\n<p>\t\tInvestigate<br \/>\n\t\tNotify<br \/>\n\t\tRemediate on their own<\/p>\n<p>The Court viewed this negatively.<\/p>\n<p>Implication<\/p>\n<p>MSPs and SaaS providers cannot simply push incident response downstream.<\/p>\n<p>If your contracts or practices:<\/p>\n<p>\tShift responsibility without support<br \/>\n\tDelay disclosure<br \/>\n\tProvide incomplete information<\/p>\n<p>You may:<\/p>\n<p>\tStrengthen causation arguments against you<br \/>\n\tIncrease liability exposure<\/p>\n<p>6. What This Means for Contracts<\/p>\n<p>For MSPs \/ SaaS Providers<\/p>\n<p>You should revisit:<\/p>\n<p>Security Commitments<\/p>\n<p>\tAvoid vague &#8220;commercially reasonable&#8221; language without definition<br \/>\n\tAlign contractual obligations with actual capabilities<\/p>\n<p>Limitation of Liability<\/p>\n<p>\tEnsure:<\/p>\n<p>\t\tClear caps<br \/>\n\t\tCyber-specific carve-outs<br \/>\n\t\tExclusions for consequential damages<\/p>\n<p>Incident Response Obligations<\/p>\n<p>\tClearly define:<\/p>\n<p>\t\tRoles<br \/>\n\t\tTimelines<br \/>\n\t\tResponsibilities<\/p>\n<p>Data Retention<\/p>\n<p>\tLimit retention to:<\/p>\n<p>\t\tNecessary business purposes<br \/>\n\t\tDefined timeframes<\/p>\n<p>For Customers of MSPs<\/p>\n<p>You should:<\/p>\n<p>\tDemand:<\/p>\n<p>\t\tSpecific security controls (MFA, encryption, etc.)<\/p>\n<p>Final Takeaways<\/p>\n<p>The Blackbaud decision signals a clear trend:<\/p>\n<p>Courts are:<\/p>\n<p>\tLowering procedural barriers<br \/>\n\tIncreasing scrutiny of cybersecurity practices<br \/>\n\tAllowing claims to proceed based on systemic failures<\/p>\n<p>The New Reality<\/p>\n<p>For MSPs and SaaS providers:<\/p>\n<p>&#8220;If you experience a breach, expect to litigate\u2014deeply and expensively.&#8221;<\/p>\n<p>For customers:<\/p>\n<p>&#8220;You have stronger legal footing to recover costs from your vendors.&#8221;<\/p>\n<p>Key Risk Themes Moving Forward<\/p>\n<p>\tAggregated, multi-customer litigation<br \/>\n\tReduced importance of proximate cause at early stages<br \/>\n\tExpansion of &#8220;reasonable security&#8221; expectations<br \/>\n\tIncreased insurer-driven recovery actions<br \/>\n\tHigher litigation and settlement costs<\/p>\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Delaware Supreme Court Expands Cyber Liability Exposure for SaaS &#038; Managed Service Providers | Shumaker,&#8230;<\/p>\n","protected":false},"author":1,"featured_media":195174,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"fifu_image_url":"https:\/\/jdsupra-static.s3.amazonaws.com\/profile-images\/og.7704_1514.jpg","fifu_image_alt":"","footnotes":""},"categories":[15],"tags":[30,24,27],"class_list":["post-195173","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cybersecurity","tag-breach","tag-cybersecurity","tag-vulnerability"],"_links":{"self":[{"href":"https:\/\/testing.news-you-need.com\/index.php\/wp-json\/wp\/v2\/posts\/195173"}],"collection":[{"href":"https:\/\/testing.news-you-need.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/testing.news-you-need.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/testing.news-you-need.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/testing.news-you-need.com\/index.php\/wp-json\/wp\/v2\/comments?post=195173"}],"version-history":[{"count":1,"href":"https:\/\/testing.news-you-need.com\/index.php\/wp-json\/wp\/v2\/posts\/195173\/revisions"}],"predecessor-version":[{"id":195175,"href":"https:\/\/testing.news-you-need.com\/index.php\/wp-json\/wp\/v2\/posts\/195173\/revisions\/195175"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/testing.news-you-need.com\/index.php\/wp-json\/wp\/v2\/media\/195174"}],"wp:attachment":[{"href":"https:\/\/testing.news-you-need.com\/index.php\/wp-json\/wp\/v2\/media?parent=195173"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/testing.news-you-need.com\/index.php\/wp-json\/wp\/v2\/categories?post=195173"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/testing.news-you-need.com\/index.php\/wp-json\/wp\/v2\/tags?post=195173"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}