Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarifying title #642

Open
h3xstream opened this issue Oct 4, 2021 · 1 comment
Open

Clarifying title #642

h3xstream opened this issue Oct 4, 2021 · 1 comment

Comments

@h3xstream
Copy link

h3xstream commented Oct 4, 2021

This project was renamed to OWASP Top 10 Risks in 2010. It is now often referred to "Top 10" alone.

I think the next release would be a great opportunity to rename it to something more significant.

Top 10 "Risks"

Risks is the likelihood of a security threat to happen. Therefore an SQL injection is not a risk. The possibility for private information being stolen or the possibility of some content being modified by an attacker are risks examples because they demonstrate a threat.

Does an XSS in a production system vs development system pose the same risk? It is the same vulnerability. It is the same software. The impact will likely be more important on the production environment.

Definitions:

It is also important to link up with other fields of cyber security notably threat analysis and risk management.

Better alternatives

  • Top 10 Weaknesses
  • Top 10 Vulnerabilities
  • Top 10 Classes of vulnerabilities
  • Top 10 Weaknesses categories

..What do you guys think?

@puneeth072003
Copy link

@h3xstream Its great:-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants