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.

Sign up for GitHub

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

Jump to bottom

Revise numbering scheme to avoid clash with OWASP Top 10 #24

Closed
bkimminich opened this issue Sep 25, 2019 · 0 comments
Closed

Revise numbering scheme to avoid clash with OWASP Top 10 #24

bkimminich opened this issue Sep 25, 2019 · 0 comments
Assignees
@PauloASilva
Labels
bug Something isn't working

Comments

@bkimminich
Copy link
Member

Currently the numbering scheme is A1:2019, A2:2019 etc. which is identical to the way OWASP Top 10 is doing it. Their latest entries are A1:2017 to A10:2017. This could cause confusion such as people might assume that the OWASP Top 10 had a 2019 release when only seeing references to A1:2019 etc. somewhere.

For comparison, the Docker Top 10 (https://github.com/OWASP/Docker-Security) avoid this by using D1, D2 etc. as their numbering scheme. (They lack the year of document release though.)

Recommendation

As A is taken by OWASP Top 10 and no other single-letter comes to mind change numbering scheme into API1:2019 to API10:2019.
@bkimminich bkimminich changed the title Revise numbering scheme to avoid clash with OWASP Top 10 Revise numbering scheme to avoid clash w/ OWASP Top 10 Sep 25, 2019
@bkimminich bkimminich changed the title Revise numbering scheme to avoid clash w/ OWASP Top 10 Revise numbering scheme to avoid clash with OWASP Top 10 Sep 25, 2019
This was referenced Sep 25, 2019
Open
Closed
@PauloASilva PauloASilva self-assigned this Sep 25, 2019
@PauloASilva PauloASilva added the bug Something isn't working label Sep 25, 2019
PauloASilva pushed a commit that referenced this issue Jan 22, 2021
@Malajab
Merge pull request #24 from 0xMohammed/patch-21
67fcb5d 
Update 0xb1-next-devsecops.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@PauloASilva PauloASilva

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@PauloASilva @bkimminich