Privacy, Consent and Security Within Modern Applications

Privacy, Consent and Security Within Modern Applications

Linux Foundation via YouTube Direct link

Intro

1 of 22

1 of 22

Intro

Class Central Classrooms beta

YouTube videos curated by Class Central.

Classroom Contents

Privacy, Consent and Security Within Modern Applications

Automatically move to the next video in the Classroom when playback concludes

  1. 1 Intro
  2. 2 Being a security target is costly
  3. 3 Equifax breach focused attention on open source risk
  4. 4 So what is "data" anyway?
  5. 5 What about "data privacy" then?
  6. 6 Example: New user with email identifier
  7. 7 Example: Assumption of valid email
  8. 8 "Consent" is a tricky concept
  9. 9 "Trust" is the most complex of the concepts
  10. 10 Top 12 questions when managing collected data
  11. 11 GOPR actions not just for data breaches
  12. 12 Reputational damage factors
  13. 13 Anonymizing shared data doesn't guarantee privacy
  14. 14 Web service APIs change risk dynamic
  15. 15 Managing consent can be complicated
  16. 16 loT development requires multiple disciplines
  17. 17 Identity security targets from platform requirements
  18. 18 Select development frameworks and environment
  19. 19 Continuous security assessments during development
  20. 20 Continuous security assessments during build
  21. 21 Confirm governance and security target progress
  22. 22 Key open source centric takeaways

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Someone learning on their laptop while sitting on the floor.