It usually starts quietly. An employee reports a strange email. A vendor sends an urgent notice about “suspicious activity.” Or a file server stops opening, and a ransom note appears on the screen. In the first few hours, most owners are focused on getting back to work. The legal clock, however, may already be running.
If your company holds personal information about customers, patients, clients, or employees, Wisconsin law may require you to tell the affected people within a set period. Missing that window can add legal, financial, and reputational damage on top of the breach itself.
At CMIT Solutions of Southeast Wisconsin, we help local businesses prepare for exactly this moment. This guide explains the basics of Wisconsin’s breach notification rules in plain language: who is covered, what counts as personal information, how long you have, what a notice must say, and what to do in the first 72 hours. It also covers the other deadlines that may apply to you, and how to build a plan before you need one.
A quick note: this article is general information, not legal advice. Every incident is different, so involve an attorney who handles data privacy matters as soon as a real breach is suspected.
Why Breach Notification Matters for Small and Midsize Businesses
Many owners assume breach laws are written for banks and national retailers. They are not. The law is built around the type of data you hold, not the size of your company. A five-person accounting office with client Social Security numbers has the same basic duty as a large enterprise.
Smaller companies are also attractive targets. Attackers know that limited budgets often mean fewer safeguards, and that smaller firms may not have a tested response plan. Recent coverage of ransomware risks shows that local businesses remain a steady target, and ransomware incidents frequently involve stolen data as well as locked files.
When a breach happens, three kinds of cost tend to appear:
- Direct response costs. Forensic investigation, legal fees, notification mailings, and credit monitoring offers add up quickly.
- Operational costs. Staff cannot work while systems are down, and the downtime costs often exceed the ransom or repair bill.
- Trust costs. Customers remember how a company handled bad news. Prompt, honest communication protects relationships that silence would destroy.
Wisconsin’s Breach Notification Law in Plain English
Wisconsin’s main breach notification rule is found in Wisconsin Statute 134.98. In simple terms, it says that when a covered entity knows that personal information has been acquired by someone who was not authorized to have it, the entity must notify the people affected.
Here is the short version of how it works:
- The law applies to entities that do business in Wisconsin and keep personal information in the ordinary course of business.
- It also reaches entities that license personal information in Wisconsin, maintain a depository account for a Wisconsin resident, or lend money to a Wisconsin resident.
- Notice must go to each person whose information was affected.
- The notice must be sent within a reasonable time, and no later than 45 days after you learn of the acquisition.
- Some situations allow you to skip notice, and some allow a delay.
The 45 day outer limit is the number most owners remember, but “reasonable time” matters just as much. If you finish your investigation in two weeks, waiting until day 44 is hard to justify.
Who Counts as a Covered Entity?
The statute uses the word “entity,” and it is broad. It includes corporations, partnerships, sole proprietors, nonprofits, and many other organizations. Government bodies in Wisconsin are also covered. If you collect and store information about people, assume you are in scope unless your attorney tells you otherwise.
What Counts as Personal Information?
Not every piece of data triggers the law. Under Wisconsin’s definition, personal information generally means a person’s first name or first initial and last name combined with at least one of the following:
- A Social Security number
- A driver’s license number or state identification card number
- A financial account number, including a credit or debit card number, along with any required security code, access code, or password that would allow access to the account
- A DNA profile
- Unique biometric data, such as a fingerprint, voice print, retina or iris image, or other unique physical representation
Notice what is missing from that list. A name and email address alone typically do not meet the definition. That said, other laws and contracts may still apply, and an exposed email list can still fuel phishing attacks. Do not treat the definition as the end of your analysis.
What Does “Unauthorized Acquisition” Mean?
The trigger is not simply that a hacker touched your network. The trigger is that personal information was acquired by someone without authorization. In practice, that can include:
- A cybercriminal copying files from your server
- A stolen laptop or phone with unencrypted customer records
- An employee emailing a spreadsheet of client data to the wrong external address
- A compromised vendor system that held your customers’ data
- A former employee taking records without permission
Determining whether data was actually acquired, rather than merely exposed, is one of the hardest parts of an investigation. It often requires log analysis and forensic tools that most small offices do not have on hand.
The 45 Day Deadline: How the Clock Works
The statute measures the deadline from the moment your organization learns of the unauthorized acquisition. That wording is important. The clock does not start when the attack began, and it does not wait for your investigation to be perfect.
Here is a simple way to think about the timeline:
- Day 0. Your team confirms, or has good reason to believe, that personal information was acquired.
- Days 1 to 3. You contain the threat, preserve evidence, call your attorney and insurer, and begin the forensic review.
- Days 4 to 20. You identify which records and which people were affected, and gather current mailing addresses.
- Days 20 to 35. You prepare and review the notice, set up any credit monitoring or support line, and coordinate with counsel.
- No later than day 45. Notices must be sent.
Most prudent companies aim to finish well ahead of the outer limit. Document every date and decision as you go, because you may need to show regulators, insurers, or opposing counsel how and when you acted.
When You May Not Need to Notify
Wisconsin’s law includes limited exceptions. An entity is generally not required to provide notice if:
- The acquisition does not create a material risk of identity theft or fraud for the people affected.
- The personal information was acquired in good faith by an employee or agent of the entity for a lawful purpose, and it is not used for an unlawful purpose or further disclosed without authorization.
These exceptions are narrow, and relying on them is a judgment call. A business that decides “no material risk” must be able to support that conclusion with evidence, such as proof that the data was strongly encrypted and the keys were not compromised. Because a wrong call can be costly, this decision should be made with legal counsel, and the reasoning should be written down.
When Law Enforcement Can Delay Notice
Sometimes police or other agencies ask a company to hold off on notifying people because an announcement could interfere with an investigation. Wisconsin law addresses this directly. If a law enforcement agency asks you not to notify, you may not provide notice or publicize the incident except as the agency authorizes.
If this happens, keep a record of who made the request, when, and what they said. Once the agency clears you, the notification process resumes.
What a Wisconsin Breach Notice Must Include
Wisconsin’s requirements for the content of the notice are fairly light compared with some other states. The notice must indicate that your entity knows of the unauthorized acquisition of personal information pertaining to the person receiving it. In addition, upon written request from someone who received a notice, you must identify the personal information that was acquired.
Even though the statute is short on required content, a good notice should be clear and useful. Include:
- A plain description of what happened and when you discovered it
- The types of information involved
- What you are doing in response
- Steps the person can take to protect themselves, such as monitoring accounts and placing fraud alerts
- Contact information for questions
- Details about any credit monitoring or identity protection you are offering
Avoid jargon, avoid blaming the victim, and avoid speculation. Tell people what you know, what you do not know yet, and when you will update them.
How to Deliver the Notice
The law calls for notice by mail or by a method you have previously used to communicate with the person. If you cannot determine a mailing address with reasonable diligence and have not communicated with the person before, you must use a method reasonably calculated to provide actual notice.
Practical delivery options include:
- First-class mail to the last known address
- Email, if that is the established way you communicate with the individual
- Phone follow-up for high-risk situations
- A dedicated web page or call center for questions
Notifying Credit Reporting Agencies
Beyond individual notices, Wisconsin law has an additional requirement for larger incidents. If you notify 1,000 or more people in connection with a single incident, you must also notify the nationwide consumer reporting agencies without unreasonable delay. The notice to those agencies should explain the timing, distribution, and content of the notices you sent.
If a Vendor Holds Your Data
Many breaches do not happen on your own network. They happen at a payroll provider, a cloud application, a billing service, or a software vendor. Wisconsin’s law recognizes this. A company that stores personal information it does not own or license must notify the owner of the data as soon as practicable when it learns of an unauthorized acquisition, unless a contract already addresses the situation.
Your obligations to the people affected do not disappear because the breach happened at a supplier. Review the contracts you have with every provider that touches sensitive data, and ask whether they commit to prompt notice. Understanding vendor breach risks before something goes wrong makes those conversations much easier.
Industry Rules That May Apply on Top of Wisconsin Law
Wisconsin law is only one layer. Depending on what you do, other rules may apply at the same time, and they sometimes set shorter deadlines or require additional notices.
- HIPAA. Healthcare providers and their business associates follow the federal Breach Notification Rule. Wisconsin’s statute treats entities that comply with the relevant federal regulations as meeting its requirements, but you still must follow the federal process. Healthcare teams benefit from healthcare threat monitoring that goes beyond a once-a-year compliance review.
- FTC Safeguards Rule. Certain non-bank financial businesses, such as tax preparers, mortgage brokers, and some lenders, must follow federal safeguards requirements, which include notifying the FTC after qualifying incidents involving a large number of consumers.
- Payment card rules. If you accept cards, your merchant agreement and card brand rules may require quick notice to your processor.
- Other states’ laws. If you serve customers who live in Illinois, Minnesota, or elsewhere, those states’ laws may apply to their residents, and some require notice to the attorney general.
- Contracts. Client agreements and vendor contracts frequently require notice within days, not weeks.
- Cyber insurance. Most policies demand prompt notice to the carrier, often before you hire outside help. Reviewing a cyber insurance renewal checklist now can prevent a coverage dispute later.
Because requirements overlap, a documented compliance program is worth the effort. Reliable compliance support helps you track which rules apply to your business, and the broader trend toward data privacy regulations means the list is growing, not shrinking.
Your First 72 Hours After a Suspected Breach
What you do early shapes everything that follows. Use this checklist as a starting point and adapt it to your environment.
Hour 0 to 4: Contain and Escalate
- Isolate affected devices from the network, but do not power them off unless instructed, since memory can hold valuable evidence.
- Disable compromised accounts and reset credentials, starting with administrators.
- Notify your IT provider or security team immediately.
- Start an incident log with times, names, and actions.
Hour 4 to 24: Bring in the Right People
- Call your attorney, ideally one experienced in data privacy.
- Notify your cyber insurance carrier according to your policy.
- Engage forensic specialists if the scope is unclear.
- Preserve logs, emails, and system images.
- Limit communication to a small response group so details do not spread informally.
Hour 24 to 72: Scope and Plan
- Determine what data was involved and whether it was actually acquired.
- Identify the affected individuals and the states where they live.
- Check contracts and regulations for deadlines other than Wisconsin’s.
- Decide on internal and external messaging, and prepare a holding statement.
- Confirm the threat is fully removed before restoring normal operations.
Quick, coordinated action is much easier when you have a team on standby. A responsive IT help desk and experienced security staff can handle containment while you focus on decisions and communication.
Common Mistakes That Make Breaches Worse
Experience shows the same errors appearing in incident after incident:
- Waiting for certainty. Owners delay action while hoping the problem is minor, and days disappear.
- Deleting evidence. Wiping and rebuilding systems too quickly destroys the logs needed to prove what happened.
- Paying without a plan. Ransom decisions involve legal, ethical, and practical issues, and paying does not guarantee data is not published.
- Unclear ownership. No one knows who is in charge, so everyone assumes someone else called the lawyer.
- Inconsistent messaging. Staff share different stories with customers, and confusion spreads.
- Ignoring vendors. The company does not check whether a supplier’s incident involves its data.
- Skipping documentation. Weeks later, no one can explain who decided what.
How to Reduce the Odds You Ever Need to Send a Notice
Notification rules exist for the worst day. The best strategy is to make that day less likely, and to limit the damage if it comes. A few investments make a major difference.
Know What Data You Hold
You cannot protect what you have not mapped. Take an inventory of where personal information lives: file servers, cloud storage, email, laptops, accounting software, paper files, and backups. Then delete what you no longer need. Data you do not keep cannot be stolen. Guidance on protecting sensitive data offers a practical starting point for that inventory.
Encrypt Everything Reasonable
Encryption can turn a reportable event into a non-event. If a stolen laptop has full-disk encryption and the keys were not exposed, the risk of identity theft may be low. Encrypt laptops, phones, removable media, and backups. When buying devices, smart IT procurement choices make encryption and security features a default rather than an afterthought.
Lock Down Identities
Most modern attacks start with stolen or guessed credentials. Strong controls include:
- Multi-factor authentication on email, remote access, and financial systems
- Unique, long passwords managed by a password manager
- Conditional access rules that block risky sign-ins
- Prompt removal of access when employees leave
Attackers have also learned to wear users down with repeated prompts, so training on MFA fatigue attacks is just as important as turning MFA on. A broader look at identity security explains why account protection now sits at the center of ransomware defense.
Build Layered Defenses
No single tool stops every attack. A strong program combines several layers:
- Managed cybersecurity services with endpoint detection, email filtering, and around-the-clock alerting
- Careful network monitoring to spot unusual traffic and unauthorized devices
- Segmentation so one compromised device cannot reach everything
- Regular patching of operating systems and applications
Many companies are adopting zero trust basics to limit how far an intruder can move once inside, which also helps shrink the number of records exposed in any single incident.
Protect Email and Collaboration Tools
Email is the most common doorway into a business. Proper Microsoft 365 security settings block many phishing attempts, restrict risky sharing, and log activity you will need during an investigation. Well-configured productivity application support ensures staff use approved tools instead of personal accounts, and secure unified communications keeps call recordings, voicemails, and chat messages inside a managed environment.
Secure Your Cloud Environment
Data stored with cloud providers is still your responsibility. Sensible cloud security services include access controls, activity logging, and configuration reviews, so a misconfigured storage setting does not quietly expose customer files.
Back Up and Practice Recovery
Backups do not prevent breaches, but they decide how long your outage lasts. Dependable secure data backup should be encrypted, stored offsite, and protected from tampering. Equally important is disaster recovery planning, which defines how fast you restore operations and who does what during the crisis.
Train Your People
People are both the biggest risk and the best defense. Ongoing employee security awareness training, including simulated phishing, teaches staff to report suspicious messages quickly. Fast reporting often decides whether an incident stays small.
Set Rules for AI Tools
Employees now paste customer details into chatbots and AI assistants without thinking twice. That can be an unauthorized disclosure waiting to happen. Clear AI governance policies spell out which tools are approved and what data may never be entered.
Build an Incident Response Plan Before You Need One
A written plan turns panic into process. It does not need to be a hundred pages, but it should be specific and tested. A practical plan includes:
- A response team. Name an incident lead, a decision maker, a legal contact, an IT contact, and a communications contact, along with backups for each.
- Contact lists. Keep phone numbers for your attorney, insurer, IT provider, forensic firm, bank, and key vendors somewhere accessible offline.
- Data map and decision tree. Know which systems hold regulated data and who decides when a threshold is met.
- Notification templates. Pre-approved drafts for individuals, customers, employees, and regulators save precious days.
- Evidence handling steps. Spell out how to preserve logs and devices.
- Communication rules. Decide who may speak publicly and who must refer questions.
- Practice sessions. Run a tabletop exercise once or twice a year so everyone knows their role.
Owners who want help turning this into a working document can lean on strategic IT guidance to align the plan with budgets, insurance requirements, and growth goals. Many businesses also find it easier to budget when they compare IT service packages that bundle security, support, and monitoring under one predictable fee.
Why Having a Local Team Matters
When an incident hits, speed and familiarity matter. A provider who already understands your systems, your vendors, and your compliance obligations can start containment in minutes rather than hours. Teams offering managed IT services already monitor your environment daily, so they know what normal looks like and can spot what is not. Beyond emergencies, proactive IT monitoring catches missing patches, failed backups, and risky settings before attackers use them.
If you are still weighing your options, start a conversation with a local IT team that is willing to review your current protections honestly and explain where the gaps are, in language you can use.
Conclusion
Wisconsin’s breach notification rules are short, but the stakes are high. When personal information is acquired without authorization, you generally have no more than 45 days from discovery to notify the people affected, and sooner if a contract, insurer, or other law demands it. Know what counts as personal information, understand the narrow exceptions, involve legal counsel early, and document every step. Then do the work that matters most: reduce what you store, protect what remains, train your people, and rehearse your response.
You do not have to figure this out alone. CMIT Solutions of Southeast Wisconsin helps local businesses assess their risks, strengthen their defenses, and prepare a response plan that works under pressure. Schedule a consultation to review your current security, identify gaps, and build a clear path forward before a bad day arrives.


