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

Change from Vulnerabilities to Risks #188

Open
Bobsimonoff opened this issue Sep 22, 2023 · 1 comment
Open

Change from Vulnerabilities to Risks #188

Bobsimonoff opened this issue Sep 22, 2023 · 1 comment
Assignees
Labels
discuss Indicates that this issue requires a deeper discussion v2 A topic for v2 discussion

Comments

@Bobsimonoff
Copy link
Contributor

With the realization that the top 10 focuses on the risks that vulnerabilities, I recommend changing our template and the content of the Top 10 to match.

The TL;DR

Fo to the OWASP Top 10 page and the first 2 sentences read:

The OWASP Top 10 is a standard awareness document for developers and web application security. It represents a broad consensus about the most critical security risks to web applications.

My detailed reasoning is in this document: risks-vs-vulnerabilities.md

@rossja
Copy link
Collaborator

rossja commented Sep 27, 2023

I agree that this makes sense, but think we need to reach consensus. In the meantime though, I've updated the style guide and the template for entries to swap out this wording in favor of risk, so folks can see what that looks like. (I did NOT update the entries for 1.1 to match, but feel we probably can do that for the next sprint if folks agree to this change).

@rossja rossja added discuss Indicates that this issue requires a deeper discussion v2 A topic for v2 discussion labels Mar 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss Indicates that this issue requires a deeper discussion v2 A topic for v2 discussion
Projects
None yet
Development

No branches or pull requests

2 participants