[Owasp-topten] OWASP TOP TEN PROJECT - Issues Reported [ ref:_00DU0IvqV._5000BZo42j:ref ]
dave.wichers at owasp.org
Tue Feb 7 16:16:19 UTC 2017
Thanks for reporting. This has been fixed.
On Tue, Feb 7, 2017 at 10:59 AM, Claudia Aviles-Casanovas <
claudia.casanovas at owasp.org> wrote:
> Hello Shakti:
> Thank you for reporting the issues you encuntered in te OWASP Top Ten
> Project <https://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project>.
> I have cc'd the Project Leader, Dave Wichers so the they can get started on
> the corrections.
> OWASP TOP TEN PROJECT
> <https://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project>: Issue
> Hello I'm not sure how much it matters but I just wanted to let someone
> know that on the TOP 10 2013 - NOTES ON RISK Page, Under the OWASP Top Ten
> Project, the first few lines are duplicated in its entirety, which makes
> for a very large typo.
> The lines that are duplicated state: " Although the 2007 and earlier
> versions of the OWASP Top 10 focused on identifying the most common
> “vulnerabilities,” the OWASP Top 10 has always been organized around risks.
> This has caused some understandable confusion on the part of people
> searching for an airtight weakness taxonomy. The OWASP Top 10 for 2010
> clarified the risk-focus in the Top 10 by being very explicit about how
> threat agents, attack vectors, weaknesses, technical impacts, and business
> impacts combine to produce risks. This version of the OWASP Top 10 follows
> the same methodology. "
> Just thought for professionalism sake I'd inform someone. Again it's
> probably trivial in the grand scheme of things but still.
> Kind Regards,
> Disclaimer: OWASP does not endorse or recommend commercial products or
> services allowing our community to remain vendor neutral with the
> collective wisdom of the best minds in application security worldwide.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Owasp-topten