• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

OWASP guidelines

 
Ranch Hand
Posts: 60
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
 
Owasp member
Posts: 4
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
Posts: 60
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
Posts: 4
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
Posts: 60
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
It did help to an extent.Thanks Jaun for direction.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic