Monday, August 19, 2024

The National Data Breach: Deconstructing the Largest Database Ever Leaked

 



The recent incident with the background check titan, National Public Data (NPD), may be recorded as one of the most consequential data breaches in history. And this breach, of 2.7 billion records including almost 900 million unique Social Security numbers (SSNs), is larger than any we've seen to date in exposing sensitive information! #DataBreach #CyberSecurity #DataPrivacy

What makes this breach especially concerning, however, is not just the size of that data dump—it's what NPD does with said data. #InfoSec #DataSecurity


National Public Data Who?

National U.S. Public Records, Inc. has data for virtually every American in the markets it serves and is a significant competitor within the background check industry. NPD has provided its services to businesses as well as portions of local and state-level government agencies, such as courts, obtaining detailed information on an individual from their past behavior patterns. #BackgroundChecks #DataProtection

Not only is NPD being slammed for just taking any basic information they can—full names, addresses (current as well as decades worth of address history), Social Security numbers, and email/phone numbers—but this level of data depth lets NPD create dossiers of the citizen type that businesses rely upon to make hiring and security clearance decisions, etc., similar to what TIA was supposed to deliver. #CyberThreats

As for the Significance of This Breach…

While the leaking of nearly 900 million unique SSNs is devastating enough, the true threat comes in how much information was exposed and to what extent. Although sensitive, Social Security numbers are, in fact, one of the most widely disseminated types of information among many existent databases. The significant difference here is the granularity with which these records can be expanded. #IdentityTheft #DataSecurity

NPD records are how SSNs string together with data associated with you personally and produce a comprehensive record on thousands. It is a veritable gold mine for identity thieves, fraudsters, and even nation-state actors. #InfoSec #DigitalSecurity

This could have harsher and more lasting repercussions than an incident like the Ashley Madison hack, which led to personal embarrassment (even tragic suicides). For as devastating a personal breach as the Ashley Madison hack was for individuals, its impact pales in comparison to what might be at hand with an NPD-style breach. With all the things that can be done with that information—identity theft, fraudulent activities, and any kind of misuse—this breach holds immense potential for harm. #CyberAwareness

The Legal and Regulatory Aftermath

It also raises substantial legal and regulatory issues. Data processors like NPD are subject to regulations such as the GDPR that require a high degree of accountability. However, the companies utilizing NPD services still have to be sweating. #RegulatoryCompliance #GDPR

GDPR makes both data controllers and processors liable to legal action, which means that companies using NPD information for background checks may also be sued if they do not secure the personal information of their customers properly. Cases like this highlight the need for much more stringent enforcement of data protection rules. This breach is poised to become a testing event in data privacy litigation, with legal battles already kicked off even beyond the courtroom. #LegalConsequences #DataProtection

The Future: Rethinking Data Security

This loss is a red flag for everyone in the industry. It emphasizes obvious holes in data security measures and serves as a wake-up call that more regulation is necessary. In the wake of this event, we need a full reevaluation nationwide as it relates to how data is garnered, stored, and saved. This incident is almost certain to spawn wide-ranging new rules for cybersecurity practice and law. #DataSecurity #CyberThreats

In any case, breaches of this scale are always cause for worry, but the NPD breach holds great potential to do more harm than anything known to date. The sheer volume of individuals affected and the depth of data uncovered—this is not only a major breach, but it could be the biggest single (and sought-after) trove we have ever seen. It will take months, possibly years, to work out the full extent of the damage, but one thing is clear: The way we deal with personal data and protect it has got to change, now. #InfoSec #PersonalDataProtection

Unfortunately, as individuals, our options are limited in the wake of this monumental breach. While suing NPD might seem like a path to justice, it's also worth considering legal action against the businesses that trusted NPD with our sensitive information. After all, under regulations like GDPR, these companies share responsibility for ensuring our data's security. Note, although GDPR is an EU regulation, the same fundamental principles hold true in the US, holding providers responsible for third-party breaches. #GDPR #DataProtection

The Target Data Breach


Background:


Target was infiltrated by hackers who were able to steal the personal and credit information of more than 40 million customers. #DataBreach


Chain Reaction:


The culprit was identified as network credentials that had been pilfered from a third-party vendor, Fazio Mechanical Services, who handled the HVAC for Target. #ThirdPartyRisk #CyberSecurity


Liability:


Although the breach was perpetrated through a third-party vendor, Target was found to be liable for it because they should have protected their network—including any ingress by third parties. #LegalConsequences


Financial Penalties:


In the wake of the breach, Target was also hit with an $18.5 million multistate settlement related to its data breach, which at that time had been the largest ever for such an event. Costs directly associated with the incident exceeded beyond $200 million. #DataBreach #BusinessImpact


Legal Precedents:


