Comparison Overview

TOTVS

VS

Sage

TOTVS

Av Braz Leme, 1000, Sao Paulo, SP, BR, 02511-900
Last Update: 2025-12-09
Between 750 and 799

Olá, somos a TOTVS! A maior empresa de tecnologia do Brasil. 🤓 Líder absoluta em sistemas e plataformas para empresas, a TOTVS possui mais de 70 mil clientes. Indo muito além do ERP, oferece tecnologia completa para digitalização dos negócios por meio de 3 unidades de negócio: - Gestão: ERPs, soluções cross e sistemas especializados visando garantir mais produtividade, eficiência e governança para os negócios; 💻 - Techfin: ERP Banking que oferece soluções de crédito B2B e pagamento, integrados a sistemas de gestão; 💸 - RD Station: Ferramentas digitais de marketing, vendas e relacionamento, para empresas de todos os portes e segmentos. 🚀 Nos últimos 5 anos, a companhia investiu R$3 bilhões em pesquisa e desenvolvimento para atender de maneira cada vez mais especializada empresas de 12 segmentos da economia, tornando-se um trusted advisor de seus clientes. A TOTVS é uma potência tecnológica que apoia a evolução de empresas de norte a sul do país. O Brasil, que faz, faz com TOTVS.

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 16,304
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Sage

North Park, Newcastle upon Tyne, undefined, NE13 9AA, GB
Last Update: 2025-12-09
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/totvs.jpeg
TOTVS
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
TOTVS
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)

No incidents recorded for TOTVS in 2025.

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for Sage in 2025.

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

TOTVS 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/totvs.jpeg
TOTVS
Incidents

No Incident

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 TOTVS company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Sage company has historically faced a number of disclosed cyber incidents, whereas TOTVS company has not reported any.

In the current year, Sage company and TOTVS company have not reported any cyber incidents.

Neither Sage company nor TOTVS company has reported experiencing a ransomware attack publicly.

Sage company has disclosed at least one data breach, while TOTVS company has not reported such incidents publicly.

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

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

Neither TOTVS nor Sage holds any compliance certifications.

Neither company holds any compliance certifications.

Sage company has more subsidiaries worldwide compared to TOTVS company.

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

Neither TOTVS nor Sage holds SOC 2 Type 1 certification.

Neither TOTVS nor Sage holds SOC 2 Type 2 certification.

Neither TOTVS nor Sage holds ISO 27001 certification.

Neither TOTVS nor Sage holds PCI DSS certification.

Neither TOTVS nor Sage holds HIPAA certification.

Neither TOTVS nor Sage holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

NXLog Agent before 6.11 can load a file specified by the OPENSSL_CONF environment variable.

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

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

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

A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. You should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."

Risk Information
cvss2
Base: 5.0
Severity: LOW
AV:N/AC:L/Au:N/C:N/I:P/A:N
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/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

MJML through 4.18.0 allows mj-include directory traversal to test file existence and (in the type="css" case) read files. NOTE: this issue exists because of an incomplete fix for CVE-2020-12827.

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

A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).

Risk Information
cvss3
Base: 5.8
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N