C2: Leverage Security Frameworks and Libraries
Description
Secure coding libraries and software frameworks with embedded security help software developers guard against security-related design and implementation flaws. A developer writing an application from scratch might not have sufficient knowledge, time, or budget to properly implement or maintain security features. Leveraging security frameworks helps accomplish security goals more efficiently and accurately.
Implementation Best Practices
When incorporating third party libraries or frameworks into your software, it is important to consider the following best practices:
- Use libraries and frameworks from trusted sources that are actively maintained and widely used by many applications.
- Create and maintain an inventory catalog of all the third party libraries.
- Proactively keep libraries and components up to date. Use a tool like OWASP Dependency Check and Retire.JS to identify project dependencies and check if there are any known, publicly disclosed vulnerabilities for all third party code.
- Reduce the attack surface by encapsulating the library and expose only the required behaviour into your software.
Vulnerabilities Prevented
Secure frameworks and libraries can help to prevent a wide range of web application vulnerabilities. It is critical to keep these frameworks and libraries up to date as described in the [using components with known vulnerabilities Top Ten 2017 risks.
Tools
- OWASP Dependency Check - identifies project dependencies and checks for publicly disclosed vulnerabilities
- Retire.JS scanner for JavaScript libraries
Disclaimer
Credit via (OWASP Proactive Controls). For more information visit the (project page) or GitHub repository. OWASP ASVS is under the Creative Commons Attribution-Share Alike v3.0 license.
Loading comments 0%