Comparison Overview

Upwork

VS

Thomson Reuters

Upwork

475 Brannan St, San Francisco, California, 94107, US
Last Update: 2025-11-20
Between 800 and 849

Upwork is the world’s work marketplace that connects businesses with independent talent from across the globe. We serve everyone from one-person startups to large, Fortune 100 enterprises with a powerful, trust-driven platform that enables companies and talent to work together in new ways that unlock their potential. Our talent community on Upwork encompasses more than 10,000 skills in categories including website & app development, creative & design, customer support, finance & accounting, consulting, and operations.

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

Thomson Reuters

19 Duncan Street , Toronto, ON, M5H 3G6, CA
Last Update: 2025-11-27
Between 750 and 799

Thomson Reuters is the world’s leading provider of news and information-based tools to professionals. Our worldwide network of journalists and specialist editors keep customers up to speed on global developments, with a particular focus on legal, regulatory and tax changes. Our customers operate in complex arenas that move society forward — tax, law, compliance, government, media. In a disruptive digital age, we help professionals reinvent themselves. Thomson Reuters shares are listed on the Toronto and New York Stock Exchanges (symbol: TRI).

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 35,141
Subsidiaries: 26
12-month incidents
0
Known data breaches
1
Attack type number
2

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/upwork.jpeg
Upwork
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/thomson-reuters.jpeg
Thomson Reuters
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
Upwork
100%
Compliance Rate
0/4 Standards Verified
Thomson Reuters
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for Upwork in 2025.

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for Thomson Reuters in 2025.

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

Upwork cyber incidents detection timeline including parent company and subsidiaries

Incident History — Thomson Reuters (X = Date, Y = Severity)

Thomson Reuters cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/upwork.jpeg
Upwork
Incidents

No Incident

https://images.rankiteo.com/companyimages/thomson-reuters.jpeg
Thomson Reuters
Incidents

Date Detected: 01/2024
Type:Cyber Attack
Attack Vector: Unspecified Infiltration
Motivation: Retaliation for a cyber attack by Russia against Kyivstar
Blog: Blog

Date Detected: 10/2022
Type:Breach
Attack Vector: Unsecured Database
Blog: Blog

FAQ

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

Thomson Reuters company has historically faced a number of disclosed cyber incidents, whereas Upwork company has not reported any.

In the current year, Thomson Reuters company and Upwork company have not reported any cyber incidents.

Neither Thomson Reuters company nor Upwork company has reported experiencing a ransomware attack publicly.

Thomson Reuters company has disclosed at least one data breach, while Upwork company has not reported such incidents publicly.

Thomson Reuters company has reported targeted cyberattacks, while Upwork company has not reported such incidents publicly.

Neither Upwork company nor Thomson Reuters company has reported experiencing or disclosing vulnerabilities publicly.

Neither Upwork nor Thomson Reuters holds any compliance certifications.

Neither company holds any compliance certifications.

Thomson Reuters company has more subsidiaries worldwide compared to Upwork company.

Upwork company employs more people globally than Thomson Reuters company, reflecting its scale as a Software Development.

Neither Upwork nor Thomson Reuters holds SOC 2 Type 1 certification.

Neither Upwork nor Thomson Reuters holds SOC 2 Type 2 certification.

Neither Upwork nor Thomson Reuters holds ISO 27001 certification.

Neither Upwork nor Thomson Reuters holds PCI DSS certification.

Neither Upwork nor Thomson Reuters holds HIPAA certification.

Neither Upwork nor Thomson Reuters 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