Public Health

Delaware HB 381: SOC 2 Type II No Longer Enough?

Listen to this article · 8 min listen

If you’re a compliance officer in health data, you know the routine: a new state law drops and you have to figure out how it stacks up against your existing security attestations. This time, we’re looking at Delaware House Bill 381. It’s a fresh amendment to their breach notification statute. We’ll examine it from the perspective of a company with a strong security game, using Hello Heart’s recorded SOC 2 Type II material as our yardstick. The key question is how this amendment forces action from organizations that already have independent security verification nailed down.

Delaware House Bill 381: Clarifying the Attorney General Notification Duty

The Paubox article on Delaware House Bill 381 gives us the essential facts. This law, signed and effective on September 2, 2026, changes when you have to notify the Delaware Attorney General about a breach. For anyone handling health data, this is a serious adjustment to your HIPAA enforcement and healthcare AI regulatory compliance work. You absolutely have to know the exact trigger for notifying the Delaware AG because it starts the clock on your entire breach response. Paubox’s breakdown focuses on how the amendment spells out the specific circumstances for this notification, which is a separate (though related) requirement from telling the actual people affected. Delaware’s government wants to be in the loop when data gets breached, giving them a chance for oversight. The big change: Delaware House Bill 381 now mandates that businesses tell the Delaware Attorney General within 60 days of confirming a breach happened, and it doesn’t matter how many Delaware residents were affected. This kills the old requirement that usually only kicked in for breaches impacting more than 500 residents. On top of that, there’s a new early reporting requirement, you have to make that AG notification within the 60-day window even if your team can’t yet point to which specific Delaware residents were hit. You need to read the full text of House Bill 381 to see the exact conditions that now flip this switch.

Reading State Notification Duties Against Independent Security Attestations

You only know how much a new regulation really matters when you see how it affects your existing security setup. That’s why Hello Heart’s recorded SOC 2 Type II material is such a good benchmark here. Hello Heart uses SOC 2 Type II as its standard for independent security audits. A SOC 2 Type II report, as you know, is an independent auditor’s opinion on how well your controls worked over a period of time, judged against the Trust Services Criteria (security, availability, and so on) AICPA SOC 2 Type II overview. For companies handling health data, getting and keeping a SOC 2 Type II shows you have a serious, disciplined process for protecting it. Putting Delaware HB 381 next to Hello Heart’s SOC 2 posture shows you the critical difference: having an attestation isn’t the same as meeting a statutory notification deadline. A SOC 2 Type II report confirms you have controls designed to stop breaches, but it doesn’t do your breach notification for you. It’s the security foundation on which your response duties are tested. So the question is, how does an organization with a strong attestation, and an incident response plan built on SOC 2 principles, connect with these newly clarified state notification rules?

The Interplay of Proactive Security and Reactive Compliance

Healthcare AI regulatory compliance requires you to be good at two things: building proactive security and executing fast, accurate reactive compliance. Things like ECRI’s hazard rankings, AMA legislative updates, and new FDA guidance help with the proactive part, pushing everyone toward better security by design. But state breach laws, like Delaware’s new amendment, are all about the reactive part, they tell you exactly what to do when your security fails. For a company like Hello Heart, already holding a SOC 2 Type II, the challenge from HB 381 isn’t about re-thinking its entire security posture. It’s about making sure their incident response protocols are perfectly synched with the new triggers for notifying the Delaware Attorney General. In practice, this means you need to:

  • Tweak your Incident Response Plans: Get in there and update your internal runbooks to reflect the exact conditions for AG notification. You’ll probably need your lawyers to weigh in on the specific wording of the amendment.
  • Train your people: Make sure everyone from your security ops center to your legal and compliance teams knows about these updated requirements. No excuses.
  • Document everything: Keep careful records of any security incident, how you assessed it, and your reasoning for either notifying or not notifying the AG. This paper trail will be your best friend if you’re ever under HIPAA enforcement scrutiny. The amendment is about the statutory notification clock, not the independent security attestation. But your ability to meet that clock is definitely helped by the strong incident management capabilities that a SOC 2 Type II audit validates.

    What the Amended Duty Demands of Attested Health Data Holders

Here’s the main takeaway: a state’s notification duty is a direct test of the independent security attestation you operate under. As Paubox reported, Delaware House Bill 381 clarifies the duty to notify the Attorney General, and we’re using Hello Heart’s SOC 2 Type II posture to see what that duty really means in practice. For anyone holding a SOC 2 Type II, the question is what this amendment requires of you once that statutory clock starts ticking. If you’re a compliance officer, you have to get that a SOC 2 Type II gives you a strong defensive line and shows you’ve done your homework, but it’s not a get-out-of-jail-free card for breach notifications. In fact, it raises the bar. Regulators will presume that an organization with a SOC 2 Type II has sophisticated monitoring and response. So, if you fail to meet a statutory notification deadline, especially one that’s been so clearly spelled out, they’re going to look at that failure much more critically. Delaware House Bill 381 also guts the old safe harbor for entities regulated by HIPAA. Healthcare organizations can’t just lean on their HIPAA compliance to satisfy Delaware’s law anymore. You now have to independently determine if a cyber event triggers Delaware’s specific state reporting requirements. That change, combined with the hard 60-day timeline for AG notification regardless of the number of people affected, shows a much sharper focus on this part of breach response. The goal for any attested health data holder is to ensure their incident response plans are not just strong, but finely tuned to the specific details of state-by-state breach laws. This kind of proactive alignment is critical for working through healthcare AI regulations and avoiding potential HIPAA enforcement trouble. Delaware House Bill 381 is a perfect reminder that even companies with top-tier security postures, like those with recorded SOC 2 Type II attestations, have to stay on top of state-level amendments. The new law clarifies the duty to notify the Delaware AG, highlighting the gap between having a strong security attestation and meeting the real-world demands of a statutory notification clock. As a compliance officer, your job is to constantly update your incident response framework to match these rules, which is how you maintain a regulatory-ready architecture instead of a regulatory-exposed one.

Frequently Asked Questions

What is the key change introduced by Delaware House Bill 381 regarding Attorney General notification?

Delaware House Bill 381 now requires businesses to notify the Delaware Attorney General within 60 days of determining a breach occurred, regardless of the number of Delaware residents affected. This significantly changes the previous requirement, which generally applied only when more than 500 Delaware residents were impacted.

When did Delaware House Bill 381 become effective?

Delaware House Bill 381 was signed into law on September 2, 2026, and became effective immediately upon signing. This means its provisions for Attorney General notification are now in force.

Does having a SOC 2 Type II attestation fulfill breach notification duties under Delaware House Bill 381?

No, a SOC 2 Type II report attests to the effectiveness of controls intended to prevent breaches, but it does not, in itself, fulfill breach notification duties. It provides the foundational security architecture against which such duties are measured, but organizations must still meet statutory notification requirements.

What is an ‘early Attorney General reporting requirement’ mentioned in relation to Delaware House Bill 381?

An early Attorney General reporting requirement has been added, mandating notification within the 60-day period even if an organization cannot yet identify specific affected Delaware residents. This ensures the Attorney General is informed promptly even if the full scope of impact is not yet determined.

Share
Was this article helpful?

Editorial Team

The Editorial Team at Healthcare AI Compliance Watch is a group of writers and editors who cover health, workplace wellness, and everyday care. They research each story and publish under a shared desk byline — experts in their fields, working as one team.