Evaluating Privacy Perceptions, Experience, and Behavior of Software Development Teams
summary
Mixed-method survey with 362 participants across 23 countries measures concrete gaps: 15 annotated definitions of privacy, information security staff report highest confidence while QA reports lowest, larger firms more often have a CPO yet presence of a CPO raises confidence without reliably reducing breaches, privacy impact assessments mostly occur in planning but most team members do not know how they are created, 57% of developers use privacy-by-design approaches, over 50% use Stack Overflow/GitHub daily.
AI-written summary · about
chapters (11)
- 0:00Privacy research focus
- 1:16Research questions
- 2:00Survey methodology
- 3:07Privacy perception definitions
- 4:10Confidence by role and size
- 4:53Privacy assessments and policy
- 5:37Privacy behavior gaps
- 7:29Privacy knowledge sources
- 7:50Regional regulation knowledge
- 8:32Takeaways for improvement
- 9:38Study conclusion
related talks
16mCache-22: Doing Privacy Engineering with Privacy Standards
12mPrivacy Engineers on the Front Line: Bridging Technical and Managerial Skills
21mHow Software is Developed for Privacy Professionals
51mFilling the gap between DPOs and developers
21mWhy Unleashing Your Software Security Potential is Necessary & How to Achieve It
15mTurning Privacy Risk Assessment Into 20 Questions for Developers
28mBuild Privacy into Your Products and Gain User Trust
40mExtreme Makeover: Privacy Edition