ITC Secure vs OpenText
ITC Secure is a Microsoft-ecosystem that works with your existing tools. OpenText is a Pure-play MDR that works with your existing tools. ITC Secure targets Mid-market and Enterprise organizations; OpenText serves SMB and Mid-market. ITC Secure includes 3 attack surfaces in base pricing (Endpoint, SaaS, Identity), compared to 4 for OpenText (Endpoint, Cloud, SaaS, Network).
Buyer brief
ITC Secure is a Microsoft-ecosystem that works with your existing tools. OpenText is a Pure-play MDR that works with your existing tools. ITC Secure targets Mid-market and Enterprise organizations; OpenText serves SMB and Mid-market. ITC Secure includes 3 attack surfaces in base pricing (Endpoint, SaaS, Identity), compared to 4 for OpenText (Endpoint, Cloud, SaaS, Network).
ITC Secure (Microsoft-ecosystem) and OpenText (Pure-play MDR) serve different buyer profiles. Your decision depends on whether you prioritize ITC Secure's itc secure fits buyers that want microsoft-centered mxdr with pulse portal visibility, service re... or OpenText's sensible fit for smaller it teams that want opentext's threat intelligence and a 24/7 soc layered....
At a glance
| FIELD |  |  |
|---|---|---|
| Best fit | Microsoft-centered buyers that want a verified managed XDR provider rather than a pure-play MDR platform | SMB and lower mid-market organizations that want a SOC layer over their existing endpoint stack |
| Price | Custom quote | Custom quote |
| Response authority | 0/6 actions · Configurable | 1/6 actions · Approval required |
| Stack | Works with existing stack | Works with existing stack |
| Data access | Dashboards | Dashboards |
| Warranty | None listed | None listed |
- Best fit
- Microsoft-centered buyers that want a verified managed XDR provider rather than a pure-play MDR platform
- Price
- Custom quote
- Response authority
- 0/6 actions · Configurable
- Stack
- Works with existing stack
- Data access
- Dashboards
- Warranty
- None listed
- Best fit
- SMB and lower mid-market organizations that want a SOC layer over their existing endpoint stack
- Price
- Custom quote
- Response authority
- 1/6 actions · Approval required
- Stack
- Works with existing stack
- Data access
- Dashboards
- Warranty
- None listed
Detailed comparison
| FIELD | ITC SecureTECH-AGNOSTIC | OpenTextTECH-AGNOSTIC |
|---|---|---|
| Fit | ||
| Target size | Mid-market, Enterprise | SMB, Mid-market |
| Sentiment | Mixed | Mixed |
| Your stack | ||
| Approach | Works with your tools | Works with your tools |
| EDR integrations | Microsoft Defender | CrowdStrikeSentinelOneSophosCarbon BlackBitdefender Microsoft Defender |
| SIEM integrations | Microsoft Sentinel | Splunk Microsoft Sentinel |
| Coverage | EPEndpoint: CoveredCloudCloud: LimitedIDIdentity: CoveredSaaSSaaS: CoveredNetNetwork: LimitedOTOT/IoT: Limited | EPEndpoint: CoveredCloudCloud: CoveredIDIdentity: LimitedSaaSSaaS: CoveredNetNetwork: CoveredOTOT/IoT: Not covered |
| Response | ||
| Response type | Active Remediation | Guided Response |
| Approval policy | Configurable | Approval Required |
| Response actions | Alert and notify only | Custom playbooks |
| IR included | Separate | Separate |
| Cost | ||
| Price range | Not published | Not published |
| Minimum seats | None | None |
| Breach warranty | – | – |
| More details | ||
| Requires own agent | No | No |
| Endpoints | ✓ Included | ✓ Included |
| Cloud workloads | ~ Limited | ✓ Included |
| Identity | ✓ Included | ~ Limited |
| SaaS apps | ✓ Included | ✓ Included |
| Network | ~ Limited | ✓ Included |
| OT/ICS | ~ Limited | Not offered |
| Threat hunting | ✓ Included | ✓ Included |
| Response SLA | Not disclosed | Not disclosed |
| 24/7 coverage | ✓ | ✓ |
| Pricing model | Custom quote. ITC Secure does not publish MXDR powered by Pulse package pricing. | Custom quote, not published. Sold direct and through OpenText partner channel. |
| Hidden cost warnings | Public pages do not publish MXDR pricing, contract minimums or service-credit language.. The service is Microsoft-centric, so Microsoft licensing, tenant readiness and log ingestion should be priced before comparison.. ITC Secure publishes broad MXDR components, including endpoint, identity, Office 365, cloud apps, storage, vulnerability management and OT. Buyers should confirm which components are included in their quote.. Public pages do not define default response authority, so containment permissions and approval rules should be written into the contract.. Incident response is listed as a separate service, so buyers should confirm what is included in MXDR versus a separate incident-response engagement. | Co-managed model means the customer's team still does the actual containment work. No published SLA, contractual response commitments must be negotiated. Headline detection metrics come from a 2021 launch announcement and have not been independently verified |
| Data portability | Partial | Partial |
| Contract terms | Custom, MXDR powered by Pulse, Managed services, Incident Response | Annual |
| Channels | PortalEmailPhone | EmailPortalPhone |
| Data access | Dashboards | Dashboards |
| Dedicated analyst | – | – |
| SOC regions | North America | |
| Onboarding | Not published. ITC Secure publishes security engineering and SOC onboarding as a build-and-deploy service, but no standard MXDR implementation duration was found. | Not published |
| Industry focus | Not published | SMBHealthcareFinancial ServicesPublic Sector |
| MTTD | Not published | Less than 30 minutes (vendor-published, 2021 launch claim) |
| MTTR | Not published | Not published |
| Community view | No meaningful MDR-specific buyer-review signal was found in major English-language review communities during this pass. The public buyer case rests on ITC Secure's Microsoft focus, Microsoft Verified Managed XDR status, Pulse portal, long managed-service history and broad MXDR service components. Buyers should validate pricing, response authority, SOC operating model and exact component inclusion directly. | Public review coverage of OpenText Core MDR is thin. Capterra lists the product with zero reviews, and there is no Gartner Peer Insights MDR profile or G2 page with a meaningful review base. Practitioner discussion mostly references the broader OpenText Cybersecurity portfolio and the Webroot heritage rather than the MDR service itself. |
| Compliance | ISO 27001Cyber Essentials PlusISO/IEC 20000-1 | Not published |
| Certifications | Microsoft Verified Managed XDRMicrosoft Solutions Partner in SecurityMicrosoft Solutions Partner in Modern WorkMicrosoft Solutions Partner in Infrastructure AzureMicrosoft Intelligent Security AssociationCyber Essentials PlusISO/IEC 20000-1ISO/IEC 27001Great Place to Work Certification | Not published |
| Founded | – | 1991 |
| Data retention | Not published. ITC Secure says Pulse provides visibility into customer security posture, activities, incident trends, Microsoft license consumption and service metrics. No standard public MXDR log-retention period or data-residency term was found. | Not published |
| API available | – | ✓ |
| Website | Visit → | Visit → |
FAQ
What is the main difference between ITC Secure and OpenText?
ITC Secure is a Microsoft-ecosystem that is technology-agnostic (works with your existing tools). OpenText is a Pure-play MDR that is technology-agnostic (works with your existing tools). ITC Secure covers 3 attack surfaces in base pricing vs. 4 for OpenText.
How do ITC Secure and OpenText differ in response capabilities?
ITC Secure supports 0 autonomous actions (none) and approval is configurable. OpenText supports 1 autonomous actions (custom playbooks) and requires approval before acting.
How does ITC Secure pricing compare to OpenText?
ITC Secure pricing: Not published. OpenText pricing: Not published. Watch for with ITC Secure: Public pages do not publish MXDR pricing, contract minimums or service-credit language.; The service is Microsoft-centric, so Microsoft licensing, tenant readiness and log ingestion should be priced before comparison.. Watch for with OpenText: Co-managed model means the customer's team still does the actual containment work; No published SLA, contractual response commitments must be negotiated.
Should I choose ITC Secure or OpenText?
Choose ITC Secure if: microsoft-centered buyers that want a verified managed XDR provider rather than a pure-play MDR platform. Choose OpenText if: sMB and lower mid-market organizations that want a SOC layer over their existing endpoint stack. ITC Secure is not ideal for buyers that need public MDR pricing before sales. OpenText is not ideal for buyers who need analysts to isolate endpoints or kill processes without customer approval.
Daylight Security
AI-native MDR for buyers comparing active remediation across endpoint, cloud, identity, and SaaS. Daylight works with existing EDR/SIEM stacks and uses ChatOps-native collaboration, so it can be a useful third reference point in this comparison.