Research session unavailable. No participant research session is associated with this browser. Use the participant access link supplied by the facilitator.
← Back to dashboard
TA0043 Reconnaissance · T1681 · Search Threat Vendor Data

Search Threat Vendor Data: recognize the technique

Lesson Purpose

What you are learning

This technique is about using information from security vendors, researchers, and intelligence providers. Reports may discuss malware, vulnerabilities, infrastructure, campaigns, exposed assets, or attacker behavior. Vendor data is useful context, but it is not automatic proof that an organization is affected.

Learning Objectives
Why This Matters

Security teams use vendor reports every day. Reports can be incomplete, old, or focused on other organizations, so defenders should compare them with their own current evidence. In practice, defenders compare public information with internal records, logs, inventories, and monitoring data to decide whether the information is current, expected, and useful to an attacker. The goal is not to remove all public information, but to reduce unnecessary exposure and review information that could create avoidable security risk.

OWASP Web Security Testing Guide (WSTG)

Use a repeatable web-testing method

Connect this ATT&CK training activity to the WSTG approach: establish expected behavior, identify the relevant attack surface, change one controlled input or observation at a time, compare the response with the baseline, and record evidence before drawing a conclusion.

For reconnaissance-oriented lessons such as T1595, treat reachability, exposed services, and observable application behavior as information gathering. A reachable service is evidence about exposure; it is not by itself proof of a vulnerability.

Open WSTG web security fundamentals
Exercise
Before You Practice

Practice Preparation

Use these lesson concepts for the ungraded practice activity below. You do not need outside research.

  • Threat vendors may provide vulnerability information, indicators/infrastructure, malware or campaign reporting, and exposed-asset observations.
  • Before acting, ask whether the report is current and actually applies to your organization.
  • Confirm or challenge vendor reporting with internal asset inventory, DNS/network telemetry, endpoint logs, vulnerability data, and other organization-specific evidence.

This is ungraded practice. Use the lesson material above; exact wording is not required. Identify three kinds of information a threat vendor might provide. Then name one question a defender should ask before acting and two ways internal evidence can confirm or challenge the report. No external target interaction is required.

Knowledge Check

Check your understanding

Answer the questions shown below. You must answer at least 2 correctly before marking this concept lesson complete.

1. Which statement best describes Search Threat Vendor Data?
2. A defender is investigating activity related to the behavior described in this lesson. Which evidence set would provide the most relevant context?
3. Which interpretation best avoids overstating what the observed information proves?
4. Consider this behavior: This technique is about using information from security vendors, researchers, and intelligence providers. Reports may discuss malware, vulnerabilities, infrastructure, campaigns, exposed assets, or attacker behavior. Which ATT&CK technique best matches the behavior?
5. A defender wants to reduce or validate the risk described in this scenario. Which response is the most appropriate?
6. Which limitation should a defender keep in mind before drawing a conclusion from this evidence?
Learning Moment

Threat-vendor data is useful context, not proof. Combine it with current internal evidence. Defenders should confirm context with more than one source and reduce unnecessary exposure where practical.

Defender Perspective

Useful sources include threat-intelligence feeds, vendor advisories, vulnerability reports, exposure reports, asset inventories, SIEM data, and incident records. Check whether the reported issue applies to systems the organization owns, how current the report is, and whether internal logs support it. Reduce risk by prioritizing relevant vulnerabilities and tracking the life cycle of indicators. Risk reduction includes reviewing what is exposed and using controls to limit information that is not needed.

Continue Your Learning Pathway

Next Step · Continue ATT&CK Training

Continue building your reconnaissance and resource-development foundation with the next ATT&CK lesson.

Complete this lesson first. Finish the required lesson activity and knowledge check, if present, before continuing.

Return to dashboard