Comparison Overview

Verizon Business

VS

UST

Verizon Business

1 Verizon Way, None, Basking Ridge, NJ, US, 07920-1097
Last Update: 2025-12-09
Between 750 and 799

You’re more than a business, agency or organization leader. We’re more than the usual network that provides reliable coverage. Together, we can empower you and your people.

NAICS: 5415
NAICS Definition: Computer Systems Design and Related Services
Employees: 16,452
Subsidiaries: 17
12-month incidents
0
Known data breaches
8
Attack type number
4

UST

5 Polaris Way, Aliso Viejo, CA, 92656, US
Last Update: 2025-12-09
Between 800 and 849

UST is a global digital transformation solutions provider. For more than 20 years, UST has worked side by side with the world’s best companies to make a real impact through transformation. Powered by technology, inspired by people and led by purpose, UST partners with their clients from design to operation. With deep domain expertise and a future-proof philosophy, UST embeds innovation and agility into their clients’ organizations. With over 30K+ employees in 30+ countries, UST builds for boundless impact—touching billions of lives in the process.

NAICS: 5415
NAICS Definition: Computer Systems Design and Related Services
Employees: 36,536
Subsidiaries: 6
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/verizonbusiness.jpeg
Verizon Business
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/ust-global.jpeg
UST
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
Verizon Business
100%
Compliance Rate
0/4 Standards Verified
UST
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs IT Services and IT Consulting Industry Average (This Year)

No incidents recorded for Verizon Business in 2025.

Incidents vs IT Services and IT Consulting Industry Average (This Year)

No incidents recorded for UST in 2025.

Incident History — Verizon Business (X = Date, Y = Severity)

Verizon Business cyber incidents detection timeline including parent company and subsidiaries

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

UST cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/verizonbusiness.jpeg
Verizon Business
Incidents

Date Detected: 2/2025
Type:Vulnerability
Attack Vector: Unsecured API
Blog: Blog

Date Detected: 10/2024
Type:Cyber Attack
Motivation: Influence Operations, Espionage
Blog: Blog

Date Detected: 6/2024
Type:Breach
Attack Vector: Network Penetration
Motivation: Espionage, Influence Operations
Blog: Blog
https://images.rankiteo.com/companyimages/ust-global.jpeg
UST
Incidents

No Incident

FAQ

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

Verizon Business company has historically faced a number of disclosed cyber incidents, whereas UST company has not reported any.

In the current year, Verizon Business company has reported more cyber incidents than UST company.

Neither UST company nor Verizon Business company has reported experiencing a ransomware attack publicly.

Verizon Business company has disclosed at least one data breach, while the other UST company has not reported such incidents publicly.

Verizon Business company has reported targeted cyberattacks, while UST company has not reported such incidents publicly.

Verizon Business company has disclosed at least one vulnerability, while UST company has not reported such incidents publicly.

Neither Verizon Business nor UST holds any compliance certifications.

Neither company holds any compliance certifications.

Verizon Business company has more subsidiaries worldwide compared to UST company.

UST company employs more people globally than Verizon Business company, reflecting its scale as a IT Services and IT Consulting.

Neither Verizon Business nor UST holds SOC 2 Type 1 certification.

Neither Verizon Business nor UST holds SOC 2 Type 2 certification.

Neither Verizon Business nor UST holds ISO 27001 certification.

Neither Verizon Business nor UST holds PCI DSS certification.

Neither Verizon Business nor UST holds HIPAA certification.

Neither Verizon Business nor UST 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