BigID for Data Privacy Flashcards
Privacy cannot be easily addressed by today’s classification or cataloging tools. It
requires people and residency views. It requires
knowledge of context (where is it,
who created it, who is accessing it etc).
PII
Personally Identifiable Information
PI
Personal Information
PII can be used on its own or with other
information to
identify, contact, or locate a single person, or an individual in context
PI describes
a broad range of data that can be linked or linkable to an individual
PI is non-synonymous with PII and
significantly broader
It covers social media posts, photographs, lifestyle preferences, transaction histories and even IP addresses
PII refers to a relatively narrow data set such as
name, address, birth date, Social Security number and financial information such as
credit card numbers or bank accounts that can be used to identify a person
Private Data” is NOT a synonym with
“Personal Data”, and is not a term that should be used in a privacy context. It
only applies in classification discussions and data governance in the context of private data vs public data.
The European General Data Protection Regulation applies to
any entity that collects, stores and processes GDPR-related data in the EU -
whether or not the entity or the data subject are domiciled in the EU. Applies to organizations (private, government, non-profit) conducting business in the EU even if they don’t have an office there
The driving intent of GDPR is that privacy considerations become an integral
component of how business collect and process customer or employee data for EU
residents. Designed to
foster responsibility and transparency, the GDPR introduces not only obligations for organizations but most significantly rights for individuals whose data is being collected - including access rights, explicit and revocable consent requirements, data portability and the Right-to-Be-Forgotten (ie erasure of data).
Subject Rights Puts the Customer in the Driver’s Seat. Organizations need to have
explicit consent to collect data, and only
attributes that are covered by purpose of use limitations
GDPR mandates that data subjects have access to
all the data that a covered entity stores about them, and the ability to modify and delete the data
In effect, under GDPR, organizations don’t
own their customer data, but they are responsible for the data they store
Organizations that have customer data are either
controllers (with direct responsibility), or processors (that perform operations on behalf of controllers under defined contractual terms)
GDPR expands the definition of what constitutes personal data to
any data that can be tied to a specific individual
Traditional data discovery tools are designed to find personally identifiable data based on pattern matching. They don’t
associate the data they find back to individual, and can’t infer what could be
considered personal data based on identifiability and context.
GDPR outlines a set of principles that
controllers need to adhere to in order to
protect and maintain data privacy for all personal data - not just attest to and
provide evidence of controls for securing sensitive data (as defined under PCI
DSS or even NY DFS Cybersecurity, for example).
GDPR Key Principles: Accountability
can the controller provide an accurate and comprehensive accounting of whose data they have, where the data it is, and how it’s being processed, stored and accessed?