Properly securing sensitive customer data is more important than ever. Consumers are increasingly insisting that their data be secured and managed properly. The regulatory environment is also becoming tougher, and business requirements are becoming increasingly complex. The burden is placed on the company and its development teams to meet these requirements while still delighting users. If that leaves you in a bind, we’re here to help with a quick data privacy primer! First, we’ll help you to understand the various kinds of sensitive customer data and the regulations that apply to it. Next, we’ll guide you in assessing your current handling of that data. Finally, we’ll provide direction on how to properly govern that data. Learn The first task is to understand what kind of sensitive customer data you are already handling and what regulations apply to it. Three factors determine which regulations apply to a given set of data: The data itself Your company’s industry vertical The location(s) where your business operates First, consider the data itself. Depending on the type of data that is being stored in your system, different regulations apply. Let’s begin with (PI). This is perhaps the broadest category of regulated data, referring to nearly anything that is or can be associated with a person. PI is regulated by the (GDPR), the (CRPA), , and others. Examples of this data include: Personal Information General Data Protection Regulation California Privacy Rights Act NY SHIELD IP addresses Geolocation information Internal ID numbers Ethnic or racial origin (PII) is a subcategory of PI and refers to any data which could be used to distinguish or otherwise determine a person’s identity. Generally speaking, the same regulations which apply to PI also apply to PII, although with differing levels of sensitivity. Examples of PII include: Personally Identifiable Information Names Phone numbers Driver’s license or other ID numbers Social Security Numbers (SSNs are more highly regulated than other PII) Biometric records Other categories of private consumer data tend to be industry-specific. For example, (PHI) refers to all “individually identifiable health information.” This is regulated in the US by , and is defined as any information which relates to any of the following: Protected Health Information HIPAA The individual’s past, present, or future physical or mental health or condition The provision of healthcare to the individual The past, present, or future payment for the provision of healthcare to the individual Similarly, (NPI) refers to the personally identifiable financial information that is provided by a consumer to a financial institution, and as such is specific to financial service organizations. In the US, NPI is regulated by the (GLBA). Nonpublic Personal Information Gramm-Leach Bliley Act Finally, some types of personal information are governed by location-specific regulations. (SPI) is defined by the . This refers to data that does not directly identify an individual but may cause harm if made public. Examples include ID numbers, geolocation, account login information, and genetic information. Sensitive Personal Information CPRA is defined by the and applies to any data related to a resident of New York. Additionally, nearly every privacy regulation has some kind of location scope (such as GDPR for the EU, HIPAA for the US, and so on). Private Information NY SHIELD Act This is not an exhaustive list of regulations or categories of sensitive customer data. With this in mind, however, we can see several trends. First, many of these categories overlap with one another. The same data can fall under the scope of multiple regulations and must be handled according to the requirements of all regulations that are relevant to your business. Second, the relevant regulations will heavily depend on your organization’s industry vertical and the locations in which it operates. Finally, even within a given regulation, different data can have differing levels of sensitivity. With an understanding of the various types of sensitive customer data in mind, we are now ready to begin an assessment process. This assessment will answer the question, “How is my sensitive customer data being handled now?” Assess Before determining how sensitive customer data be handled, it is helpful to take some time to assess how it handled. To begin, compile a list of customer data that is already being handled and stored. Next, you should carry out two assessments: a technical assessment and a policy assessment should is currently being A tells you where the data flows through the system. Begin with the moment that data enters the system, and trace it through the various pieces of your application. Make sure to consider the application, service, and data layers. Additionally, note any places where that data the system, and make note of where that data goes, such as another application or a business reporting tool. Do this for each piece of sensitive customer data that is currently in the system. As you continue to do this, make a note of any inconsistencies or mishandling to address later. technical assessment exits Example: Tracing the flow of user PII through a system With a , you review current policies and controls around data governance. Begin by compiling your organization’s internal documentation around sensitive data and reviewing the written policies and procedures. From there, consider whether these policies adequately cover the types and amount of sensitive data that your company currently handles. Another critical part of this assessment is determining whether these policies are being effectively executed, or if actual governance has diverged from the original intent. policy assessment With both assessments in hand, you should be able to confidently describe your organization’s current handling of sensitive customer data. Additionally, you will have identified areas for improvement or areas that require further research. Now, we are ready to define what be done about your sensitive customer data. should Govern To properly govern your sensitive customer data, we recommend a three-step process. First, determine the regulations which apply to you, and which subsets of data they apply to. Second, determine which policies need to apply to each subset of sensitive data. Lastly, based on the required policies, design or find a technical solution to implement and reinforce those policies. Proper technical governance of sensitive customer data protects sensitive data without making it unnecessarily difficult to use. Rather than simply storing it side-by-side with the rest of your data, consider isolating your sensitive data in a zero trust data privacy vault. This approach allows for your sensitive data to be properly governed with its own separate controls. Additionally, your data privacy vault can grow along with the scope of sensitive data your organization handles, allowing for scalability. If you’re looking to achieve compliance with data privacy regulations in days instead of weeks, one of your options for a dedicated data privacy vault is . Skyflow uses a zero trust approach to storing sensitive data of all types. The data is isolated, encrypted, and secure, yet still usable in your business workflows. Granular access policies are available for all data in the vault and are easily defined with the Skyflow Data Governance Engine. All actions are logged and auditable. Skyflow has solutions for FinTech, Healthcare, PII, and more, and it is compliant with privacy regulations worldwide. Skyflow Wrap-up We’ve gone through a three-step approach (Learn. Assess. Govern.) for handling sensitive customer data in your organization. First, we went through the various types of sensitive data and the regulations which apply to them. Next, we described how you can assess how your organization handles sensitive customer data. Finally, we sketched out a flow for properly governing your sensitive customer data. We also considered how an isolated data privacy vault such as Skyflow can help with that. The landscape of sensitive data governance is continually changing, as new regulations are created and existing ones are strengthened. As such, this process is not something that can just be done once; it must be continually updated as your organization grows and as regulations change.

Flow

Trace

Building a Kotlin Mobile App with the Salesforce SDK: Synchronizing Data

An Introduction to PCI Compliance

I write about technology michael.bogan@gmail.com

Nominated for 2022 - HackerNoon Contributor of the Year - Software Architecture

Nominated for 2022 - HackerNoon Contributor of the Year - Microservices

Nominated for 2022 - HackerNoon Contributor of the Year - Devops

Nominated for 2022 - HackerNoon Contributor of the Year - Api

Nominated for 2022 - Software Developer of the Year

Nominated for 2022 - HackerNoon Contributor of the Year - Software

Too Long; Didn't Read

Handling Sensitive Data: A Primer

Handling Sensitive Data: A Primer

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

10 Threats to an Open API Ecosystem

10 Reasons Wordpress Sites Get Hacked and How to Avoid Them

10 Features of a Secure Website

10 Cybersecurity Books Every Business Owner Should Read

10 Cybersecurity Tips Everyone Should Follow

10 Threats to an Open API Ecosystem

10 Reasons Wordpress Sites Get Hacked and How to Avoid Them

10 Features of a Secure Website

10 Cybersecurity Books Every Business Owner Should Read

10 Cybersecurity Tips Everyone Should Follow

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps