Comparison Overview

OpenText

VS

Sage

OpenText

275 Frank Tompa Drive, Waterloo, ON, CA, N2L 0A1
Last Update: 2025-11-27
Between 650 and 699

OpenText is a leading Cloud and AI company that provides organizations around the world with a comprehensive suite of Business AI, Business Clouds, and Business Technology. We help organizations grow, innovate, become more efficient and effective, and do so in a trusted and secure way—through Information Management. OpenText (NASDAQ/TSX: OTEX), founded in 1991 in Waterloo, has a rich history of helping customers manage their most important asset—information. Originating from a collaboration to digitize the Oxford English Dictionary, OpenText has grown into a global leader in information management. With over 120,000 enterprise customers across 180 countries, OpenText supports 98 of the top 100 global companies. A wide breadth of offerings uniquely positions OpenText to help customers unlock the value of that information using Al, cloud, and security innovations. At OpenText, our culture is at the heart of everything we do—and today, that includes being proudly AI-first. We’re creating a workplace where everyone can thrive, with artificial intelligence integrated into how we work, solve problems, and innovate together. By fostering a collaborative and inclusive environment, we empower digital knowledge workers and drive forward-thinking solutions that shape the future of information management. We believe our success comes from the strength of our team—talent that AI can’t replace—and we’re committed to attracting and supporting those who bring unique insight, adaptability, and creativity. Because at OpenText, people aren’t just our greatest asset—they’re the reason we shine in an AI-powered world. Join us at OpenText and become part of a team where your talents and ideas are truly valued.

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 22,020
Subsidiaries: 17
12-month incidents
1
Known data breaches
1
Attack type number
2

Sage

North Park, Newcastle upon Tyne, undefined, NE13 9AA, GB
Last Update: 2025-11-22
Between 750 and 799

At Sage, we knock down barriers with information, insights, and tools to help your business flow. We provide businesses with software and services that are simple and easy to use, as we work with you to give you that feeling of confidence. Customers trust our Payroll, HR, and Finance software to make business flow with ease. From our local network of experts to our ever-growing partnerships, we are on hand to give you all the insights you need to thrive. 💚

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 14,135
Subsidiaries: 4
12-month incidents
0
Known data breaches
2
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/opentext.jpeg
OpenText
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/sage-software.jpeg
Sage
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
OpenText
100%
Compliance Rate
0/4 Standards Verified
Sage
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Software Development Industry Average (This Year)

OpenText has 127.27% more incidents than the average of same-industry companies with at least one recorded incident.

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for Sage in 2025.

Incident History — OpenText (X = Date, Y = Severity)

OpenText cyber incidents detection timeline including parent company and subsidiaries

Incident History — Sage (X = Date, Y = Severity)

Sage cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/opentext.jpeg
OpenText
Incidents

Date Detected: 11/2025
Type:Ransomware
Attack Vector: AI-driven phishing, deepfake (voice/video spoofing), third-party service providers, software supply chain
Motivation: financial gain (ransom payments), data theft, disruption of operations
Blog: Blog

Date Detected: 06/2016
Type:Breach
Attack Vector: Compromised Credentials
Motivation: Data Theft
Blog: Blog
https://images.rankiteo.com/companyimages/sage-software.jpeg
Sage
Incidents

Date Detected: 8/2016
Type:Breach
Attack Vector: Unauthorized Access
Blog: Blog

Date Detected: 07/2016
Type:Breach
Attack Vector: Unsecured Databases
Blog: Blog

FAQ

Sage company demonstrates a stronger AI Cybersecurity Score compared to OpenText company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

OpenText and Sage have experienced a similar number of publicly disclosed cyber incidents.

In the current year, OpenText company has reported more cyber incidents than Sage company.

OpenText company has confirmed experiencing a ransomware attack, while Sage company has not reported such incidents publicly.

Both Sage company and OpenText company have disclosed experiencing at least one data breach.

Neither Sage company nor OpenText company has reported experiencing targeted cyberattacks publicly.

Neither OpenText company nor Sage company has reported experiencing or disclosing vulnerabilities publicly.

Neither OpenText nor Sage holds any compliance certifications.

Neither company holds any compliance certifications.

OpenText company has more subsidiaries worldwide compared to Sage company.

OpenText company employs more people globally than Sage company, reflecting its scale as a Software Development.

Neither OpenText nor Sage holds SOC 2 Type 1 certification.

Neither OpenText nor Sage holds SOC 2 Type 2 certification.

Neither OpenText nor Sage holds ISO 27001 certification.

Neither OpenText nor Sage holds PCI DSS certification.

Neither OpenText nor Sage holds HIPAA certification.

Neither OpenText nor Sage holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.

Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Integer Overflow vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 6.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, working with large buffers in Lua scripts can lead to a stack overflow. Users of Lua rules and output scripts may be affected when working with large buffers. This includes a rule passing a large buffer to a Lua script. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves disabling Lua rules and output scripts, or making sure limits, such as stream.depth.reassembly and HTTP response body limits (response-body-limit), are set to less than half the stack size.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Description

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions from 8.0.0 to before 8.0.2, a NULL dereference can occur when the entropy keyword is used in conjunction with base64_data. This issue has been patched in version 8.0.2. A workaround involves disabling rules that use entropy in conjunction with base64_data.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H