The breach established a precedent that companies are liable for ensuring their third-party vendors have proper security safeguards. Ultimately, this case illustrates the necessity for robust third-party risk management. #ThirdPartyRisk #RegulatoryCompliance


Business Implications


The Target breach illustrates the point we made that third-party risk management is crucial! When a breach starts from any third party, the primary business can still be culpable, especially when it should have employed proper security and management oversight. #CyberSecurity #BusinessImpact


That history is particularly concerning, given the NPD breach. The companies using the services of NPD could end up being held responsible for allowing such a weakly protected environment in which NPD operated. Such a move could pave the way for lawsuits not just against NPD, but also potentially against those businesses that depended on its services. #LegalConsequences #ThirdPartyRisk


This precedent is particularly relevant in the context of the National Public Data (NPD) breach. Companies that used NPD’s services could potentially be held liable for not ensuring that NPD had robust security measures in place. This could open the door to litigation not only against NPD but also against the businesses that relied on their services. #RegulatoryCompliance #DataProtection


In Summary:


Businesses in the U.S. can indeed be held responsible for third-party breaches, especially when there is a failure to manage and oversee third-party security practices. #CyberSecurity #ThirdPartyRisk


In the meantime, the best steps we can take are proactive measures to protect ourselves. Lock your credit report immediately—something that’s advisable even in the absence of such breaches. Consider credit monitoring services to keep a close watch on any unusual activity. Change all your passwords, and most importantly, never use your Social Security number or driver’s license number as a password. These actions won’t undo the damage, but they can help mitigate the risks in this new, more vulnerable landscape. #PersonalDataProtection #CyberAwareness


Sunday, September 6, 2009

201CMR17 pushed again

Looks like 201 has been delayed yet again. Looks like the go live data is 3/10 vs 1/10. At somepont this will happen.

Sunday, August 2, 2009

iPhone and PI

So I was sitting with my lawyer last week who uses an iPhone and sync's with Exchange 2003. It then dawned on me that his office outlook contacts holds what is classified under 201CMR17 as PI. Then I started thinking about it, what about windows device (mobile) or blackberries. If the device is lost do I report under MGL 93H? How do we protect this information?

Wednesday, July 15, 2009

201 CMR 17.04 -Computer System Security Requirements Section 3,4 and 5

Ok.. lets take a look at the following sections of the regulation.

