WISP requirements in South Dakota
South Dakota's workflow has two unusual documentation points: the 250-resident Attorney General threshold and the written no-likely-harm determination that must be preserved for at least three years after Attorney General notice. A Policywright South Dakota incident file should preserve the discovery or vendor-notification date, personal-versus-protected-information analysis, encryption-key analysis, affected-resident count, AG mail or electronic-mail report, consumer-reporting-agency notice, substitute-notice analysis at $250,000 or 500,000 people, and any law-enforcement delay.
Key facts
- South Dakota firms should keep a written security program tied to the FTC Safeguards Rule and IRS taxpayer-data guidance.
- Resident notice no later than 60 days from discovery or notification of the breach, unless law-enforcement needs require more time; Attorney General notice applies for breaches exceeding 250 South Dakota residents; consumer-reporting-agency notice is due without unreasonable delay when resident notice is required.
- Notify the South Dakota Attorney General by mail or electronic mail for any breach of system security that exceeds 250 South Dakota residents; if relying on the no-likely-harm exception, provide notice to the Attorney General and keep the written determination for at least three years.
Key takeaways
- South Dakota firms should keep a written security program tied to the FTC Safeguards Rule and IRS taxpayer-data guidance.
- Resident notice no later than 60 days from discovery or notification of the breach, unless law-enforcement needs require more time; Attorney General notice applies for breaches exceeding 250 South Dakota residents; consumer-reporting-agency notice is due without unreasonable delay when resident notice is required.
- Notify the South Dakota Attorney General by mail or electronic mail for any breach of system security that exceeds 250 South Dakota residents; if relying on the no-likely-harm exception, provide notice to the Attorney General and keep the written determination for at least three years.
- The WISP should preserve evidence, remediation steps, and annual review records.
Do South Dakota 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 Dakota 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 Dakota requires Attorney General notice by mail or electronic mail when a breach exceeds 250 South Dakota residents, and requires notice to nationwide consumer reporting agencies when circumstances require resident notice.
What is specific to South Dakota?
Resident notice no later than 60 days from discovery or notification of the breach, unless law-enforcement needs require more time; Attorney General notice applies for breaches exceeding 250 South Dakota residents; consumer-reporting-agency notice is due without unreasonable delay when resident notice is required. 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 Dakota residents.
South Dakota residents whose personal or protected information was, or is reasonably believed to have been, acquired by an unauthorized person after a breach of system security.
Notify the South Dakota Attorney General by mail or electronic mail for any breach of system security that exceeds 250 South Dakota residents; if relying on the no-likely-harm exception, provide notice to the Attorney General and keep the written determination for at least three years.
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 Dakota 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 no later than 60 days from discovery or notification of the breach, unless law-enforcement needs require more time; Attorney General notice applies for breaches exceeding 250 South Dakota residents; consumer-reporting-agency notice is due without unreasonable delay when resident notice is required. | Incident clock and counsel review record |
| Regulator path | Notify the South Dakota Attorney General by mail or electronic mail for any breach of system security that exceeds 250 South Dakota residents; if relying on the no-likely-harm exception, provide notice to the Attorney General and keep the written determination for at least three years. | Notification decision log |
| State statute | S.D. Codified Laws §§ 22-40-19 through 22-40-26, including §§ 22-40-20 and 22-40-24 | 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 Dakota have its own WISP law?
This page does not claim a standalone South Dakota WISP statute for every firm. It explains how federal WISP duties should be paired with South Dakota breach-notification planning.
Who reviews South Dakota breach notice?
The incident plan should route state-law decisions through qualified counsel and preserve any South Dakota Attorney General / Consumer Protection Division 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 Dakota Codified Laws § 22-40-20
- South Dakota Codified Laws § 22-40-19
- South Dakota Codified Laws § 22-40-24
- South Dakota Attorney General data breach bill signing release
- South Dakota Consumer Protection security breach guidance
Build a South Dakota-aware WISP packet.
Policywright generates a source-cited WISP and incident response plan you can review with counsel.
Start the questionnaire