OWASP SAMM - Evaluating 'Not Applicable' in Security Practices: A Balanced Approach

The blog post "The 'Not Applicable' Question" on the OWASP SAMM (Software Assurance Maturity Model) website discusses the challenge of determining when a security practice or requirement is genuinely "not applicable" to a specific project or context. It emphasizes the importance of carefully evaluating each case to ensure that dismissing a requirement does not introduce security risks. The post provides guidance on how to document and justify "not applicable" decisions and highlights the need for a balanced approach to maintain security without overburdening the development process. 

https://owaspsamm.org/blog/2023/02/28/the-not-applicable-question/

Comments

Post a Comment

Popular posts from this blog

Endor Labs Announces Integrated SAST Offerings

 Endor Labs recently announced that their Static Application Security Testing (SAST) toolset will be integrated into their platform, enhancing software security. This offering aims to help developers identify and fix code vulnerabilities earlier in the development cycle. By combining SAST with dependency management, Endor Labs provides a streamlined approach to managing and securing both custom code and third-party dependencies in a unified platform, which can improve efficiency and reduce security risks. For more details, you can read the full article  .
Read more

OWASP Releases Enhanced Dependency-Check Tool with Advanced Tagging and Policy Management Features

 OWASP has released an updated version of its dependency-check tool, version 4.12.0, which identifies vulnerabilities in third-party software components, enforces policy compliance, and generates a CycloneDX-based Software Bill of Materials (SBOM). Key updates include enhanced tag features for improved control over security alerts and SBOM validation, a new tag management view, a global policy violation audit view, and authorization for security status badges. These changes offer more granular control over managing third-party dependencies, though experts note that managing software risk remains an ongoing challenge despite these improvements. https://securityboulevard.com/2024/10/owasps-dependency-check-tool-update-key-changes-and-limitations/ ps.  I think Security Boulevard (https://securityboulevard.com/) is a little bit confused here. https://securityboulevard.com/2024/10/owasps-dependency-check-tool-update-key-changes-and-limitations/ The original news links to Dependency...
Read more

The Hidden Cost of DevSecOps: Time and Financial Burden of Security on Developers

 A survey by JFrog, "The Hidden Cost of DevSecOps: A Developer’s Time Assessment," reveals that developers spend a significant amount of time on security-related tasks, costing companies around $28,000 per developer annually. Half of senior developers and team leaders report a notable increase in weekly hours dedicated to security tasks like manual application scans, context switching, and secrets detection. This time detracts from innovation and delivering new applications. JFrog’s CTO, Asaf Karas, emphasized the inefficiency caused by juggling multiple tools and environments, advocating for streamlined security processes to boost efficiency and reduce risks. Many developers spend 19% of their weekly hours on security tasks, often outside regular work hours, resulting in a reactive approach to security. https://informationsecuritybuzz.com/the-hidden-price-of-devsecops/
Read more