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 43 guests online
 
Free Business and Tech Magazines and eBooks

You are here: Home arrow Ethical Hacking Discussions and Related Certificationsarrow Network Pen Testingarrow Pen testing logs
EH-Net
May 18, 2013, 05:56:34 AM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Go back to The Ethical Hacker Network Online Magazine Home Page
 
   Home   Help Calendar Login Register  
Pages: [1]   Go Down
  Print  
Author Topic: Pen testing logs  (Read 4541 times)
0 Members and 1 Guest are viewing this topic.
Breeze
Newbie
*
Offline Offline

Posts: 6



View Profile WWW
« on: February 02, 2010, 01:52:54 PM »

Not being a pen tester, I have been wondering how one would keep track of the information gathered during the test.

The way I see it, there is always the possibility of needing information you have gathered for legal/forensic reasons later so I imagine the amount of data kept and it's integrity should be high.

Not only that but there is tons of information to sift through on Google, etc.

Where would you keep and collate this? Is there a tool for this sort of thing? Do you just create a new SQL database every time? do you need to use a keystroke logger on your own machine plus some kind of mitm logger on the network?  Huh

That is actually quite a lot of questions, sorry.  Smiley
Logged

C|EH
UNIX
Hero Member
*****
Offline Offline

Posts: 1234


View Profile
« Reply #1 on: February 02, 2010, 02:00:24 PM »

I read that often similar tools such as keyloggers and desktop-monitoring software are used, not only to document everything, but also to have some kind of backup. Documentation is the a-and-o of pentesting.

In terms of forensic tasks usually a copy of the target system is taken and then used for analysis - the original is most often stored in a safe or similar secure environment. There are some members here which can certainly give you more detailed and accurate information on this one. Wink
Logged
hayabusa
Hero Member
*****
Offline Offline

Posts: 1630



View Profile
« Reply #2 on: February 02, 2010, 02:07:13 PM »

Hi Breeze.

The answers you get will vary, to an extent.  It depends upon what tools you / the tester uses.  Many tools (such as Core Impact) setup a separate project with it's own mini database and logs, for each project you are doing.  GFI Languard behaves similarly, for record-keeping, for an individual test scenario.  But when using BackTrack or other tools, you often use other means and data folders for record-keeping, where you may file screen captures, logs, files you extracted from a customer machine, etc.  It's sort of based upon the tester, as to how you want to keep record, but you're absolutely correct, in that ALL records should be kept, both for clarification of what steps and tests were performed, as well as for your own safety, after the testing is performed, to cover your backside.  And as for how any / all of this data is collected to begin with, each tester has their own preferences, but in the end, it could be keyloggers, packet captures, screen captures, or any one of MANY other methods of capturing your activities for record.

Once my tests have been completed and the customer has signed off on the deliverables, I securely archive all of the data (won't go into how, as again, this changes per tester, and I prefer to keep my methods to myself,  Wink ) and file it away, for future reference, if absolutely necessary.  (Otherwise I never open it again.)

Hope that helps, at least a little bit...
Logged

~ hayabusa ~ 

"All men can see these tactics whereby I conquer, but what none can see is the strategy out of which victory is evolved." - Sun Tzu, 'The Art of War'


OSCE, OSCP , GPEN, C|EH
Breeze
Newbie
*
Offline Offline

Posts: 6



View Profile WWW
« Reply #3 on: February 02, 2010, 03:32:06 PM »

Wow, thanks for the quick response guys.

This was kind of what I was expecting, that it is down to preference. I have not yet used Core Impact, or GFI Languard, so that is probably my next step. It seems like to get a good, repeatable, technique going for logging this info you would almost need a virtual enterprise environment that you could just build and disassemble at the stat and end of a project.

Hayabusa, you also raised another interesting point about storage of such data. I know you don't want to give away your methods, but I would guess people use HDD in safe deposit boxes Huh but then you have a constant overhead, so a safe maybe? any online storage would seem too risky. Roll Eyes

Don't want to pry, I'm just interested.
Logged

C|EH
hayabusa
Hero Member
*****
Offline Offline

Posts: 1630



View Profile
« Reply #4 on: February 02, 2010, 03:40:26 PM »

I won't discuss as far as safe deposit boxes, but I will tell you that in my case, all data, first is safely tar'd / zipped up into a passworded file and stored on encrypted file store, and I then store the encrypted files in an undisclosed, 'safe' location.

Again, as with the logging, it's all about preference, and yuo sort of have to work out what's best for you and for your customers' satisfaction and safety.
Logged

~ hayabusa ~ 

"All men can see these tactics whereby I conquer, but what none can see is the strategy out of which victory is evolved." - Sun Tzu, 'The Art of War'


OSCE, OSCP , GPEN, C|EH
Ketchup
Hero Member
*****
Offline Offline

Posts: 1021



View Profile
« Reply #5 on: February 02, 2010, 04:09:43 PM »

Like hayabusa said, I too maintain all my captures, screenshots, logs, and other output on a TrueCrypt drive.   If I am really paranoid and I am testing something I think may crash, I may record the entire session in Wireshark or tcpdump.   I have another TrueCrypt encrypted USB drive for such purposes.   
Logged

~~~~~~~~~~~~~~
Ketchup
Pages: [1]   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.18 | SMF © 2013, Simple Machines
Joomla Bridge by JoomlaHacks.com
Valid XHTML 1.0! Valid CSS!
Page created in 0.117 seconds with 23 queries.
 
Exclusive Deal

sansfire13_245x90_cw90.jpg
SANSFIRE 2013
June 15 - 22

5% Off w/ Code: EHN_5

SANS Deals 4 EH-Netters
5% OFF Any SANS Course in Any Format!
Coupon Code: EHN_5 Including SANS Rocky Mountain 2013 & SANS Boston 2013
Polls
Compared to this year, 2013 will be:
 
Recent Forum Topics
EH-Net News Feeds
Latest Additions
 
         
Advertisement

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