Skip to content

Vectra AI Detect Integration Guide🔗

Vectra AI Detect (formerly Cognito Detect) provides network and account threat detection. This integration forwards Vectra Brain logs to Secureworks® Taegis™ XDR using Common Event Format (CEF) over syslog.

CEF format required

Select CEF as the output format in Vectra. The Standard and JSON output formats are not supported by this integration's normalizer.

Prerequisites🔗

  • An operational Vectra Detect deployment and administrator access to configure syslog forwarding on the Brain.
  • A configured XDR Collector and its management IP address or hostname.
  • Network access from the Vectra Brain to the collector's syslog listener, using the same destination port and protocol on both sides.

Connectivity Requirements🔗

Source Destination Port/Protocol
Vectra Brain Taegis™ XDR Collector (mgmt IP) TCP/601 or UDP/514 (default listeners)
Vectra Brain Taegis™ XDR Collector (mgmt IP) Configured TCP port for a TLS-enabled syslog listener

For encrypted forwarding, configure a TLS Enabled Syslog listener before configuring Vectra. Use that listener's port and follow the certificate requirements in the Vectra syslog guide linked below.

Data Provided from Integration🔗

All events normalized by this integration use sensor_type = 'Vectra Detect'.

Vectra log type Advanced Search schema Data provided
Host Detection and Account Detection thirdparty Detection name and ID, category, severity, threat and certainty scores, observation times, and host or account context where present
Campaigns thirdparty Campaign identifiers, involved endpoints, action, reason, and event URL where present
Audit: identifiable login/logout with a user and known outcome auth Authentication action, user, source address, target Brain, and outcome
Audit: administrative, ambiguous, or pending activity cloudaudit User, role, source address, operation message, outcome, and vendor context
Host Scoring, Account Scoring, and Health generic Score changes, heartbeat messages, and other health events, with vendor fields retained in event tags

Note

XDR detectors are not guaranteed to be triggered, even if a data source's logs are normalized to a schema associated with a given detector. However, you can create Custom Detection Rules to generate detections based on normalized data from a data source.

Configure Vectra Syslog Forwarding🔗

Follow Vectra's Syslog guide (QUX) to configure CEF syslog forwarding from the Brain. The vendor guide maintains the current configuration steps, supported transports, certificate requirements, and log type descriptions.

Use these values when following the vendor guide:

Vectra setting Value for XDR
Destination Management IP address or hostname of your XDR Collector
Port and protocol Match the collector listener from Connectivity Requirements
Format CEF (required)
Log types Enable Host Detection and Account Detection for detection data.
Enable Campaigns or Audit if you also want those events.
Host Scoring, Account Scoring, and Health remain in generic.

The documented CEF feed identifies the vendor as Vectra Networks or Vectra and the product as X Series. These names may appear in the log header even though the product is named Vectra AI Detect. The anonymized sample below uses Vectra version 9.14.

Verify Forwarding🔗

  1. Save and test the syslog destination using the procedure in the Vectra syslog guide.
  2. Check collector status and recent activity in Manage Data Collectors.
  3. Run the searches below to verify event arrival and the expected normalized dataset. Verify that an actual Host Detection or Account Detection event appears in thirdparty. Note that a successful vendor test alone doesn't confirm receipt or normalization.

Example Query Language Searches🔗

To search all Vectra events from the last 24 hours:

FROM thirdparty, auth, cloudaudit, generic WHERE sensor_type = 'Vectra Detect' AND EARLIEST=-24h

To search detection and campaign events:

FROM thirdparty WHERE sensor_type = 'Vectra Detect' AND EARLIEST=-24h

To search for Suspicious Active Directory Operations events:

FROM thirdparty WHERE sensor_type = 'Vectra Detect' AND log_type = 'suspicious_ad' AND EARLIEST=-24h

To search for events from a specific Vectra Brain:

FROM thirdparty WHERE sensor_type = 'Vectra Detect' AND sensor_id = '192.0.2.1' AND EARLIEST=-24h

Troubleshooting🔗

  • No events arrive: Verify the collector is online, the Brain can reach its management address, and the destination port and protocol match the configured listener. For TLS, check the listener configuration and certificate validation using the linked Taegis and Vectra guides.
  • Events arrive as Generic: Confirm Vectra is sending CEF, and inspect the original message for the documented vendor/product identifiers. Host/account score changes and all health events intentionally remain in generic; use a Host Detection or Account Detection event to verify detection normalization.
  • A test arrives but no detection events appear: Confirm the appropriate log types are enabled in Vectra, then check for actual events in the search time range. A heartbeat or configuration test is not a substitute for a detection event.

Sample Logs🔗

Host Detection🔗

The following anonymized CEF sample represents a Suspicious Active Directory Operations event:

<13>Nov 12 00:56:08 brain-01 vectra_cef_v2 -: CEF:0|Vectra Networks|X Series|9.14|suspicious_ad|Suspicious Active Directory Operations|9.0|externalId=600024 cat=LATERAL MOVEMENT dvc=192.0.2.1 dvchost=host01.example.test shost=host22.example.test src=192.0.2.25 flexNumber1Label=threat flexNumber1=90 flexNumber2Label=certainty flexNumber2=40 cs4Label=Vectra Event URL cs4=https://192.0.2.1/detections/600024?detail_id\\=700001 cs5Label=triaged cs5=False dst=192.0.2.26 dhost= proto= dpt=50637 out=0 in=0 start=1791897419000 end=1794440819000