-
Notifications
You must be signed in to change notification settings - Fork 24
/
Penetration Testing 3 - Vulnerability Assessment.txt
40 lines (32 loc) · 1.6 KB
/
Penetration Testing 3 - Vulnerability Assessment.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
3.1 Vulnerability Assessment.
Sometimes a client will only ask for a vulnerability assessment instead of a full pentest.
My duty to understand their needs and help.
Assessments are often faster and a lighter load to infrastructure.
No need to proceed to the exploitation phase. So no cycle.
Engagement -> Information Gathering -> Footprint and Scanning -> Vulnerability Assessment -> Reporting
Use of a Vulnerability Scanner
Use known vulnerabilities and secrurity audits to detect the vulnerabilites in a system.
Probes on:
Daemons listening on TCP and UDP Ports
Configuration files of operating systems, software suites, network devices etc.
Windows registry entries.
Popular options:
OpenVAS
Nexpose
GFI Lan Guard
Nessus
Custom applications need to be tested manually.
Learn and understand features
Understand how data is exchanged
Understand how it access resources, databases, servers, local/remote files etc.
Reverse engineering it's logic.
3.2 Nessus.
Two components.
Client - Used to configure scans - Has web interface
Server - Performs scanning process and reports back to the client.
performs scan by sending probes to systems and applicartions and matches reponses against the vulnerability databse.
Process of a vulnerability scanner
1. Determine which hosts are alive and which ports are open
2. Probe open ports to determine the application name and version.
3. Scanner looks up 2. against a list of known vulnerabilities. (List of vulnerabilities can be adjusted).
4. Sends probes to verify the vulnerabilty exists. Prone to false positives.