Wednesday, February 25, 2009

Sample Letter For L Community Service

[STANDARD] OWASP - Episode 6

This new episode is a continuation of our study the new the standard version of OWASP. The goal is to do penetration testing methodology and as a way to give new ideas. Specifically, this sixth episode focuses on specific business of the target application.
  • 1 - Foreword
  • The sixth episode we deal with here is the fifth chapter of active testing after a first chapter of discovery. In the Standard OWASP v3, this is the chapter 4.7 on testing WEB application and target particular business functions that can be prone to problems security.



2 -

Since each application is different, it n 'there is no specific tests that we can provide certainty. However, a specific approach is proposed to cover more of the application and try to find potential security holes.

1 / Understanding of application:

This involves awareness of the opportunities offered by the application. For this, the auditor may help documentation available (in white box testing) and its own exploration of the application by browsing the different pages. It is important to note at this stage:
  • the limits encountered
  • (which we will then try to circumvent) the
  • different ways to perform certain actions (including the most important actions).

This first step provides us with an overview of the application and our initial approaches.

2 / Establish the test case:
core functionality (searching for a product, ordering a product, ...);
the workflow of an action (eg the command to the validation a purchase);
the different roles involved in the application (eg the administrator to the director);
different departments (IT department, marketing, ...);

rights and privileges granted to each ... and verify.
These five elements should enable us to form a table with all actions permitted for each user level.

3 / Test Preparation
Following the previous step, we must determine by the test (s) to perform accordingly to ensure that the application is properly partitioned by type of stakeholder and action.

Therefore, after this third step, a new table is created containing the resulting tests from the previous step. So we will rely heavily on the previous table.
4 / Getting the prerequisites Now that the tests to be performed are known, it is time to ask the customer the necessary resources to accomplish them. Most of the time, it will be accounts with different privilege levels. Also, there may be administrative URL for the most privileged accounts. It is best to start with a standard account and request resources as and when not to influence the tests. example, is it possible to find and access the administration interface with a standard account without notice?

5 / Running Tests
Running tests determined from Table 3 / consider most Time:
query parsing HTTP

the protections afforded (or not) and data flows (eg. encryption);
error recovery when we test the limits or outside range (eg : Negative or very large a sum);
finding information hidden in the treatment of shares;

modifying data during action;
  • circumvention of one or more validation steps; etc..
  • Have fun!
The next episode.



0 comments:

Post a Comment