What "reasonable security" means and what happens when things go wrong
Every company that holds data will eventually face a security incident. The legal question isn't just how to prevent one — it's what you're required to do before one happens and what you must do if one occurs. Before: most states have some form of reasonable security requirement, and federal sector-specific laws (HIPAA, GLBA, FTC Act) impose security standards on covered companies. The NIST Cybersecurity Framework is the closest thing to a universal standard for what "reasonable" looks like. After: breach notification laws in all 50 states require you to notify affected individuals (and in some cases regulators) when a breach occurs. The timelines, triggers, and required content vary by state.
The more complex cybersecurity picture applies to companies touching federal systems or defense contracts. FedRAMP authorization is required to sell cloud services to federal agencies. The DoD's CMMC program — now effective as of November 2025 — requires defense contractors to obtain third-party cybersecurity certification at one of three levels. These requirements are significant compliance undertakings but also significant market qualifications — a FedRAMP or CMMC certification opens government markets that are otherwise closed.