T1595.002 Vulnerability Scanning

---
name: "T1595.002_vulnerability-scanning"
description: "Adversaries may scan victims for vulnerabilities that can be used during targeting."
category: "information-gathering"
version: "18.1"
author: "cyberstrike-official"
tags:
  - mitre-attack
  - enterprise
  - t1595.002
  - reconnaissance
  - pre
  - sub-technique
technique_id: "T1595.002"
tactic: "reconnaissance"
all_tactics:
  - reconnaissance
platforms:
  - PRE
mitre_url: "https://attack.mitre.org/techniques/T1595/002"
tech_stack:
  - pre
cwe_ids:
  - CWE-200
chains_with:
  - T1595
  - T1595.001
  - T1595.003
prerequisites:
  - T1595
severity_boost:
  T1595: "Chain with T1595 for deeper attack path"
  T1595.001: "Chain with T1595.001 for deeper attack path"
  T1595.003: "Chain with T1595.003 for deeper attack path"
---

# T1595.002 Vulnerability Scanning

> **Sub-technique of:** T1595

## High-Level Description

Adversaries may scan victims for vulnerabilities that can be used during targeting. Vulnerability scans typically check if the configuration of a target host/application (ex: software and version) potentially aligns with the target of a specific exploit the adversary may seek to use.

These scans may also include more broad attempts to Gather Victim Host Information that can be used to identify more commonly known, exploitable vulnerabilities. Vulnerability scans typically harvest running software and version numbers via server banners, listening ports, or other network artifacts. Information from these scans may reveal opportunities for other forms of reconnaissance (ex: Search Open Websites/Domains or Search Open Technical Databases), establishing operational resources (ex: Develop Capabilities or Obtain Capabilities), and/or initial access (ex: Exploit Public-Facing Application).

## Kill Chain Phase

- Reconnaissance (TA0043)

**Platforms:** PRE

## What to Check

- [ ] Identify if Vulnerability Scanning technique is applicable to target environment
- [ ] Check PRE systems for indicators of Vulnerability Scanning
- [ ] Verify mitigations are bypassed or absent (1 known mitigations)
- [ ] Assess detection coverage (1 detection strategies)

## How to Test

### Manual Testing

1. **Identify Attack Surface**: Determine if the target environment is susceptible to Vulnerability Scanning by examining the target platforms (PRE).

2. **Assess Existing Defenses**: Review whether mitigations for T1595.002 are in place. If defenses are absent or misconfigured, this technique may be exploitable.

3. **Execute Test**: Use tools and methods described in the MITRE ATT&CK page and external references below.

> **Note**: No Atomic Red Team tests available for this technique. See [Atomic Red Team GitHub](https://github.com/redcanaryco/atomic-red-team) for updates.

## Remediation Guide

### M1056 Pre-compromise

This technique cannot be easily mitigated with preventive controls since it is based on behaviors performed outside of the scope of enterprise defenses and controls. Efforts should focus on minimizing the amount and sensitivity of data available to external parties.

## Detection

### Detection of Vulnerability Scanning

## Risk Assessment

| Finding                                     | Severity | Impact         |
| ------------------------------------------- | -------- | -------------- |
| Vulnerability Scanning technique applicable | High     | Reconnaissance |

## CWE Categories

| CWE ID  | Title                             |
| ------- | --------------------------------- |
| CWE-200 | Exposure of Sensitive Information |

## References

- [OWASP Vuln Scanning](https://owasp.org/www-project-automated-threats-to-web-applications/assets/oats/EN/OAT-014_Vulnerability_Scanning)
- [Atomic Red Team - T1595.002](https://github.com/redcanaryco/atomic-red-team/tree/master/atomics/T1595.002)
- [MITRE ATT&CK - T1595.002](https://attack.mitre.org/techniques/T1595/002)