Hardening vs Security Through Obscurity
Developers should learn hardening to build secure software and infrastructure, especially in production environments handling sensitive data or critical operations meets developers should understand this concept primarily to avoid it, as it is considered a poor security practice that can lead to vulnerabilities when the obscurity is inevitably bypassed. Here's our take.
Hardening
Developers should learn hardening to build secure software and infrastructure, especially in production environments handling sensitive data or critical operations
Hardening
Nice PickDevelopers should learn hardening to build secure software and infrastructure, especially in production environments handling sensitive data or critical operations
Pros
- +It is essential for compliance with standards like ISO 27001 or GDPR, and for roles in DevOps, cloud security, or system administration to prevent exploits and ensure resilience against cyber attacks
- +Related to: cybersecurity, devsecops
Cons
- -Specific tradeoffs depend on your use case
Security Through Obscurity
Developers should understand this concept primarily to avoid it, as it is considered a poor security practice that can lead to vulnerabilities when the obscurity is inevitably bypassed
Pros
- +It is sometimes used in limited contexts, such as obscuring non-critical details to add a minor layer of defense-in-depth, but it should never be the sole or primary security mechanism
- +Related to: cybersecurity, defense-in-depth
Cons
- -Specific tradeoffs depend on your use case
The Verdict
Use Hardening if: You want it is essential for compliance with standards like iso 27001 or gdpr, and for roles in devops, cloud security, or system administration to prevent exploits and ensure resilience against cyber attacks and can live with specific tradeoffs depend on your use case.
Use Security Through Obscurity if: You prioritize it is sometimes used in limited contexts, such as obscuring non-critical details to add a minor layer of defense-in-depth, but it should never be the sole or primary security mechanism over what Hardening offers.
Developers should learn hardening to build secure software and infrastructure, especially in production environments handling sensitive data or critical operations
Disagree with our pick? nice@nicepick.dev