Protecting Personally Identifiable Information in Projects
Project+ · Basics of IT and Governance · By Super Admin
Master the essentials of protecting personally identifiable information and sensitive data in project environments to ensure compliance and prevent breaches.
Understanding Personally Identifiable Information
Personally identifiable information (PII) is defined by the National Institute of Standards and Technology (NIST) as "any information about an individual maintained by an agency, including (1) any information that can be used to distinguish or trace an individual's identity such as name, social security number, date and place of birth, mother's maiden name, or biometric records; and (2) any other information that is linked or linkable to an individual such as medical, educational, financial, and employment information." Data confidentiality involves protecting sensitive data and data types in order to protect individual identities and personal information relating to those individuals. Project managers must understand what data confidentiality entails and ensure that projects and systems are implemented in accordance with regulations. Information that is directly associated with an individual, such as social security numbers or biometric records, is used to "distinguish or trace an individual's identity" and is considered sensitive personally identifiable information (SPII), which is a subset of PII.
Sensitive Versus Linkable Data
Any of the SPII data elements on their own could identify an individual and cause them great harm or potential embarrassment if used inappropriately. Linkable data is also personally identifiable data but, on its own, is not sensitive data. However, when you combine linkable data with any sensitive data elements, it becomes sensitive personally identifiable information. For example, criminal history data, land ownership, and business ownership information are often easy to find through public records and are not sensitive on their own. However, if you are collecting a name, zip code, and credit card number together, for example, you are now handling sensitive data and need to be aware of the regulations and processes concerned with processing and storing this data. Context is important when you're using these data elements and determining whether they are sensitive. Whenever the data may cause substantial harm to an individual, may embarrass them or harm their reputation, or cause them to be treated unfairly, you are likely dealing with SPII.
Data Protection Strategies and Compliance
When working on a project, think about the context of the project and the data it will process or collect. Rather than collecting data on each individual, you could consider aggregating the data by using income ranges by zip code, identifying age ranges rather than specific ages, or obscuring the data so that names are not associated with income levels, for example. Anonymizing the data is a way to take what once was identifiable information and deidentify it so that it's generalized and less precise. This might also include deleting portions of the record or using average values for a group of data. Information technology projects often involve sensitive data, and project managers must implement protective measures. For example, if you're implementing a new human resources system, there will be weeks of testing needed to ensure the system is performing properly and verifying that company data has been uploaded correctly. However, you don't want to give all project team members the ability to see employee Social Security numbers or salaries, so you could manage sensitive data by scrambling it, obscuring all but the last two digits of the salary and Social Security number, and so on. Obviously, someone will have to verify Social Security numbers and other sensitive information, but these specific testing scenarios should be assigned to those in the organization who already have these responsibilities such as payroll clerks.
Regulatory Frameworks and Project Implications
As the project manager, it is your responsibility to know and understand the rules and regulations that apply to PII data. There could be significant fines and consequences for not adhering to proper handling of sensitive personally identifiable information. Many countries have developed their own standards and regulations for controlling, storing, and transmitting PII data. In the United States, NIST has published the "Guide to Protecting the Confidentiality of Personally Identifiable Information" as well as many other publications on data privacy issues. Canada has developed the Personal Information Protection and Electronic Documents Act (PIPEDA) and the Privacy Act. The European Union (EU) established the General Data Protection Regulation (GDPR). All organizations that engage in business in the EU must comply with GDPR, whether or not the business itself resides in the EU. Simply doing business in the EU requires compliance with GDPR standards. GDPR regulations are more restrictive than the NIST standards. For example, GDPR describes IP addresses, cookies, and radio frequency identification tags as sensitive personal data.
Discussion (0)
No discussion on this article yet — be the first to comment.
Please sign in to join the discussion.