Link Search Menu Expand Document
  1. 6 Server OS Penetration Tasks
    1. 6.1 Information Gathering
      1. 6.1.1 DNS Interrogation
      2. 6.1.2 Port Scanning
      3. 6.1.3 Service Fingerprinting
      4. 6.1.4 SNMP Enumeration
      5. 6.1.5 Packet Sniffing
    2. 6.2 Vulnerability Analysis
      1. 6.2.1 Unauthenticated Vulnerability Scanning
      2. 6.2.2 Authenticated Vulnerability Scanning
      3. 6.2.3 Vulnerability Validation
      4. 6.2.4 Packet Capture Analysis
    3. 6.3 Server OS Exploitation
      1. 6.3.1 Identify Attack Avenues
      2. 6.3.2 Vulnerability Exploitation
      3. 6.3.3 Post Exploitation

6 Server OS Penetration Tasks

This section pertains to the testing of the operating system of the control servers. This follows more traditional network-based vulnerability assessment of the windows, unix, and linux based systems, such as the identification of missing security patches, insecure configurations, or presence of insecure services. The overarching goal is to identify and exploit un-patched vulnerabilities to gain access to the control server. The following table maps specific components that should be considered for each Smart Grid product domain.

AMI



Headend  servers  (often  several  servers  make  up  the  “headend”)

The  MDMS.
DR









DRAS

Gateway

BAS

DCU  may  run  an  OS
DER

DER  Management  Server
DGM



Management  servers  for  each  vendor’s  DGM  devices

DGM  Server
ET



EV  management  server

Gateway  may  run  an  OS
WAMPAC









Servers  hosting  WAMPAC  applications

PDCs  with  operating  systems

WAMPAC  datastore  applications

WAMPAC  software  installed  on  commodity  operating  systems.

Figure 6a below shows the overall process flow of the task sub-categories in this section. The figure shows the three task sub-categories must be performed in series. As in previous diagrams in this document, the colors represent the recommended likelihood that a utility should consider performing these task sub-categories, and the relative level of expertise required.

Figure 6a: Server OS Subcategory Flow Figure 6a: Server OS Subcategory Flow

Each subcategory below will include a similar diagram depicting the process flow and recommended likelihood to perform for each task.

Suggested Tools:

  • Standard network vulnerability assessment and penetration testing tools such as found on the BackTrack distribution

  • Guidance documents such as the Penetration Testing Standard (PTES)

6.1 Information Gathering

Figure 6.1a: OS Information Gathering Task Flow Figure 6.1a: OS Information Gathering Task Flow

6.1.1 DNS Interrogation

Level of Effort: Low

Task Description: Use tools to attempt zone transfers and perform queries from target Domain Name Service (DNS) servers.

Task Goal: Identify targets, verify ownership, and detect anomalies.

6.1.2 Port Scanning

Level of Effort: Low

Task Description: Use tools that send requests to possible application layer services (such as scanning TCP and UDP ports to discover services like HTTP and SSH).

Task Goal: Identify all listening services and possible firewall rules.

6.1.3 Service Fingerprinting

Level of Effort: Low

Task Description: Use tools to examine listening services.

Task Goal: Identify the nature and function of all listening services.

6.1.4 SNMP Enumeration

Level of Effort: Low

Task Description: Use tools to attempt to examine SNMP services.

Task Goal: Identify insecure SNMP services, extract information about the endpoints, and identify vulnerabilities that allow attackers to reconfigure endpoints.

6.1.5 Packet Sniffing

Level of Effort: Low

Task Description: Capture various samples of network communications.

Task Goal: Collect samples for later analysis.

6.2 Vulnerability Analysis

Figure 6.2a: OS Vulnerability Analysis Task Flow Figure 6.2a: OS Vulnerability Analysis Task Flow

6.2.1 Unauthenticated Vulnerability Scanning

Level of Effort: Medium

Task Description: Use automated tools without credentials to identify known vulnerabilities in network services and their respective systems.

Task Goal: Identify vulnerabilities in the operating system and the network services

6.2.2 Authenticated Vulnerability Scanning

Level of Effort: Medium

Task Description: Use automated tools that use valid credentials to authenticate to systems and identify known vulnerabilities with installed software.

Task Goal: Identify vulnerabilities in the operating system and installed software.

6.2.3 Vulnerability Validation

Level of Effort: Medium

Task Description: Manually validate findings from automated tools where possible. Merge and combine findings where applicable.

Task Goal: Consolidate findings and remove any false positive findings that you identify.

6.2.4 Packet Capture Analysis

Level of Effort: Low to Medium

Task Description: Examine network traffic samples and look for protocols with known vulnerabilities such as session hijacking, weak authentication, or weak/no cryptographic protections.

Task Goal: Identify vulnerabilities in network protocols and network communications.

6.3 Server OS Exploitation

Figure 6.3a: Server OS Exploitation Task Flow Figure 6.3a: Server OS Exploitation Task Flow

6.3.1 Identify Attack Avenues

Level of Effort: Medium

Task Description: Review all findings and outputs from previous tasks and identify plausible attacks that have a moderate chance of success. Prioritize these possible attacks by likelihood and the tester’s ability to execute them.

Task Goal: Organize and plan next steps.

6.3.2 Vulnerability Exploitation

Level of Effort: Low to Medium

Task Description: Create proof of concept attacks to demonstrate the feasibility and business risk created by the discovered vulnerabilities. Once a vulnerability has been exploited, attempt to pivot and identify additional vulnerabilities to exploit.

Task Goal: Validate the assumed business risk created by the identified vulnerabilities and identify additional targets of opportunity.

6.3.3 Post Exploitation

Level of Effort: Low to Medium

Task Description: Remove any code, data, or configurations that were added to the system as a part of the assessment.

Task Goal: Return the systems to their pre-assessment state.


Table of Contents