Security As A Bolt On
Security As A Bolt On is a software development anti-pattern where security measures are added to a system as an afterthought or late in the development lifecycle, rather than being integrated from the start. This approach often involves tacking on security features like authentication, encryption, or input validation after core functionality is already built, leading to vulnerabilities, higher costs, and inefficiencies. It contrasts with proactive security practices like DevSecOps or security-by-design.
Developers should learn about this concept to understand why it's problematic and avoid it in practice, as it can result in insecure software, increased technical debt, and costly fixes post-deployment. It's particularly relevant in scenarios where rapid development or legacy systems lead to security being neglected, such as in startups or when maintaining older codebases. Recognizing this anti-pattern helps teams shift towards more secure methodologies like integrating security early in the SDLC.