Image
 
linkedin_logo.png rss_logo.jpg
twitter_logo.png youtube_logo.jpg
Latest Additions
 
EH-Net Login
Welcome Guest.






Lost Password?
No account yet? Register
Who's Online
We have 65 guests and 1 member online
EH-Net News Feeds
Latest Additions
 
Advertisement

You are here: Home arrow Forum arrow Ethical Hacking Discussions and Related Certificationsarrow Web Applicationsarrow Web Applications PenTesting Methodology
EH-Net
May 25, 2012, 12:43:44 PM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Advertise on EH-Net!! - Reasonable Rates, Highly Targeted Audience.
 
   Home   Help Calendar Login Register  
Pages: [1]   Go Down
  Print  
Author Topic: Web Applications PenTesting Methodology  (Read 6415 times)
0 Members and 3 Guests are viewing this topic.
H1t M0nk3y
Hero Member
*****
Offline Offline

Posts: 660



View Profile
« on: February 12, 2010, 06:24:15 AM »

Hi,

I currently have to perform a security evaluation of a web site. The server itself (OS) and the network are not in the scope because my client has no power over them. However, they can change the web server configuration and since they're the ones developing the web application, they can modify it.

So, my task is to do a security evaluation of the web application and the web server. Where do I start?

I have completed the reconnaissance phase. I suspect some XSS and SQL Injection vulnerabilities. But if I really want to do a good job and produce a very complete report, with the ad-hoc way I am doing this, I am afraid of missing some stuff...

I have looked a 3 books on the subject and browsed the OWASP web site, but I just can't seem to find a good methodology for pentesting web apps.

Any suggestions?

Thanks
 
Logged

GPEN, GSEC, CEH, CISSP, PMP
Ketchup
Hero Member
*****
Offline Offline

Posts: 1006



View Profile
« Reply #1 on: February 12, 2010, 07:10:45 AM »

I think that the same methodology as usual applies.   You have your automated scanners, proxies, manual testing, source code audit, fuzzing, exploiting, etc. 

I like to use this framework for pen testing.  I think that you can adapt it to your project.

http://www.vulnerabilityassessment.co.uk/Penetration%20Test.html
Logged

~~~~~~~~~~~~~~
Ketchup
aweSEC
Hero Member
*****
Offline Offline

Posts: 1100


View Profile
« Reply #2 on: February 12, 2010, 08:12:02 AM »

In terms of OWASP you might have a look at their Testing Guide, which may help additionally to what Ketchup already recommended.

Is source code audit within the scope?
Logged
Dark_Knight
Full Member
***
Offline Offline

Posts: 215


View Profile WWW
« Reply #3 on: February 12, 2010, 06:04:10 PM »

I think that the same methodology as usual applies.   You have your automated scanners, proxies, manual testing, source code audit, fuzzing, exploiting, etc. 

I like to use this framework for pen testing.  I think that you can adapt it to your project.

http://www.vulnerabilityassessment.co.uk/Penetration%20Test.html
Thanks for posting this. Smiley
Logged

CEH, OSCP, GPEN, GWAPT, GCIA
http://sector876.blogspot.com
H1t M0nk3y
Hero Member
*****
Offline Offline

Posts: 660



View Profile
« Reply #4 on: February 14, 2010, 07:16:21 AM »

Yes, source code audit is within the scope.
But with 60 000 lines of code, where should I start?

BTW, I am a web developer, so I understand the code well.
Logged

GPEN, GSEC, CEH, CISSP, PMP
Ketchup
Hero Member
*****
Offline Offline

Posts: 1006



View Profile
« Reply #5 on: February 14, 2010, 08:51:41 AM »

There are a bunch of source code auditing tools that may help you with this problem.  You can add a bit of manual spot checking as well. 

http://www.owasp.org/index.php/Source_Code_Analysis_Tools
Logged

~~~~~~~~~~~~~~
Ketchup
zeroflaw
Full Member
***
Offline Offline

Posts: 184



View Profile
« Reply #6 on: February 14, 2010, 08:52:58 AM »

Well if you're going to audit the source code, then I guess you could scan the code for possibly dangerous functions that perform jobs such as string concatenation or forms that allow users to upload files to the server. Also find out how the applications deals with sessions.

Because you already suspect some XSS and SQL injection vulnerabilities, I would mark all input fields and other possible entry points. Then find out how the code deals with those. Document all your findings, explain the vulnerabilities and how to fix them.

I don't know much about good tools, but I've used Acunetix Web Vulnerability Scanner last year and was very pleased with the results.

You probably figured most of this out already, but I'm just trying to help Tongue

ZF
Logged

ZF
H1t M0nk3y
Hero Member
*****
Offline Offline

Posts: 660



View Profile
« Reply #7 on: February 14, 2010, 05:58:07 PM »

Thank you very much guys, I will give these tools a try this week.
Logged

GPEN, GSEC, CEH, CISSP, PMP
Pages: [1]   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.16 | SMF © 2011, Simple Machines
Joomla Bridge by JoomlaHacks.com
Valid XHTML 1.0! Valid CSS!
Page created in 0.32 seconds with 22 queries.
 

gk_static-ad_feb2012.jpg
Global Knowledge: Build Security Skills to Protect & Defend

els_130x200fixed2.gif
eLearnSecurity Student Course Now Live!
5% Off with Code
ELS-EH-5

SANS Deals 4 EH-Netters
$150 OFF Any SANS Course in Any Format!
Coupon Code: EHN_Connect Including SANS Security West 2012 & SANSFIRE 2012
Recent Forum Topics

cbtnuggets_logo_125.jpg
Try CBT Nuggets Free!

Vote For EH-Net

Add to Technorati Favorites
technorati fave

 
         
Advertisement

© 2012 The Ethical Hacker Network
Joomla! is Free Software released under the GNU/GPL License.