Thinking Outside the (Linux) Box: Security Considerations From Human Actors
summary
Embedded Linux security shifts from hardening boxes to defending people: 60–90% of attacks use humans as the initial access vector, so mitigate social engineering with agreed communication channels, named cross‑org contacts, and secure defaults like two‑factor auth. Reduce risky actions with least‑privilege roles, minimal interfaces, confirmation delays and testing; detect incidents via endpoint log collection and file‑change/intrusion alerts; plan containment, unique keys, and robust firmware updates to recover when errors or compromises occur.
AI-written summary · about
chapters (13)
- 0:00Human actors in Linux security
- 1:51Beyond technical hardening
- 3:15Key human actor groups
- 6:08Developers users adversaries defined
- 9:20Insiders most dangerous adversaries
- 10:23Social engineering targeting developers
- 12:33Human behavior problems
- 17:51Three-step model of actions
- 20:02Secure organizational environment
- 26:06Preventing human errors
- 31:48Designing for resilience
- 35:48Practical security steps
- 38:18Q&A
related talks
32mEmbedded Linux Security: Dr Jekyll and Mr Hyde- 32mEmbedded Linux Security: Dr Jekyll and Mr Hyde
05mEnterprise security: A new hope
51mThinking Differently About Security
33mInterview with
18mSecuring Organizations Through Bad Behavior
48mSecurity today: change your habits and make it safer and efficient
59mGetting Started with Embedded Linux Security