# Intel Threat Detection Technology Architecture reference: Feex Also called Threat Detection Intel Threat Detection Technology, TDT, supplies hardware-assisted telemetry and capabilities for integrated endpoint security software. It is not a standalone antivirus verdict supplied by the CPU. ## What you need to know Intel Threat Detection Technology, TDT, supplies hardware-assisted telemetry and capabilities for integrated endpoint security software. It is not a standalone antivirus verdict supplied by the CPU. ## How it works A compatible security product can use processor telemetry and supported offload mechanisms as inputs to its detection pipeline. Which signals and accelerators are available depends on the platform and software integration. The endpoint product still performs policy, detection, response and update management. ## Where it is useful An integrated endpoint solution can analyze supported behavior signals to supplement its other detection techniques. Whether the integration is active must be established in that product's status and deployment documentation. ## How to check support and enablement Match the exact platform to Intel's supported capabilities and the security vendor's integration requirements. Verify the endpoint product's active configuration and diagnostic output rather than expecting a generic CPUID bit to report antivirus status. Platform features can depend on the motherboard, chipset, firmware provisioning, drivers and product tier. The CPU specification is one input, not a complete description of the assembled computer or its active configuration. ## What the feature does not establish A TDT support field does not mean a compatible security product is installed, enabled or detecting every attack. It cannot establish that a particular process is safe, and it does not replace OS, firmware or endpoint updates. ## Compatibility and performance in practice Before changing firmware, management or boot-storage settings, identify the exact system and follow its manufacturer's supported procedure. Record the existing configuration and preserve recovery access. A generic feature article cannot supply a universal firmware menu sequence. ## A practical verification checklist 1. Record the exact processor or platform model and the application, OS and runtime versions involved. Preserve the wording of the actual error or requirement. 2. Check the manufacturer reference for that exact model, then inspect the effective capability and enabled state in the environment where the program runs. 3. Compare every requirement of the selected binary or backend. A similarly named feature, alias or broad technology label is not enough. 4. Confirm the application selected the intended implementation. Use its documented diagnostics and a supported fallback when requirements are not met. 5. Make one supported change at a time and repeat the same workload. Keep the original configuration and recovery path available. ## If the feature is listed but software cannot use it Start with the exact failing component. A hardware database describes recorded capability; the operating system or hypervisor can expose a different effective environment. An illegal-instruction error also needs investigation of the actual faulting instruction and binary build, because corruption or an unrelated unsupported instruction can produce a similar symptom. Install the application, driver or runtime version supported for the exact platform, and use the vendor's documented baseline or fallback build if needed. A software update cannot create an instruction that the processor lacks. Firmware and security-policy changes should follow the system manufacturer's procedure and a recovery plan rather than a generic optimization recipe. ## Related features and useful distinctions [Intel Hardware Shield](https://feex.it/wiki/hardware/system/hardware-shield/) · [Control-flow Enforcement (CET)](https://feex.it/wiki/hardware/system/cet/) · [Boot Guard](https://feex.it/wiki/hardware/system/boot-guard/) ## Sources and scope of this explanation [Intel Threat Detection Technology](https://www.intel.com/content/www/us/en/architecture-and-technology/vpro/vpro-security/threat-detection-technology.html) · [Intel vPro platform brief: hardware and software security](https://www.intel.com/content/www/us/en/products/docs/processors/vpro/13th-gen-vpro-processors-brief.html) These references establish architectural behavior and software requirements. They do not independently verify every feature value on a linked hardware model page. For model support, use that page's manufacturer evidence and check the effective system configuration. This article does not supply a benchmark, certification or independent review date. ## Related These entities connect to this article. Type is shown on every link. [Intel Hardware Shield: Architecture reference](https://feex.it/wiki/hardware/system/hardware-shield/)[Control-flow Enforcement (CET): Architecture reference](https://feex.it/wiki/hardware/system/cet/)[Boot Guard: Architecture reference](https://feex.it/wiki/hardware/system/boot-guard/) ## Sources and verification Editorial ownership: Feex. No independent review date is recorded. [How we research](https://feex.it/wiki/research/). - [Intel Threat Detection Technology ](https://www.intel.com/content/www/us/en/architecture-and-technology/vpro/vpro-security/threat-detection-technology.html)· Hardware-assisted telemetry and endpoint security integration. Support is not an antivirus verdict or proof of active protection. - [Intel vPro platform brief: hardware and software security ](https://www.intel.com/content/www/us/en/products/docs/processors/vpro/13th-gen-vpro-processors-brief.html)· Describes the Hardware Shield portfolio and platform requirements for this generation. It does not establish identical capabilities across all vPro generations. [Report a correction to Feex](https://feex.it/contact/) ## Was this article useful? A yes or no is enough. Pick a reason if you want, or add a short note. Quick facts The short identity of this page. Specs, sources, and the full story stay in the article. --- Source: [Canonical Feex Wiki page](https://feex.it/wiki/hardware/system/threat-detection/) [Developer guide](https://feex.it/wiki/developers/) | [API policy](https://feex.it/developers/api-policy/) | [Agent guidance](https://feex.it/wiki/llms.txt)