Privacy Operational Life Cycle: Chapter 4 Assess Flashcards
Data governance
planning, oversight, and control over management
Data governance levels
Strategic: data steering committee, c-level
Managerial: data owners, functional leads
Operational: data stewards, SMEs
Data governance includes
Data architecture
Data modeling and design
Data storage and operations
Data security
Data integration and interoperability
Documents and content
Reference and master data
Data warehousing and business intelligence
Metadata
Data quality
Article 30 (GDPR)
Records must include:
- Name and contact details of the controller or processor, DPO, and/or data protection rep
- Name and contact of details of any Joint Controllers
- Purpose for the processing (for controllers)
- Description of categories of personal data and subjects (controllers) or processing (processors)
- Categories of recipients (for controllers)
- International transfers to third countries or multinational orgs
- Where applicable, Safeguards in place for exceptional transfers
- Where possible, retention periods for various categories of personal data (for controllers)
- General description of technical and org security measures.
Must be disclosed to a data authority upon request
Company of 250 employees or more if occasional and not sensitive
Data inventory should include
What is the context and purpose of the repo?
Who is the owner?
Which legal entity?
How much data (personal and sensitive)?
Format (physical or electronic, structured or unstructured)
How is it used?
Data retention
Type of elements and data subjects
Where is it stored?
Where is it accessed?
International transfers
Third party disclosure or sharing?
Transfer mechanisms
Privacy assessments
Measure compliance with laws
PIA
Analysis of privacy risk with processing PI
Suggest or provide remedial action for risk
Facilitate PbD
Effective if:
- done during ideation or scoping phase
- done when new or revised standards, policies, or laws
- done when org creates new privacy risks through changes
PIAs and US laws
Required by:
E-Government Act of 2002
Virginia
ISO 29134: guidelines for PIAs and reporting
- identify information flows with PII
- Analyze the use case
- determine relevant privacy safeguards
- Assess privacy risk steps
- prepare to treat privacy risk, controls 27002 or 29151
DPIA
GDPR required for high risk, identifies and reduces risk
Article 35
DPIA required when:
1. systematic and extensive evaluation of personal aspects when automated processing, profiling when decisions produce legal effects
2. processing on a large scale of special categories or criminal info
3. systematic monitoring of publicly accessible area on a large scale
DPIA minimum requirements
Description of processing, including purpose and legitimate interest
The necessity of the processing, proportionality, risks
Measures to address the risk
When to contact a Supervisory Authority
Illegitimate access to data leading to a threat of life, layoff or financial jeopardy
Inability to reduce the number of people accessing data
Assessing vendors
Reputation
Financial condition & insurance
Infosec controls
Point of transfer
Disposal of info
Employee training and awareness
Vendor incident response
Audit rights
Policies and procedures
DPO
Mergers