(3) Encryption of all transmitted records and files containing personal information, including those in wireless environments, that will travel across public networks. Ok.. lets take a closer look. If you are using wireless (why would you-big security risk) it should be encrypted. In most cases today must wireless is encrypted. If your using wireless (wifi) in the office make sure your using WPA for more info check out this link (http://tech.blorge.com/Structure:%20/2009/02/07/how-wpa-wireless-networks-are-hacked-and-how-to-protect-yourself/). If you are using an air card (verizon card, etc) use a vpn connection. Now that encrypts the communication channel, however the payload is still unencypted. What to do. You could use thrird party tools to ensure the payload is encypted like PGP or GPG. You also could use an SSL based system to transfer information from place to place.

(4) Periodic monitoring of networks and systems, for unauthorized use of or access to personal information, and recording the audit trails for users, events, dates, times and success or failure of login; Not a big deal. Use an auditing program, oh.. this is the first thing you would need to purchase. However their are lots of open source programs.. Set the program up to alert you when things happen.

(5) Periodic review of audit trails restricted to those with job-related need to view audit trails; See above, set up the tool to send an email when a person access or tries to access a restricted resource.

Friday, July 10, 2009

201 CMR 17.04 -Computer System Security Requirements

Welcome back.. Lets take a look at Section 2

(2) Secure access control measures that:

(i) restrict access to records and files containing personal information to those who need such information to perform their job duties; Ok. You have a few options and I will make a suggestion. It is easier to control all data then a subset. Let me explain. Lets make sure all our data is protected in the same manner that we protect personal information. Small company or large same process. Who is the data owner. So for example HR, HR will dictate who has access. In a windows network validate the HR shares with HR. This also applies for AF, etc. I would suggest using groups membersships. Also dont forget to turn on auditing.

and

(ii) assign a unique identification plus a password, which is not vendor supplied, to each person with computer access; Ya.. I dont think this needs an explaination. However dont forget things like routers and firewalls, card systems, etc. I cannot tell you how many times i have found default user names and password during a security audit.


Hmm.. thats it for now...


Sunday, July 5, 2009

201 CMR 17.04 -Computer System Security Requirements

Hope everyone enjoyed the 4th of July.

Lets take a look at the next section.

Every person that owns, licenses, stores or maintains personal information about a resident of the Commonwealth and electronically stores or transmits such information shall include in its written, comprehensive information security program the establishment and maintenance of a security system covering its computers, including any wireless system, that, at a minimum, shall have the following elements:

(1) Secure user authentication protocols including:

(i) control of user IDs and other identifiers; This is easy a unique user name for every user on the system. In most cases everyone should have this implemented.

(ii) a secure method of assigning and selecting passwords consisting of at least seven letters and numbers; Another easy administrative task on Windows/MAC/Unix networks. Create a Policy that requires a password of 8 letters and numbers. Force new users to change password to meet standard.

(iii) control of data security passwords to ensure that such passwords are kept at a location separate from that of the data to which such passwords permit access; This is interesting and open to interpretation. Use a password manager tool, such as KeePass. e

(iv) restricting access to active users and active user accounts only; Ok..simple if an employee no longer works for the company disable or delete account. I like disabling them for the first 90 days. Make sure you have controls in place to ensure this gets done.

and

(v) blocking access to user identification after multiple unsuccessful attempts to gain access or the limitation placed on access for the particular system; Another network admin task. Create a lock out policy (with some alerting).


See you next week

Sunday, June 28, 2009

201 CMR 17.00 - Standards for Protection of Personal Information

Every person that owns, licenses, stores or maintains personal information about a resident of the Commonwealth shall develop, implement, maintain and monitor a comprehensive, written information security program applicable to any records containing such personal information. Such comprehensive information security program shall be reasonably consistent with industry standards, and shall contain administrative, technical, and physical safeguards to ensure the security and confidentiality of such records. Moreover, the safeguards contained in such program must be consistent with the safeguards for protection of personal information and information of a similar character set forth in any state or federal regulations by which the person who owns, licenses, stores or maintains such information may be regulated.

Whether the comprehensive information security program is in compliance with these regulations for the protection of personal information, shall be evaluated taking into account (i) the size, scope and type of business of the person obligated to safeguard the personal information under such comprehensive information security program, (ii) the amount of resources available to such person, (iii) the amount of stored data, and (iv) the need for security and confidentiality of both consumer and employee information. Without limiting the generality of the foregoing, every comprehensive information security program shall include, but shall not be limited to:

(a) Designating one or more employees to design, implement and coordinate the maintenance of the comprehensive information security program;

(b) Identifying and assessing internal and external risks to the security, confidentiality, and/or integrity of any electronic, paper or other records containing personal information in each relevant area of the person’s operation, and evaluating and improving, where necessary, the effectiveness of the current safeguards for minimizing such risks, including but not limited to: (i) ongoing employee (including temporary and contract employee) training; (ii) monitoring employee compliance with policies and procedures; (iii) upgrading information systems, including network, system and software design, as well as information processing, storage, and transmission, as necessary; (iv) storage of records and data in locked facilities, storage areas or containers; and (v) improving, as necessary, means for detecting, preventing and responding to security, including but not limited to security systems, failures.

(c) Developing security policies for employees who telecommute that take into account whether and how such employees should be allowed to keep, access and transport data containing personal information.

(d) Imposing disciplinary measures for violations of the comprehensive information security program rules.

(e) Preventing terminated employees from accessing records containing personal information by immediately terminating their physical and electronic access to such records, including deactivating their passwords and user names.

(f) Taking reasonable steps to verify that third-party service providers with access to personal information have the capacity to protect such personal information, including (i) selecting and retaining service providers that are capable of maintaining safeguards for personal information; and (ii) contractually requiring service providers to maintain such safeguards. Prior to permitting third-party service providers access to personal information, the person permitting such access shall obtain from the third-party service provider a written certification that such service provider has a written, comprehensive information security program that is in compliance with the provisions of these regulations.

(g) Collecting the minimum amount of personal information necessary to accomplish the legitimate purpose for which it was collected; retaining such information for the minimum time necessary to accomplish such purpose; and permitting access to the smallest number of persons who are reasonably required to know such information in order to accomplish such purpose.

(h) Inventorying paper, electronic and other records, computing systems, and storage media, including laptops and portable devices used to store personal information, to identify those records containing personal information.

(i) Regularly monitoring and auditing employee access to personal information in order to ensure that the comprehensive information security program is operating in a manner reasonably calculated to prevent unauthorized access to or unauthorized use of personal information.

(j) Reviewing the scope of the security measures at least annually or whenever there is a material change in business practices that may reasonably implicate the security or integrity of records containing personal information.

(k) Documenting responsive actions taken in connection with any incident involving a breach of security or the potential therefor, and mandatory post-incident review of events and actions taken, if any, to make changes in business practices relating to protection of personal information.


Now what.. How do we protect our networks? What do we do to meet the new standard that goes into effect on January 1st 2010. I have been reading a lots of post over the last year indicating that the requirements are unreasonable. What is being asking is nothing more then reasonable care and best practices. Over the next few weeks I will be breaking down this regulation and how and what to do to protect yourself, your network and more importantly your data.

For starters, the standards for networks is not unrealistic. Over the next few weeks I will discuss each section in depth.