WISP requirements in South Carolina
South Carolina uses a material-risk/illegal-use trigger and a 1,000-resident reporting threshold. A South Carolina incident file should preserve the access-plus-acquisition analysis, whether data was rendered unusable, the material-risk finding, resident count, Department of Consumer Affairs submission, national credit reporting agency notice, and any law-enforcement delay documentation.
Key facts
- South Carolina firms should keep a written security program tied to the FTC Safeguards Rule and IRS taxpayer-data guidance.
- Resident notice in the most expedient time possible and without unreasonable delay, subject to law-enforcement delay and scope/restoration needs; Department of Consumer Affairs and national credit reporting agency notices apply for 1,000+ South Carolina residents at one time.
- South Carolina routes large breach reporting to the Department of Consumer Affairs rather than the Attorney General; notify the Department when notice is sent to 1,000 or more South Carolina residents at one time, including breach date, awareness date, consumer notice date/method, resident count, notice copy, and corrective action.
Key takeaways
- South Carolina firms should keep a written security program tied to the FTC Safeguards Rule and IRS taxpayer-data guidance.
- Resident notice in the most expedient time possible and without unreasonable delay, subject to law-enforcement delay and scope/restoration needs; Department of Consumer Affairs and national credit reporting agency notices apply for 1,000+ South Carolina residents at one time.
- South Carolina routes large breach reporting to the Department of Consumer Affairs rather than the Attorney General; notify the Department when notice is sent to 1,000 or more South Carolina residents at one time, including breach date, awareness date, consumer notice date/method, resident count, notice copy, and corrective action.
- The WISP should preserve evidence, remediation steps, and annual review records.
Do South Carolina tax preparers need a WISP?
Yes, if they are covered by the FTC Safeguards Rule or IRS tax-data security expectations, they should maintain a written plan. South Carolina state breach-notice duties make incident planning especially important.
The WISP should start with federal obligations because the Safeguards Rule supplies the security-program structure.
South Carolina requires a business that sends data-security-breach notice to 1,000 or more South Carolina residents at one time to notify the Department of Consumer Affairs and the national credit reporting agencies.
What is specific to South Carolina?
Resident notice in the most expedient time possible and without unreasonable delay, subject to law-enforcement delay and scope/restoration needs; Department of Consumer Affairs and national credit reporting agency notices apply for 1,000+ South Carolina residents at one time. The plan should identify who evaluates state notice, who contacts counsel, and where the decision record is kept.
State breach-notification law does not replace the Safeguards Rule. It adds a state-specific response layer when an incident affects South Carolina residents.
South Carolina residents whose personal identifying information was not rendered unusable through encryption, redaction, or other methods and was, or is reasonably believed to have been, acquired by an unauthorized person under the material-risk/illegal-use trigger.
South Carolina routes large breach reporting to the Department of Consumer Affairs rather than the Attorney General; notify the Department when notice is sent to 1,000 or more South Carolina residents at one time, including breach date, awareness date, consumer notice date/method, resident count, notice copy, and corrective action.
What should the WISP say?
It should describe real safeguards, assign responsibility, map vendors and systems, and include an incident-response path that reaches state-law review quickly.
For a small firm, the strongest plan is plain and evidence-backed: MFA records, backup tests, access reviews, training, vendor lists, and remediation dates.
The plan should never promise a control that is not actually in place.
| Topic | South Carolina planning note | Evidence |
|---|---|---|
| Federal WISP | Use 16 CFR Part 314 as the program backbone | WISP and annual review |
| IRS tax data | Account for taxpayer records, PTIN practice, portals, and e-file workflows | System inventory and access list |
| Breach notice | Resident notice in the most expedient time possible and without unreasonable delay, subject to law-enforcement delay and scope/restoration needs; Department of Consumer Affairs and national credit reporting agency notices apply for 1,000+ South Carolina residents at one time. | Incident clock and counsel review record |
| Regulator path | South Carolina routes large breach reporting to the Department of Consumer Affairs rather than the Attorney General; notify the Department when notice is sent to 1,000 or more South Carolina residents at one time, including breach date, awareness date, consumer notice date/method, resident count, notice copy, and corrective action. | Notification decision log |
| State statute | S.C. Code Ann. § 39-1-90 | Source URL retained in page sources |
FAQ
Is this legal advice?
No. Policywright is a configurable template product, not a law firm and not legal advice. A qualified lawyer should review state-law reliance or breach-notification decisions.
Does a small firm still need a written plan?
Yes. The Safeguards Rule requires a written information security program for covered financial institutions, and IRS guidance tells paid tax preparers to maintain a written data security plan.
What if a control is not in place yet?
A serious WISP should not pretend. It should identify the gap, assign an owner, set a target date, and preserve a dated remediation record.
Does South Carolina have its own WISP law?
This page does not claim a standalone South Carolina WISP statute for every firm. It explains how federal WISP duties should be paired with South Carolina breach-notification planning.
Who reviews South Carolina breach notice?
The incident plan should route state-law decisions through qualified counsel and preserve any South Carolina Department of Consumer Affairs regulator-notice analysis.
Sources
- FTC Safeguards Rule, 16 CFR Part 314 (eCFR)
- FTC, Safeguards Rule: What Your Business Needs to Know
- FTC, Safeguards Rule notification requirement now in effect (16 CFR 314.4(j), eff. May 13, 2024)
- IRS Publication 5708, Creating a Written Information Security Plan
- IRS Publication 4557, Safeguarding Taxpayer Data
- IRS Form W-12, PTIN Application and Renewal
- IRS Publication 1345, Handbook for Authorized IRS e-file Providers
- South Carolina Code § 39-1-90
- South Carolina Consumer Affairs security breach business reporting
- South Carolina Consumer Affairs security breach notices
Build a South Carolina-aware WISP packet.
Policywright generates a source-cited WISP and incident response plan you can review with counsel.
Start the questionnaire