Security Best Practices vs Ad Hoc Security

Developers should learn and apply Security Best Practices to prevent costly data breaches, comply with regulations like GDPR or HIPAA, and build trust with users meets developers might use ad hoc security in fast-paced, agile projects where rapid prototyping or tight deadlines lead to deferred security considerations, or in small teams lacking dedicated security expertise. Here's our take.

Security Best Practices

Nice Pick

Developers should learn and apply Security Best Practices to prevent costly data breaches, comply with regulations like GDPR or HIPAA, and build trust with users

Pros

• Specific use cases include securing web applications against SQL injection and cross-site scripting (XSS), implementing secure authentication in mobile apps, and hardening cloud infrastructure in DevOps environments
• Related to: owasp-top-10, penetration-testing

Cons

• Specific tradeoffs depend on your use case

Ad Hoc Security

Developers might use Ad Hoc Security in fast-paced, agile projects where rapid prototyping or tight deadlines lead to deferred security considerations, or in small teams lacking dedicated security expertise

Pros

• It can serve as a temporary stopgap in emergency situations, such as responding to a newly discovered exploit, but it is generally discouraged for long-term use due to its inconsistency and higher risk of oversight
• Related to: security-by-design, devsecops

Cons

• Specific tradeoffs depend on your use case

The Verdict

These tools serve different purposes. Security Best Practices is a concept while Ad Hoc Security is a methodology. We picked Security Best Practices based on overall popularity, but your choice depends on what you're building.

The Bottom Line

Security Best Practices wins

Based on overall popularity. Security Best Practices is more widely used, but Ad Hoc Security excels in its own space.