ArcSight detection content depth
Two decades of regulated SOC content. Insider threat, account compromise, lateral movement, data exfiltration, credential misuse. Programs inherit the content base rather than starting from scratch.
OpenText • Security operations
Threat Detection and Response (formerly OpenText Core Threat Detection and Response) is the cloud-native member of the ArcSight line, a SaaS SIEM for cloud-first SOCs that puts detection content, investigation workflow and response automation in one platform and correlates with OpenText NDR, UEBA, threat intelligence and long-retention logging.
Through Merito, TDR gets onboarded against the customer's actual log sources, ArcSight content gets tuned to the threat landscape rather than running defaults, and the SaaS SIEM integrates with NDR, UEBA, and threat intelligence as one OpenText SecOps program.
What it is
Threat Detection and Response is OpenText's SaaS SOC platform and carries the ArcSight cloud lineage, rebranded for the cloud-native era. Where Enterprise Security Manager (ArcSight ESM) remains the on-prem flagship for high-throughput regulated SIEM, Threat Detection and Response is the SaaS-first option for programs that have moved past on-prem SIEM constraints. The product covers detection content, investigation workflow, and response automation in one platform.
ArcSight detection content is the operational depth. ArcSight has been deployed in regulated SOC environments for two decades, and the rule library covers the threat patterns regulated programs actually face: insider threat, account compromise, lateral movement, data exfiltration, credential misuse. Programs adopting Threat Detection and Response inherit that content base rather than starting from scratch the way a fresh SIEM deployment would.
Its value grows with the other OpenText SecOps products. Threat Detection and Response correlates with Network Detection and Response (east-west traffic), Behavioral Signals (Interset UEBA), Adversary Signals (MITRE ATT&CK content), Threat Intelligence (curated IOC feeds) and Security Log Analytics (long-retention forensic store). Connected to them it runs unified SOC operations, while on its own it is a SIEM without that cross-product depth.
Threat Detection and Response is a poor fit when it is bought as a straight Splunk replacement. Splunk dominates SIEM market share for cloud-native enterprises, and programs already running mature Splunk pipelines often do not have a compelling delta to justify migration. TDR fits programs that are already on ArcSight and modernizing to SaaS, programs subject to OpenText catalog consolidation, or programs that find Splunk pricing punishing at log volume. Scoping makes that call explicitly instead of pitching TDR as a generic Splunk alternative.
Ideal use cases
What it is best at
Two decades of regulated SOC content. Insider threat, account compromise, lateral movement, data exfiltration, credential misuse. Programs inherit the content base rather than starting from scratch.
Native correlation with NDR, Behavioral Signals (UEBA), Adversary Signals (MITRE), Threat Intelligence, and Security Log Analytics inside the OpenText SecOps line.
No on-prem SIEM tax. Programs cut over from ArcSight ESM modernization to SaaS-shaped SOC operations with detection content, investigation, and response in one platform.
Configurable rule sets, detection-as-code authoring, and tuning workflows so the SOC adapts content to the threat landscape rather than running default rules forever.
Aviator-shaped AI augmentation across the SOC for detection clustering and investigation acceleration.
Core capabilities
What ArcSight cloud actually does on the threat landscape.
ArcSight detection content
Two decades of regulated SOC content covering insider threat, account compromise, lateral movement, data exfiltration, and credential misuse.
Detection-as-code authoring
Custom detection rules authored as code, version-controlled, and tested against historical data.
MITRE ATT&CK alignment
Native MITRE ATT&CK mapping through Adversary Signals integration.
Cloud-native log source coverage
AWS CloudTrail, Azure Activity Log, GCP Cloud Audit, Microsoft 365, Workday, Salesforce, and other cloud-native sources.
Beyond detection into actual SOC operations.
Investigation workflow
Case management, evidence linking, and analyst assignment workflow inside the platform.
Response automation
SOAR-shaped response automation with playbooks, integrations, and approval gates.
Cross-product enrichment
NDR signal, UEBA scoring, threat intel, and forensic context attached to investigations.
SaaS SOC with regulated compliance posture.
Multi-tenant cloud-native operations
SaaS-first delivery with cloud-native scaling and operational simplicity compared to on-prem SIEM.
Compliance reporting
Detection and response records reported as evidence for SOC 2, ISO 27001, FedRAMP, HIPAA and PCI DSS.
Long-retention integration
Hot detection inside TDR; long-retention forensic data inside Security Log Analytics for hunt and investigation.
Aviator AI augmentation
Detection clustering, investigation acceleration, and analyst workflow assistance.
Where it fits in the stack
Deployment and implementation
Licensing and packaging
Threat Detection and Response commercial
SaaS SIEM with detection, investigation, and response in one platform.
Best for: Programs modernizing off ArcSight ESM or building cloud-native SOC capability.
Threat Detection and Response Government Cloud (FedRAMP)
FedRAMP-authorized edition for federal customers and federal contractors.
Best for: Federal SOC programs requiring FedRAMP-authorized SaaS SIEM.
Merito services
Pick the engagement that matches where you are in the lifecycle.
Tenant setup, log source onboarding, detection-content tuning, response-playbook design, cross-product SecOps integration.
Explore serviceArcSight ESM to Threat Detection and Response modernization including content migration.
Explore serviceSOC program scoping for TDR alongside Splunk, Microsoft Sentinel, Sumo Logic, and Devo.
Explore serviceDetection-as-code, response automation, and cross-product SecOps integration.
Explore serviceLong-term run support including detection-content tuning, response-playbook maintenance, and SOC operating-model evolution.
Explore serviceDetection-as-code and response-playbook workshops for SOC analysts, detection engineers and SecOps architects.
Explore serviceDetection engineers and SOC analysts who know ArcSight content, working inside your team through the modernization.
Explore serviceOpenText TDR licensing
TDR pricing arrives with tenant setup, log onboarding, detection-content tuning, response-playbook design, and cross-product SecOps integration that turn 20 years of ArcSight content depth into a working SaaS SOC.
Merito point of view
Threat Detection and Response is exactly the right answer for some SOC modernization programs (those already running ArcSight ESM, those consolidating on the OpenText catalog, and those whose Splunk costs climb with log volume) and the wrong one for others (mature Splunk Cloud pipelines with no compelling reason to migrate). Its strength is the ArcSight content depth and the SaaS modernization path, not a generic SIEM contest with Splunk.
TDR suits programs modernizing off ArcSight ESM, programs already running OpenText Cybersecurity broadly, and programs whose Splunk costs have become hard to justify. Greenfield cloud-native SOCs with no OpenText footprint are usually better served by Splunk Cloud or Microsoft Sentinel, and scoping says so when that is the case.
Cross-product SecOps integration with NDR, UEBA, MITRE content, threat intelligence, and long-retention logging is the platform claim that pays back when the program runs the full OpenText SecOps line. Programs running TDR standalone get SIEM; programs running it inside the line get unified SOC operations.
What buyers usually underestimate
Related from Merito
Related solutions
Related services
Related products
Frequently Asked Questions
Consultation request
Share your current SIEM footprint, ArcSight modernization timeline if any, and SOC operating-model targets. A Merito OpenText specialist follows up within one business day.
ArcSight content
Inherits the ArcSight detection-content library. Programs do not start from scratch.
Cross-product SecOps
Native correlation across the OpenText SecOps line. Programs running the full line get unified SOC operations.
Next step
A Merito TDR engagement starts with detection-content tuning and cross-product SecOps integration. Generic SIEM migrations without the OpenText modernization driver rarely justify the disruption.