Which Developers and Teams Are More Likely to Write Vulnerable Software?
summary
Examines which developer, team and environmental characteristics correlate with introducing security vulnerabilities, using factors such as disrupted attention, team size, work hours and collaborative code editing as the variables. Focuses on empirical associations between human/organizational traits and insecure code, aimed at audiences familiar with software engineering and application security testing.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:42Why Software Vulnerability Research
- 11:57Does CoOp Affect Failure Rates
- 13:19Does Time of Day Affect Quality
- 15:24Developers Attention
- 17:31Number of Developers
- 19:39The bystander effect
- 20:49Developer experience
- 22:00Interactive churn
- 25:32Non software development
- 26:26Fatigue
- 28:21Culture
- 29:48Environment
- 31:57Research
- 34:51Human Resources
related talks
43mHuman factors that influence secure software development
43mDo Certain Types Of Developers Or Teams Write More Secure Code?
46mAre Developers the New Front Line of Security?
59mTeam of 30 million: Reducing Software Vulnerability at a Global Scale
45mExemplars, Laggards, & The Cautious: A Data-driven Look At High-velocity Software...
27mHow Security, Development & Testing can work together to stop ...
15mAn Ethnographic Understanding of Software (In)Security and a Co-Creation Model
45mShifting from Syntax to Secure Software Development Processes