Friendly Fire: How Security Software Messes Up
summary
Security detections hinge on specifics: sign all binaries and authenticate traffic with HTTPS so reputation nudges decisions; avoid packers (about 5% of clean apps use packers vs ~90% of malware) or use only major non-polymorphic packers; show a visible GUI/EULA and avoid stealthy installers; proactively whitelist via vendor programs or IETF/episteme listings; publish a public trial build and monitor VirusTotal (BlueJeans once hit 27/67 vendors); fix bugs and unsafe installers (HP driver debug build logged keystrokes) and respond quickly to disputes.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:56Why security software fails
- 7:13Obfuscation and context
- 13:20Recommendations and detections
- 18:28Whitelisting and visibility
- 21:21Bundling and affiliate risks
- 26:23Bugs and vulnerabilities
- 30:25Malformed files and corruption
- 31:50Disputing false detections
- 33:59Summary and key takeaways
related talks
45mFriendly fire: how security software messes up
33mYour Silent Software Saboteur: Open Source Malware
18mIT Security – Don’t let Open Source Software become the next menace
44mMake It Fixable
26mBuilding and Verifying Security Trust in Today’s Complex Tech Stacks ...
41mThe Divine and Felonious Nature of Cyber Security
37mStranger Danger: Finding Security Vulnerabilities Before They Find You!
30mBroken Links: Emergence and Future of Software-Supply Chain Compromises