
Most small businesses are covered by at least one data-protection rule without knowing it. This page helps you work out which ones may apply and what to check first. It is general information, not legal advice.
Key takeaways
- Your industry and your data decide. Size alone does not exempt you.
- Common controls repeat. MFA, risk assessment, training, backups, vendor oversight and a response plan appear across most rules.
- Deadlines are short. HIPAA breach notice is within 60 days; the FTC Safeguards Rule has its own notice duty.
- Document everything. Regulators and insurers ask for evidence.
On this page: Map · HIPAA · FTC · PCI · CCPA · Professional · Common ground · Steps · FAQ
Which rules might apply to you?
HIPAA: health providers and their vendors
HIPAA applies to covered entities (such as healthcare providers and health plans) and to business associates that handle protected health information for them. HIPAA’s Breach Notification Rule requires notice to affected individuals without unreasonable delay and no later than 60 days after discovery. HHS proposed an update to the Security Rule in January 2025; as of this writing it is still a proposal. Start with a written risk analysis: HIPAA compliance checklist, and see cybersecurity for medical practices.
FTC Safeguards Rule: financial firms
The FTC’s Safeguards Rule covers non-bank financial institutions, which the FTC says include businesses such as mortgage brokers, auto dealers that finance or lease, tax preparers and some financial advisers. Required elements include a designated qualified individual, a written risk assessment, access controls, MFA, encryption, testing, staff training, oversight of service providers and a written incident response plan. The rule also requires notifying the FTC within 30 days after discovering an event involving unencrypted information of 500 or more consumers. See cybersecurity for accounting firms.
PCI DSS: anyone taking card payments
The PCI Security Standards Council says PCI DSS is intended for all entities involved in payment processing, including merchants. Whether a small merchant must validate compliance, and how, is set by the payment brands, so ask your acquirer (merchant bank). Most small merchants complete a self-assessment questionnaire (SAQ) matched to how they take cards. Using a PCI-listed point-to-point encryption (P2PE) solution can greatly reduce the requirements that apply, though it does not remove PCI DSS from your environment. The council publishes a free Guide to Safe Payments for small merchants.
CCPA/CPRA: California consumer data
The California Attorney General says the CCPA applies to for-profit businesses that operate in California and meet at least one test: annual gross revenue above $25 million; buying, selling or sharing the personal information of 100,000 or more California residents or households; or deriving 50% or more of annual revenue from selling residents’ personal information. Nonprofits and government agencies are generally not covered. Consumers can sue only for certain data breaches caused by unreasonable security, with statutory damages up to $750 per consumer per incident; other violations are enforced by the Attorney General or the California Privacy Protection Agency. Other states have their own privacy laws with different thresholds, so check where your customers live.
Professional rules
- Lawyers: ABA Formal Opinions 477R and 483 address reasonable safeguards and breach duties. See cybersecurity for law firms.
- Tax professionals: IRS Publication 4557 and Publication 5708 give safeguarding guidance. See accounting firms.
- Nonprofits: often lighter obligations but donor and card data still matter. See nonprofit security.
What do these rules have in common?
| Control | HIPAA | FTC Safeguards | PCI DSS |
|---|---|---|---|
| Risk assessment | Yes | Yes | Yes (scope and SAQ) |
| Access control and MFA | Yes | Yes | Yes |
| Staff training | Yes | Yes | Yes |
| Vendor oversight | Yes | Yes | Yes |
| Incident response plan | Yes | Yes | Yes |
Treat the table as a pointer, not a legal checklist; each rule’s text controls. The practical takeaway is that one good program covers much of all of them. See essential security controls and how to build a security program.
How do you start?
- List the data you handle (health, financial, card, personal) and where customers live.
- Match it to the rules above and note any contracts that add requirements.
- Ask a professional (lawyer, compliance consultant, your acquirer or your industry body) to confirm what applies.
- Do a risk assessment and fix the biggest gaps first.
- Write the policies (try our policy generator) and an incident response plan.
- Keep evidence: training logs, test results, vendor reviews.
- Review yearly and after changes.
Insurers also ask for proof of controls: cyber insurance requirements.
Frequently asked questions
Do small businesses have to comply with cybersecurity regulations?
Many do. Obligations depend on your industry, the data you handle and where your customers live, not just your size.
What is the FTC Safeguards Rule?
It requires covered financial businesses to maintain a written security program with elements such as a qualified individual, a risk assessment, MFA, encryption, training and an incident response plan.
Does HIPAA apply to my vendors?
Vendors that handle protected health information for a covered entity are business associates and have direct HIPAA obligations.
Is PCI DSS a law?
No. It is an industry standard enforced through your agreements with payment brands and your acquirer, though it can still carry fines and costs if you fall short.
Does the CCPA apply to small businesses?
Only if you meet one of its thresholds, such as over $25 million in revenue or handling data on 100,000 or more California residents or households.
What is the first step toward compliance?
Identify what data you hold and which rules cover it, then do a documented risk assessment.
Sources
- HHS: Breach Notification Rule
- FTC: Safeguards Rule compliance guide
- PCI Security Standards Council: Merchants
- California Attorney General: CCPA
- IRS Publication 4557
SMB Security HQ provides general information, not legal advice. Laws and thresholds change; confirm with a qualified professional. See our Affiliate Disclosure and How We Test.
