This week's book giveaways are in the Java EE and JavaScript forums.
We're giving away four copies each of The Java EE 7 Tutorial Volume 1 or Volume 2(winners choice) and jQuery UI in Action and have the authors on-line!
See this thread and this one for details.
The moose likes Security and the fly likes OWASP guidelines Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Engineering » Security
Bookmark "OWASP guidelines" Watch "OWASP guidelines" New topic
Author

OWASP guidelines

Bushra Binte
Ranch Hand

Joined: Nov 07, 2006
Posts: 60
Are there any guidelines OWASP or for that matter any other regulatory board specifies that lets a tester to understand what kind of testing should be performed either quick scan,full scan
Juan C Calderon
Owasp member
Greenhorn

Joined: Feb 08, 2011
Posts: 4
Sure there is, the project is called OWASP Application Security Verification Standard, defines 4 levels of testing and also explains what testing requirements should be covered for each level. Then it is only your task to identify what level your application should conform to, based on a the criticality of your application.

http://www.owasp.org/index.php/Category:OWASP_Application_Security_Verification_Standard_Project

Regards,
Juan Carlos
Bushra Binte
Ranch Hand

Joined: Nov 07, 2006
Posts: 60
Thanks Jaun.

I was thinking ,suppose i ask a list of questions or some information from business and based on their answers, to some extent recommend, hey your application should undergo full scan, quick scan ,standard scan,complaince scan..something of that sought

Do we have a guidelines that lead to that level of conclusion.(though the conclusion is not a perfect recommendation ..but yeah to some extent ..i can direct)
Juan C Calderon
Owasp member
Greenhorn

Joined: Feb 08, 2011
Posts: 4
What you are explaining is a Risk Analisys. I am not a aware of a set of questions. But I know 2 methods

1. Easy method. You identify application criticality based on impact (Information Sensitivity - Confidential, public, etc) and Likelyhood (exposure to audience - Intranet, internet, etc.), then create a small matrix like the one at this link http://www.owasp.org/index.php?title=OWASP_Risk_Rating_Methodology#Determining_Severity and map every resultant risk level to a level on ASVS. Thus Critical should be in compliance with Level 4, High => Level3, Med => Level2 and Low => Level 1

2. Harder (and more accurate). You do a Data Flow Diagram (First Step on Threat Modeling methodology) of the application and identify the application criticality then again map that criticality to a level on ASVS. Doing a DFD requires much more effort and knowledge of the application, though.

Hope it helps.

Regards,
Juan Carlos
Bushra Binte
Ranch Hand

Joined: Nov 07, 2006
Posts: 60
It did help to an extent.Thanks Jaun for direction.
 
wood burning stoves
 
subject: OWASP guidelines