GuidelinesDraft

Differences between revisions 6 and 7
Revision 6 as of 2008-03-28 18:19:18
Size: 26
Editor: host253-147-dynamic
Comment:
Revision 7 as of 2008-07-01 14:11:39
Size: 1368
Editor: host215-233-static
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
feel free to write here. Ubuntu White Hat - Modus operandi '''DRAFT'''

'''STEP 1'''
0. portscan IP address (with the help of nmap, nessus, etc..)
1. investigate active services and daemons
2. investigate webapps in use

'''STEP 2'''
0. Run a search through CVE Archives with the found services and active daemons running on the computer
1. Run a search through CVE Archives with the webapps used

'''STEP 3'''
0. Penetration test with active services and daemons found to be vulnerable through CVE, only non-desctructive ones (no Denial-of-Service tests)
1. Penetration test with used webapps found to be vulnerable through CVE, only non-desctructive ones (no Denial-of-Service tests)

'''STEP 4'''
0. Auditing of used daemons and webapps

'''STEP 5'''
0. In case a 0day will be found, mail the Ubuntu pentest private mailing list to organize and help writing the bugfix and eventual Advisory
1. Write definitive report with "UWHA" (Ubuntu White Hat Anteater) and send it to Launchpad, in case of vulnerability attach screenshot and POC.
2. Automatically subscribe to launchpad bug the team that handles that specific infrastructure and in case the package is in Ubuntu mirrors and it's still not fixed, then subscribe Security Team (main) or MOTU Swat (universe)

'''STEP 6'''
0. Get in touch with the team responsible for the infrastructure for eventual DoS tests.

Ubuntu White Hat - Modus operandi DRAFT

STEP 1 0. portscan IP address (with the help of nmap, nessus, etc..) 1. investigate active services and daemons 2. investigate webapps in use

STEP 2 0. Run a search through CVE Archives with the found services and active daemons running on the computer 1. Run a search through CVE Archives with the webapps used

STEP 3 0. Penetration test with active services and daemons found to be vulnerable through CVE, only non-desctructive ones (no Denial-of-Service tests) 1. Penetration test with used webapps found to be vulnerable through CVE, only non-desctructive ones (no Denial-of-Service tests)

STEP 4 0. Auditing of used daemons and webapps

STEP 5 0. In case a 0day will be found, mail the Ubuntu pentest private mailing list to organize and help writing the bugfix and eventual Advisory 1. Write definitive report with "UWHA" (Ubuntu White Hat Anteater) and send it to Launchpad, in case of vulnerability attach screenshot and POC. 2. Automatically subscribe to launchpad bug the team that handles that specific infrastructure and in case the package is in Ubuntu mirrors and it's still not fixed, then subscribe Security Team (main) or MOTU Swat (universe)

STEP 6 0. Get in touch with the team responsible for the infrastructure for eventual DoS tests.

UbuntuPentest/GuidelinesDraft (last edited 2008-08-06 16:18:30 by localhost)