A Penetration Test Is A Method Of Evaluating The Security Of A Computer System Or Network By Simulating An Attack. A Web Application Penetration Test Focuses Only On Evaluating The Security Of A Web Application. The Process Involves An Active Analysis Of The Application For Any Weaknesses, Technical Flaws, Or Vulnerabilities. Any Security Issues That Are Found Will Be Presented To The System Owner Together With An Assessment Of Their Impact And Often With A Proposal For Mitigation Or A Technical Solution. What Is A Vulnerability? A Vulnerability Is A Flaw Or Weakness In A System’s Design, Implementation, Or Operation And Management That Could Be Exploited To Violate The System’s Security Policy. A Threat Is A Potential Attack That, By Exploiting A Vulnerability, May Harm The Assets Owned By An Application (Resources Of Value, Such As The Data In A Database Or In The File System). A Test Is An Action That Tends To Show A Vulnerability In The Application. What Are Application Security Risks? Attackers Can Potentially Use Many Different Paths Through Your Application To Do Harm To Your Business Or Organization. Each Of These Paths Represents A Risk That May, Or May Not, Be Serious Enough To Warrant Attention.What’s My Risk We Provide Generic Information About Likelihood And Technical Impact Using The Following Simple Rating Scheme, Which Is As Follows :

What Is The OWASP Testing Methodology?

Penetration Testing Will Never Be An Exact Science Where A Complete List Of All Possible Issues That Should Be Tested Can Be Defined. Indeed, Penetration Testing Is Only An Appropriate Technique For Testing The Security Of Web Applications Under Certain Circumstances. The Goal Is To Collect All The Possible Testing Techniques, Explain Them And Keep The Guide Updated. The OWASP Web Application Penetration Testing Method Is Based On The Black Box Approach. The Tester Knows Nothing Or Very Little Information

About The Application To Be Tested. The Testing Model Consists Of:

    • Tester: Who Performs The Testing Activities
    • Tools And Methodology: The Core Of This Testing Guide Project
    • Application: The Black Box To Test The Test Is Divided Into 2 Phases:
    • Passive Mode: In The Passive Mode
  • The Tester Tries To Understand The Application’s Logic, And Plays With The Application. Tools Can Be Used For Information Gathering, For Example, An HTTP Proxy To Observe All The HTTP Requests And Responses. At The End Of This Phase, The Tester Should Understand All The Access Points (Gates) Of The .Application (E.G., HTTP Headers, Parameters, And Cookies).
    • Active Mode: In This Phase, The Tester Begins To Test Using The Methodology Described In The Follow Paragraphs. We Have Split The Set Of Active Tests In 9 Sub-Categories For A Total Of 66 Controls: • Configuration Management Testing
    • Business Logic Testing
    • Authentication Testing
    • Authorization Testing
    • Session Management Testing
    • Data Validation Testing
    • Denial Of Service Testing
    • Web Services Testing
    • Ajax Testing