OWASP ASVS
OWASP ASVS
@asvs.owasp.org
+ Follow
490
followers
33
following
7
posts
Posts
Media
Videos
Starter Packs
OWASP ASVS
@asvs.owasp.org
· 13d
With the May release of
@OWASP
ASVS 5.0.0, we now have 3 finished translations: Turkish, Russian and French!
Thanks to everyone who prepared these and in particular thanks to Ata Seren who built a nice new translation validation script for us!
Look out others on the way!
2
1
OWASP ASVS
@asvs.owasp.org
· May 30
So @ElarLang just published version 5.0.0 of OWASP ASVS, live on stage at
@OWASP
Global AppSec EU Barcelona 2025!
9
12
OWASP ASVS
@asvs.owasp.org
· May 27
Don't miss OWASP ASVS co-leader @ElarLang who will be announcing the release of version 5.0, live on stage at OWASP Global AppSec EU Barcelona.
You can catch him on Friday 30th May in Room 116+117 at 11:30am.
See you there!
2
4
OWASP ASVS
@asvs.owasp.org
· Apr 9
ICYMI
ASVS 5.0 RC1 is ready for your review!
Give us your feedback now!
owasp.org/blog/2025/...
ASVS 5.0 RC1 is ready for your review! | OWASP Foundation
ASVS 5.0 RC1 is ready for your review! on the main website for The OWASP Foundation. OWASP is a nonprofit foundation that works to improve the security of software.
owasp.org
1
4
OWASP ASVS
@asvs.owasp.org
· Mar 31
You can find out details in our contribution guide:
github.com/OWASP/ASV...
Alternatively, get in contact with us via OWASP Slack:
owasp.slack.com/arch...
Have your say now! Submit early to avoid disappointment 😀
2/2
ASVS/CONTRIBUTING.md at master · OWASP/ASVS
Application Security Verification Standard. Contribute to OWASP/ASVS development by creating an account on GitHub.
github.com
3
5
OWASP ASVS
@asvs.owasp.org
· Mar 31
📯YOUR INPUT IS NEEDED!📯
@OWASP
ASVS version 5.0 release candidate is ready for review.
The final version is planned for the end of May. We want your feedback before then!
Can devs understand it? How about testers? Anything missing?
Dive into GitHub and let us know!
1/2
1
5
7
OWASP ASVS
@asvs.owasp.org
· Jan 31
Hi folks, we are considering replacing the current tick boxes which indicate the level of a requirement with a simple number.
In the short term we will change markdown files but leave the output formats the same.
Can anyone think of a good reason why we should not do this?
2
2
5