In the United States, statutory requirements are legal obligations established by acts of legislation (laws) passed by Congress or state legislatures.
| Type | Where it comes from | Example |
|---|---|---|
| Statutory | A law passed by a legislature | The Health Insurance Portability and Accountability Act (HIPAA), passed by Congress |
| Regulatory | Rules an agency issues to carry out a law | The HIPAA Privacy Rule issued by the Department of Health and Human Services (HHS) |
| Contractual | Obligations you agree to in a contract | A DFARS clause in a Department of Defense (DoD) contract, or PCI DSS required by a merchant agreement |
In short: statutes say what must happen, regulations say how, and contracts add obligations you accept by signing. See statutory vs regulatory vs contractual compliance for the full guide.
Statutory requirements represent the foundational legal mandates organizations must follow. For example, the Health Insurance Portability and Accountability Act (HIPAA) is a statute that sets rules for protecting patient health information.
Regulatory requirements are detailed rules and standards developed by Federal and/or state government agencies authorized by statute to implement and enforce the law. Regulations provide the technical, operational, or administrative specifics necessary to comply with statutes. For example, the Department of Health and Human Services’ HIPAA Privacy Rule is a regulatory implementation of the HIPAA statute.
Key distinctions between statutory and regulatory compliance include:
In cybersecurity compliance, understanding the difference is important because organizations often comply with regulations that operationalize statutes and failure to meet regulatory requirements can lead to legal consequences under the underlying statute.