Comments (2)
Very much agree that the numbering is odd. It's a new major version, the whole point is to break with the old and introduce the new.
The reply I got at the time from @vanderaj was:
I think the missing gaps are v1.0 -> 2.0 mapping related - i.e. issues that are no longer inspected. I originally had "Deleted" or something there, but I think it may be important to declare why there are gaps (it makes translating v1.0 reports to ASVS 2.0 requirements much easier!).
My reply still stands I think:
Don't really agree with the reason, ASVS 2014 shouldn't be saddled with the burden of 2009 to make a one time thing easier for a few 2009 users IMHO.
Now I can no longer easily verify if a verification contains everything required for that level (instead of checking is 1.1 through 1.7 there, I have to memorise all the numbers per level). Making it easier for an auditor to sneakily leave off 'difficult' requirements or simply forget.
from asvs.
We are adding the missing requirements back, and then putting in a small amount of detail as to what happened to them including when the issues were retired. This will hopefully answer this issue and make it easier for tool users to keep faith with ASVS as we don't change the numbering scheme.
from asvs.
Related Issues (20)
- Request for Reevaluation of ASVS Item 10.3.3 Related to Subdomain Takeovers HOT 26
- Masking Sensitive Information in Category 8 HOT 23
- Discourage the use of Stateless Sessions (and therefor the usage of JWT for session) HOT 10
- Consideration for Memcache Injection Vulnerabilities HOT 16
- Consideration for Excluding Item 14.5.6 HOT 4
- 7.2 covering "Security Events" HOT 1
- 1.7.1 - do we need to require common logging format? HOT 6
- Section and requirement relevance questions HOT 2
- Consideration for HTTP/3 Security HOT 6
- Suggestion for Reconsideration of ASVS Requirement 8.3.1 Classification HOT 6
- Opportunistic Session Termination HOT 20
- recommendations chapter HOT 3
- Require case-sensitive password matching? HOT 11
- 14.4 section (HTTP Security Headers) rename / find better category-section for "content-type" requirements. HOT 2
- proposal: new requirement for disallowing search engines to crawl and index the content HOT 8
- 2.2.2 and 2.7.1 are duplicates HOT 2
- 2.7.5 is a security problem and weakness HOT 8
- 2.7.6 and 2.7.7 are in conflict HOT 6
- discussion/proposal: disallow user-autologin to an application using SSO sessions HOT 3
- Inclusion of Cypher Injection Prevention for Neo4j in ASVS 5.3.4 HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from asvs.