A comprehensive book walks through Data Management fundamentals using a fictional university case study involving a free taxi service for students. It covers the data lifecycle (planning, acquisition, storage, use, enrichment, disposal), Data Management principles and capabilities, roles like CDO, Data Owner, and Data Steward, and dedicates sections to Data Governance (ownership, stewardship, decision rights, policies, standards, accountability), Data Ethics (fairness, consent, responsible sharing), and Data Security and Privacy (classification, IAM, encryption, masking, auditing, SecOps). A companion Jupyter notebook using sample taxi-trip data demonstrates concepts like data profiling, quality rules, and dimensional modeling.
Table of contents
Table Of ContentsOur Case StudyData Management FundamentalsData GovernanceData EthicsData Security and PrivacyData ArchitectureData Modeling and DesignData Storage and OperationsDocument and Content ManagementReference and Master Data ManagementMetadata ManagementData Integration and InteroperabilityData QualityData EngineeringData Warehousing and Business IntelligenceBig DataAnalytics and Data ScienceData ProductsData Management OrganizationData Management MaturityConclusionsQuestions this post answers
What is the difference between data masking, pseudonymization, and anonymization?
Masking transforms or partially hides data to reduce exposure while keeping enough utility, such as showing only the last four digits of a bank account. Pseudonymization replaces identifiers with codes while retaining a separate way to reconnect them to the person, so it remains personal data requiring protection. Anonymization goes further, reducing identification risk so a person can no longer reasonably be identified, and only then is data no longer considered personal. Teams weighing privacy techniques for sensitive datasets can track deeper explainers like this on daily.dev.
What is the principle of least privilege in data access management?
It is the principle that each identity should receive only the permissions necessary to perform its specific job, nothing more. For example, an instructor can view contact information for students enrolled in their own courses but should not have access to records of students who are not enrolled with them. Role-Based Access Control (RBAC) is commonly used to implement this at scale by tying permissions to roles rather than individuals. Developers designing access control systems can follow least-privilege patterns and case studies on daily.dev.