We're Here! The last step with the end of our adventure on the methodology OWASP. After seeing a large number of checkpoints - gathering information for the operation of injections - it remains for us to see the possible attacks on AJAX. I shall conclude with a quick summary on the vision of the standard for the "post-pentest.
Sunday, March 22, 2009
What Not To Have In A Kitchen Worksheet
[STANDARD] OWASP - Episode 10
We're Here! The last step with the end of our adventure on the methodology OWASP. After seeing a large number of checkpoints - gathering information for the operation of injections - it remains for us to see the possible attacks on AJAX. I shall conclude with a quick summary on the vision of the standard for the "post-pentest.
We're Here! The last step with the end of our adventure on the methodology OWASP. After seeing a large number of checkpoints - gathering information for the operation of injections - it remains for us to see the possible attacks on AJAX. I shall conclude with a quick summary on the vision of the standard for the "post-pentest.
Tenth episode! Yep, here we go! It summarizes the section 4.11 of the standard. I will go very quickly because I am not an expert
AJAX;) But I had to be comprehensive in addressing all the chapters of the methodology. Finally, I will describe briefly in Part 5 of OWASP regarding the work of a PenTest once the tests.
AJAX;) But I had to be comprehensive in addressing all the chapters of the methodology. Finally, I will describe briefly in Part 5 of OWASP regarding the work of a PenTest once the tests.
2 -
testing AJAX applications
AJ-001 - AJAX Vulnerabilities
Our approach is a first step in exploring the potential vulnerabilities in AJAX applications or at least check that there is no flaw exploited by an attacker. To ensure this, we must cover a broad field of research because AJAX apps are affected by many attack vectors: The injection attacks (see episode 7): ex; SQL / XSS / CSRF; denial of service (see episode 8); Attack on the client side (browser). Monitoring new vulnerabilities! (Eg www.securityfocus.com ).
AJ-002 - Testing AJAX applications
There is no accurate method but here we give some hints. The first is to work with a local proxy (eg
paros
- ). As with any type of web application, this kind of tool we can often find "what's wrong." At least it allows us to better understand the application.
- The second track is to find the errors or deficiencies in the JavaScript code. This time, we can use a Firefox extension like Firebug
- . The goal is to find loopholes in the code that will allow us to make shots.
- 3 - After the tests ...
The achievement tests form the core of the provision of a penetration test of a web application. However, the end result is the report.
3.1 - Study of vulnerability
However, the end result is the report. OWASP provides six steps to investigate a fault:
Step 1: Description and identification of risk flaw found
For example, damage to company image, financial loss, etc. ...
Step 2: Estimating the probability
Is it conceivable that Such an attack will occur? If yes, how? For example, if there is financial gain to the key, an attacker will be more motivated to attack the target in question. Second case: imagine a remote attack. If the company has secured external access with properly configured firewall and web protection platform, the attack will be less chance of success.
Step 3: Estimating the impact on the company
Identified risks should be assessed. We bring a different coefficient depending on whether one or more persons may be affected by the operation of the fault study. The financial impact do they consist of a one-day loss of production or of a longer duration?
Step 4: Estimate the severity of risk.
severity risk = probability of achievement (step 2) * Impact (step 3)
We get a criticality "Low" to "Critical".
Step 5: Recommendations
It is time here to provide solutions to correct the faults. The recommendations should take into account the context of the client so they can be realized.
Step 6: Customizing
The idea here is to refine the study by providing a personalized view for the customer solutions tailored to industry, and the changing needs of the business.
3.2 - Report Writing
We cut the ratio by three points:
part for managers (with a summary of tests);
some technical operational teams;
achieving the actual tests taking into account the work done in 3.1.
Conclusion / Briefly
To conclude ten posts about the methodology OWAP, I would say it is for me the only proven standard
- dedicated to Web applications. It has the advantage of treating all types of
- most common tests (eg injections) and testing of new attractions WEB technologies (eg AJAX application). Second, it addresses all these issues in a very technical way
- (Part 4 of the document) but also the surrounding parts to offer a full penetration test (context
- tests, evaluating results, writing a report ).
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment