Data Breach? We Can Help!
Call us today at 1-888-457-4736
Financial Institutions
Click here to find out how LoudSiren can become
part of your Incident Response Plan
What steps do you need to take if your business or organization suffers a data breach (sometimes called “security breach”) affecting the “personal information” of your customers, employees, or contractors? The answer varies depending on your specific circumstances and the law that applies, but hopefully the following information will be helpful.
1. What constitutes personal information, and what is a security or data breach?
- Among other things, personal information (sometimes called “Personally Identifiable Information”) includes all of the following: name and address, SSN, DOB, mother’s maiden name, driver’s license number, medical information, and other identifying information. Personal information may also include email addresses, phone numbers and other contact info, family history information, etc.
- A data breach usually occurs when personal information is compromised or disclosed without prior authorization.
2. As a custodian of personal information, your obligations in the event of a data breach are likely dictated by federal law, state law, and common law standards of negligence.
- Many state and federal laws require data custodians to give notice to the people whose personal information has been compromised and often require the custodian to take steps to limit the damage that could be caused by the breach. Links to state laws at the time of this writing are listed below. Keep in mind the potential victims of a data breach may live in a number of states.
- In addition to any statutory obligations imposed by federal and state law, there may be common law liability that could come into play if any of the compromised private information is used by identity thieves to harm the victims of the breach. This is why many organizations that experience a data breach offer victims a fraud alert management solution such as LoudSiren -- usually for at least one year from the date of the breach and often at no cost to the victims.
3. To see a typical notification letter to victims, click here
4. If a data breach could result in harm to a person or business, you should consider calling local law enforcement immediately. If you do, explain your situation and the potential risk for identity theft. Typically, the sooner law enforcement learns about a breach, the more effective they can be to prevent or limit theft. If your law enforcement agency is not familiar with investigating data breaches, contact the local office of the FBI or the U.S. Secret Service. For incidents involving mail theft, contact the U.S. Postal Inspection Service. Check the blue pages of your telephone directory or an online search engine for the number of the nearest field offices.
5. Other helpful resources
- Federal Trade Commission
- California Recommended Practices for Security Breaches
- PrivacyRights.org
•compiles data regarding recent data breaches and other helpful information
- LoudSiren
•helps victims of a data breach to stop credit-based identity theft before it happens
- LoudSiren Fraud Alert Management. Enables victims to stop credit-based identity theft before it happens.
- PrivacyRights.org. Good compilation of recent data breaches and other helpful information.
Data Breach? We Can Help!
Call us today at 1-888-457-4736
Financial Institutions
Click here to find out how LoudSiren can become
part of your Incident Response Plan
| STATE |
STATUE/LAW |
LINK |
| Arizona |
Ariz. Rev. Stat. 44-7501 |
|
| Arkansas |
Ark. Code 4-110-101 et seq. |
|
| California |
Cal. Civil Code 1798.82 |
|
| Colorado |
Col. Rev. Stat. 6-1-716 |
|
| Connecticut |
Conn. Gen. Stat. 36A-701(B) |
|
| Delaware |
De. Code tit. 6, 12B-101 et seq. |
|
| Florida |
Fla. Stat. 817.5681 |
|
| Georgia |
Ga. Code 10-1-910 et seq. |
|
| Hawaii |
Hawaii Rev. Stat. 487N-2 |
|
| Idaho |
Id. Code 28-51-104 to 28-51-107 |
|
| Illinois |
815 Ill. Comp. Stat. 530/1 et seq. |
|
| Indiana |
Ind. Code 24-4.9 |
|
| Kansas |
Ks. Stat. 50-7a01, 50-7a02 (2006 S.B. 196, Chapter 149) |
|
| Louisiana |
La. Rev. Stat. 51:3071 et seq. |
|
| Maine |
Me. Rev. Stat. tit. 10, 1347 et seq. |
|
| Michigan |
2006 S.B. 309, Public Act 566 |
|
| Minnesota |
Minn. Stat 325E.61 |
|
|
Minn. Stat . 609.891 |
|
| Montana |
Mont. Code 30-14-1701 et seq. |
|
| Nebraska |
Neb. Rev. Stat. 87-801 et seq. |
|
| Nevada |
Nev. Rev. Stat. 603A.010 et seq. |
|
| New Hampshire |
N.H. RS 359-c:19 et seq. |
|
| New Jersey |
N.J. Stat. 56:8-163 *brings up P.L.2005,c226(A4001 ACS 1R) |
|
| New York |
N.Y. Bus. Law 899-aa |
|
| North Carolina |
N.C. Gen. Laws 75-65 |
|
| North Dakota |
N.D. Cent. Code 51-30-01 et seq. |
|
| Ohio |
Ohio Rev. Code 1349.19 |
|
|
1347 et seq |
|
| Oklahoma |
Okla. Stat. 74-3113.1 |
|
| Pennsylvania |
73 Pa. Cons. Stat. 2303 |
|
| Rhode Island |
R.I. Gen. Laws 11-49.2-1 et seq. |
|
| Tennessee |
Tenn. Code 47-18-2107 |
|
| Texas |
Tex. Bus. & com. Code 48.001 et seq. |
|
| Utah |
Utah Code 13-44-101 et seq. *brings up 13-42-101 et seq. |
|
| Vermont |
Vt. Stat. Tit. 9, 2430 et seq. |
|
| Washington |
Wash. Rev. Code 19.255.010 |
|
| Wisconsin |
Ws. Stat. 895.507 |
|
*LoudSiren does not render accounting or legal services. The information contained in this website is offered only for general information and education purposes. The contents are not provided as and do not constitute accounting or legal advice. LoudSiren does not guarantee that the information is complete or up-to-date due to the dynamic nature of the subject matter. By using this site, you acknowledge and agree that there may be omissions and/or inaccuracies in the information and any data conveyed on this website.
|