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