05.02.2013 Views

download issue 24 here - Help Net Security

download issue 24 here - Help Net Security

download issue 24 here - Help Net Security

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Selecting the right testing approach<br />

Once an Application Criticality Matrix has<br />

been established, you may opt to focus first<br />

on those that, as a result of the assessment,<br />

have been classified in the levels of High and<br />

Critical. Now it is time to determine the kind of<br />

testing that should be used, choosing between<br />

a wide range of approaches:<br />

• Depth vs. breadth. Penetration testing or<br />

vulnerability assessment?<br />

• Inside-out vs. outside-in. Do you want to<br />

know the insider threat level or the outsider<br />

one?<br />

Table 1: Application Criticality Matrix.<br />

• Timing. At what point(s) in the SDLC will the<br />

assessment be performed? (Rule of thumb:<br />

the earlier, the better)<br />

• Manual, automated or “hybrid” testing?<br />

To identify the best suited approach, OWASP,<br />

a worldwide community focused on improving<br />

security of application software, has published<br />

the Application <strong>Security</strong> Verification Standard<br />

(ASVS), which serves as a great starting<br />

point. ASVS defines four levels of Web application<br />

security verification: Automated, Manual<br />

Review, Design Verification and Internal<br />

Verification. Each level includes a set of requirements<br />

for verifying the effectiveness of<br />

security controls that are being used.<br />

www.insecuremag.com 30

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!