Friendly fire: how security software messes up
summary
Security software handles 10 million files a day and fields 24,000 disputes per year, running on about 55 million endpoints, so rare errors still hit many users. Most malware is packed (90% of malware is packed vs 5% of clean software), so bespoke or polymorphic packers trigger detections; unsigned or obscure installers and bundled affiliate installers trigger PUAs. Best practices are clear: sign your binaries, publish clear EULAs and visible UI, use standard packers, and offer proactive whitelisting.
AI-written summary · about
chapters (8)
- 0:00Start
- 4:23Minor inconvenience
- 6:17Productivity loss
- 7:39Complete incapacitation
- 15:53Obfuscation
- 24:14Behaviour
- 28:34Proactive whitelisting with IEEE
- 45:02KEY TAKEAWAYS
related talks
35mFriendly Fire: How Security Software Messes Up
33mYour Silent Software Saboteur: Open Source Malware
47mPrevalent Characteristics in Modern Malware
30mOpen Source Malware or a Vulnerability? The Philosophical Debate and How To Mitigate
36mUsing AI to Discover Silently Patched Vulnerabilities in Open...
46mThe Rise of Malware Within the Software Supply Chain
51mWanna Get Malware Out of Emails? CISA’s Latest Research
30mDeception at Scale: How Malware Abuses Trust