The OWASP Top 10 2021 🔝🔟
The THREAD 🧵 | #OWASPTop10
What's changed in the Top 10 for 2021
There are three new categories, four categories with naming and scoping changes, and some consolidation in the Top 10 for 2021.
• A01:2021-Broken Access Control owasp.org/Top10/A01_2021-Broken_Access_Control/ moves up from the fifth position to the category with the most serious web application security risk; the contributed data indicates that on average,... (1/2)
... 3.81% of applications tested had one or more Common Weakness Enumerations (CWEs) with more than 318k occurrences of CWEs in this risk category. The 34 CWEs mapped to Broken Access Control had more occurrences in applications than any other category. (2/2)
• A02:2021-Cryptographic Failures owasp.org/Top10/A02_2021-Cryptographic_Failures/ shifts up one position to #2, previously known as A3:2017-Sensitive Data Exposure, which was a broad symptom rather than a root cause.... (1/2)
... The renewed name focuses on failures related to cryptography as it has been implicitly before. This category often leads to sensitive data exposure or system compromise. (2/2)
• A03:2021-Injection owasp.org/Top10/A03_2021-Injection/ slides down to the third position. 94% of the applications were tested for some form of injection with a max incidence rate of 19%,... (1/2)
... an average incidence rate of 3.37%, and the 33 CWEs mapped into this category have the second most occurrences in applications with 274k occurrences. Cross-site Scripting is now part of this category in this edition. (2/2)
• A04:2021-Insecure Design owasp.org/Top10/A04_2021-Insecure_Design/ is a new category for 2021, with a focus on risks related to design flaws. If we genuinely want to "move left" as an industry, we need more threat modeling, secure design patterns, and principles,... (1/2)
... and reference architectures. An insecure design cannot be fixed by a perfect implementation as by definition, needed security controls were never created to defend against specific attacks. (2/2)
• A05:2021-Security Misconfiguration owasp.org/Top10/A05_2021-Security_Misconfiguration/ moves up from #6 in the previous edition; 90% of applications were tested for some form of misconfiguration, with an average incidence rate of 4.5%,... (1/2)
... and over 208k occurrences of CWEs mapped to this risk category. With more shifts into highly configurable software, it's not surprising to see this category move up. The former category for A4:2017-XML External Entities (XXE) is now part of this risk category. (2/2)
• A06:2021-Vulnerable and Outdated Components owasp.org/Top10/A06_2021-Vulnerable_and_Outdated_Components/ was previously titled Using Components with Known Vulnerabilities and is #2 in the Top 10 community survey, but also had enough data to make the Top 10 via data analysis. This category moves up... (1/2)
... from #9 in 2017 and is a known issue that we struggle to test and assess risk. It is the only category not to have any Common Vulnerability and Exposures (CVEs) mapped to the included CWEs, so a default exploit and impact weights of 5.0 are factored into their scores. (2/2)
• A07:2021-Identification and Authentication Failures owasp.org/Top10/A07_2021-Identification_and_Authentication_Failures/ has previously Broken Authentication and is sliding down from the second position, and now includes CWEs that are more related to identification failures.... (1/2)
... This category is still an integral part of the Top 10, but the increased availability of standardized frameworks seems to be helping. (2/2)
• A08:2021-Software and Data Integrity Failures owasp.org/Top10/A08_2021-Software_and_Data_Integrity_Failures/ is a new category for 2021, focusing on making assumptions related to software updates, critical data, and CI/CD pipelines without verifying integrity.... (1/2)
... One of the highest weighted impacts from Common Vulnerability and Exposures/Common Vulnerability Scoring System (CVE/CVSS) data mapped to the 10 CWEs in this category. A8:2017-Insecure Deserialization is now a part of this larger category. (2/2)
• A09:2021-Security Logging and Monitoring Failures owasp.org/Top10/A09_2021-Security_Logging_and_Monitoring_Failures/ was previously A10:2017-Insufficient Logging & Monitoring and is added from the Top 10 community survey (#3), moving up from #10 previously.... (1/2)
... This category is expanded to include more types of failures, is challenging to test for, and isn't well represented in the CVE/CVSS data. However, failures in this category can directly impact visibility, incident alerting, and forensics. (2/2)
• A10:2021-Server-Side Request Forgery owasp.org/Top10/A10_2021-Server-Side_Request_Forgery_%28SSRF%29/ is added from the Top 10 community survey (#1). The data shows a relatively low incidence rate with above-average testing coverage, along with above-average ratings for Exploit and Impact potential.... (1/2)
... This category represents the scenario where the security community members are telling us this is important, even though it's not illustrated in the data at this time. (2/2)
Follow @ScriptKKiddie for more Technology, Security & Open-Source Threads & Resources. #ScriptKKiddie