Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Contentious Issues in Data Security

Contentious Issues in Data Security

Modern database systems have introduced more support for security, privacy, and compliance over the last few years. We expect this to increase as issues such as GDPR and other data compliance challenges arise. In this session, Karen will be discussing the newer features from a data modelers/database designers' point of view, including:

Data Masking
End-to-End encryption
Row Level Security
New Data Types
Data Categorization and Classification
We'll look at the new database and modeling tool features, why you should consider them, where they work, where they don't. We will also discuss how to negotiate on behalf of data protection in a world of Agile, MVP, Lean and DevOps.

Karen Lopez

November 13, 2024
Tweet

Other Decks in Technology

Transcript

  1. Karen Lopez Karen has 20+ years of data and information

    architecture experience on large, multi-project programs. She is a frequent speaker on data modeling, data- driven methodologies and pattern data models. She wants you to love your data.
  2. About this Presentation We will be using an interactive format

    - you will be participating in informal polls about data issues and best practices. This is not an introductory presentation - a good knowledge of data topics will be assumed.
  3. Contentious Issues Near-religious discussions and debates • People rarely change

    their minds based on this discussion • The most successful discussions are ones where both sides learn something new about the other viewpoint.
  4. Vote! We debate the answer and the results You put

    the sticky in the area for your vote I give the answers a range. I post a question
  5. Note Due to time, all questions today will be about

    Transactional data models. Not BI/DW/Dimensional models. …but you can still talk about analytical models…
  6. Remember… The words in the answer are just snarky, possible

    answers to help you understand the range of possible answers. Just because you vote on one end doesn’t mean you agree with the statement.
  7. Security at the data level Models capture security & privacy

    requirements Management reports and reviews Measurement Karen’s Governance Position (c) InfoAdvisors, all rights reserved, 2024
  8. • Karen’s Preference • Track all kinds of metadata •

    Advanced Compare features • Support DevOps and Iterative development • Support Conceptual, Logical and Physical design Data Models (c) InfoAdvisors, all rights reserved, 2024
  9. Locations of encryption On disk In flight At client(s) (c)

    InfoAdvisors, all rights reserved, 2024 21
  10. Encryption - Vote Is a Data Pro responsible for any

    of this? 1. Love my data, so yes! 2. 3. 4. Leave it to the DBAs/Dev/Others
  11. Data Masking Exampes XXXX XXXX XXXX 1234 [email protected] $99,9999 June,

    99, 9999 KXXXXX Lopez (c) InfoAdvisors, all rights reserved, 2024 25
  12. Data Masking - Vote Where should data masking be implemented?

    1. Every client application 2. 3. 4. In the database
  13. Why would a Data Pro love it? •Allows central, reusable

    design for standard masking •Offers more reliable masking and more usable masking •Applies across applications •Removes whining about “we can do that later” (c) InfoAdvisors, all rights reserved, 2024 29
  14. Row Level Security Who can see and manage which data?

    (c) InfoAdvisors, all rights reserved, 2024 30
  15. Security – Row Level Security Filtering result sets (predicate-based access)

    Predicates applied when reading data May be used to block write access Lots of options (c) InfoAdvisors, all rights reserved, 2024 33
  16. Row Level Security - Vote How should Data Pros be

    involved? 1. Requirements and Design 2. 3. 4. Not really at all
  17. Why would a Data Designer love it? Allows a designer

    to do this sort of data protection IN THE DATABASE, not just rely on code. Many, many pieces of code Applies across applications (c) InfoAdvisors, all rights reserved, 2024 35
  18. © 2007 InfoAdvisors, Inc. AI applied to Data New services/features

    Other vendors are embracing this Could be Skynet, could be the best thing ever!
  19. AI for Data - Vote What, today, would you use

    AI for in Data programs? 1. Everything I can 2. 3. 4. Almost nothing
  20. AI as a Steward - Vote Do you think we

    will see AI Security Stewards? 1. Soon, if not earlier 2. 3. 4. Maybe, but I’ll be long gone by then
  21. What roles/titles are responsible for determining security and privacy needs?

    Who designs them? Who monitors them? But really, who? (c) InfoAdvisors, all rights reserved, 2024
  22. Who is responsible for Security -Vote What best describes your

    belief? 1. The CEO/CIO/CDO/CTO…. 2. 3. 4. The developers
  23. Data Inventories and Categorizations Syntax Data Profiling Standard lists Custom

    Cross-column Manual Validation/Curation (c) InfoAdvisors, all rights reserved, 2024 41
  24. Who is responsible for Data Inventory -Vote What best describes

    your belief? 1. Data Governance/Management group 2. 3. 4. The developers
  25. Vote: IT Role in Compliance 1. Finally, a reason for

    the Execs to support us… 2. 3. 4. Hey! I don’t even have time write good definitions…
  26. Near-religious discussions and debates People rarely change their minds based

    on this discussion The best way to convince someone is with measureable facts There is no one “right” solution for all situations The most successful discussions are ones where both sides learn something new about the other viewpoint.
  27. Contentious Issues & Collaboration If we can’t collaborate well with

    other DAs, we don’t stand a chance of collaborating well with Project Managers, DBAs, Developers, Testers – or users. (c) InfoAdvisors, all rights reserved, 2024 48