Chapter 4: Secure Development & Testing · Section 4.8
Common Development Pitfalls
Pitfall 1: "Security by Obscurity"
Problem: Hiding how things work instead of securing them Reality: Attackers will reverse engineer Solution: Assume attackers know everything except keys
Pitfall 2: "We'll Patch It Later"
Problem: Shipping with known vulnerabilities Reality: Patches may never happen Solution: Fix critical issues before release
Pitfall 3: "It's Not Connected"
Problem: Ignoring non-network attack vectors Reality: USB, physical access still exist Solution: Threat model all interfaces
Pitfall 4: "The Vendor Handles Security"
Problem: Blindly trusting third-party components Reality: You're responsible for everything Solution: Verify and monitor all components
Pitfall 5: "Testing Will Find Everything"
Problem: Over-reliance on testing Reality: Can't test all possibilities Solution: Defense in depth approach
See how your device measures up
Take the free FDA 524B readiness assessment and get a personalized gap report covering this topic and more.
Check Your Readiness