The Open Web Application Security Project (OWASP) is an open community
dedicated to enabling organizations to develop and maintain applications and
APIs that can be trusted. All OWASP tools, documents, videos, presentations,
and chapters are free and open-source to anyone interested in improving
application security.
OWASP is a new kind of organization. Their freedom from commercial pressures
allows them to provide unbiased, practical, and cost-effective information
about application security.
The OWASP Top 10 focuses on identifying the most serious web application
security risks for a broad array of organizations.
COMPARING 2017 v/s 2021
In the Top 10 for 2021, there are three new categories, four categories with
naming and scoping modifications, and some consolidation. OWASP changed the
names to focus on the core cause rather than the symptom.
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,
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.
A02:2021-Cryptographic Failures
shift up one position to #2, previously known as A3:2017-Sensitive Data
Exposure, which was a broad symptom rather than a root cause. 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.
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%, 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.
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, 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.
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%,
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.
A06:2021-Vulnerable and Outdated Components
was previously titled Using Components with Known Vulnerabilities and are #2
in the Top 10 community survey, but also had enough data to make the Top 10
via data analysis. This category moves up 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.
A07:2021-Identification and Authentication Failures
were previously Broken Authentication and are sliding down from the second
position, and now include CWEs that are more related to identification
failures. This category is still an integral part of the Top 10, but the
increased availability of standardized frameworks seems to be helping.
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. 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.
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. 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.
A10:2021-Server-Side Request Forgery is added to 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. 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.
A11:2021 - Next Steps -
By design, the OWASP Top 10 is innately limited to the ten most significant
risks. Every OWASP Top 10 has “on the cusp” risks considered at length for
inclusion, but in the end, they didn’t make it. No matter how we tried to
interpret or twist the data, the other risks were more prevalent and
impactful.
We hope this helps. If any suggestions or doubts you can add a comment and we
will reply as soon as possible.
No comments:
Post a Comment