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

Please enumerate what's new in version 3.0 #48

Closed
javabeanz opened this issue Jun 12, 2015 · 4 comments
Closed

Please enumerate what's new in version 3.0 #48

javabeanz opened this issue Jun 12, 2015 · 4 comments
Assignees
Milestone

Comments

@javabeanz
Copy link

People using the former version 2.0, want to know what had changed so that they can update their policies.

@vanderaj
Copy link
Member

Already done - please see the document. I've actually mapped it back all
the way to 1.0. :) If it changed in 3.0, a new control is in green, a
deleted control is in red on the right hand column.

thanks
Andrew

On Fri, Jun 12, 2015 at 7:10 PM, javabeanz notifications@github.com wrote:

People using the former version 2.0, want to know what had changed so that
they can update their policies.


Reply to this email directly or view it on GitHub
#48.

@vanderaj vanderaj self-assigned this Jul 7, 2015
@vanderaj vanderaj closed this as completed Jul 7, 2015
@javabeanz
Copy link
Author

thanks for your reply. it would be nice if there was a "what's new " with some explanations for the new controls etc. And initially, there was a 2.1 version, but finally it was considered a major upgrade; why ?
Those things are relevant to sell an update to the latest ASVS in some cases.

@vanderaj
Copy link
Member

vanderaj commented Jul 8, 2015

Absolutely - that's going in the executive summary, so great suggestion.

When I got to AppSec EU, 2.1 was on the cards as a minor update to 2.0 to get rid of duplicate requirements, and drop or change requirements that made no sense (i.e. many of the things in the mobile checklist). I was expecting myself and Dan Cuthbert to show up as no one RSVP'd.

However, we had about 10-15 folks show up and there were four new contributed sections (also unexpected), and we carefully peer reviewed all of the ASVS findings in 2.0. This was more effort than even 2.0 had, so it deserved a 3.0 moniker. Hope this helps.

@vanderaj vanderaj reopened this Jul 8, 2015
@vanderaj vanderaj modified the milestone: 3.0 Jul 10, 2015
@danielcuthbert
Copy link
Collaborator

This is on the cards so closing this ticket down

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