Comparison Overview

Transamerica

VS

BNY

Transamerica

Baltimore, Maryland, US, 21202
Last Update: 2026-01-16
View Profile
Between 700 and 749
http://www.transamerica.com

Longer lifespans are changing the way we exist. Instead of the traditional stages of learn, work, and retire, we now have the potential for a more fulfilling, multi-stage life. With this opportunity comes the need to plan for it. We enable financial professionals, brokers, agents, advisors, and employers to energize clients and employees to seize the possibilities longevity brings. So, no matter where someone is on their journey, we can help them pursue the freedom to live the life they want. Transamerica. Live your best life. Securities distributed by Transamerica Capital, Inc. Social terms: https://www.transamerica.com/social-media-guidelines

NAICS: 52
NAICS Definition: Finance and Insurance
Employees: 15,465
Subsidiaries: 23
12-month incidents
0
Known data breaches
3
Attack type number
2
View Profile

BNY

240 Greenwich St, New York, NY, US, 10286
Last Update: 2026-01-19
Between 800 and 849
https://www.bny.com

For more than 240 years BNY has partnered alongside clients, using its expertise and platforms to help them operate more efficiently and accelerate growth. Today BNY serves over 90% of Fortune 100 companies and nearly all the top 100 banks globally. BNY supports governments in funding local projects and works with over 90% of the top 100 pension plans to safeguard investments for millions of individuals. As of December 31, 2025, BNY oversees $59.3 trillion in assets under custody and/or administration and $2.2 trillion in assets under management. Follow BNY on Instagram & X: @BNYglobal

NAICS: 52
NAICS Definition: Finance and Insurance
Employees: 54,053
Subsidiaries: 10
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/transamerica.jpeg
Transamerica
—
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/bnyglobal.jpeg
BNY
—
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
Transamerica
100%
Compliance Rate
0/4 Standards Verified
BNY
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for Transamerica in 2026.

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for BNY in 2026.

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

Transamerica cyber incidents detection timeline including parent company and subsidiaries

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

BNY cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/transamerica.jpeg
Transamerica
Incidents

Date Detected: 5/2023
Type:Vulnerability
Attack Vector: Exploitation of Vulnerability
Blog: Blog

Date Detected: 6/2021
Type:Breach
Attack Vector: Unauthorized Access
Blog: Blog

Date Detected: 8/2018
Type:Breach
Attack Vector: Email
Blog: Blog
https://images.rankiteo.com/companyimages/bnyglobal.jpeg
BNY
Incidents

No Incident

FAQ

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

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

In the current year, BNY company and Transamerica company have not reported any cyber incidents.

Neither BNY company nor Transamerica company has reported experiencing a ransomware attack publicly.

Transamerica company has disclosed at least one data breach, while the other BNY company has not reported such incidents publicly.

Neither BNY company nor Transamerica company has reported experiencing targeted cyberattacks publicly.

Transamerica company has disclosed at least one vulnerability, while BNY company has not reported such incidents publicly.

Neither Transamerica nor BNY holds any compliance certifications.

Neither company holds any compliance certifications.

Transamerica company has more subsidiaries worldwide compared to BNY company.

BNY company employs more people globally than Transamerica company, reflecting its scale as a Financial Services.

Neither Transamerica nor BNY holds SOC 2 Type 1 certification.

Neither Transamerica nor BNY holds SOC 2 Type 2 certification.

Neither Transamerica nor BNY holds ISO 27001 certification.

Neither Transamerica nor BNY holds PCI DSS certification.

Neither Transamerica nor BNY holds HIPAA certification.

Neither Transamerica nor BNY holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

SummaryA command injection vulnerability (CWE-78) has been found to exist in the `wrangler pages deploy` command. The issue occurs because the `--commit-hash` parameter is passed directly to a shell command without proper validation or sanitization, allowing an attacker with control of `--commit-hash` to execute arbitrary commands on the system running Wrangler. Root causeThe commitHash variable, derived from user input via the --commit-hash CLI argument, is interpolated directly into a shell command using template literals (e.g.,  execSync(`git show -s --format=%B ${commitHash}`)). Shell metacharacters are interpreted by the shell, enabling command execution. ImpactThis vulnerability is generally hard to exploit, as it requires --commit-hash to be attacker controlled. The vulnerability primarily affects CI/CD environments where `wrangler pages deploy` is used in automated pipelines and the --commit-hash parameter is populated from external, potentially untrusted sources. An attacker could exploit this to: * Run any shell command. * Exfiltrate environment variables. * Compromise the CI runner to install backdoors or modify build artifacts. Credits Disclosed responsibly by kny4hacker. Mitigation * Wrangler v4 users are requested to upgrade to Wrangler v4.59.1 or higher. * Wrangler v3 users are requested to upgrade to Wrangler v3.114.17 or higher. * Users on Wrangler v2 (EOL) should upgrade to a supported major version.

Published
Date
2026-01-20
Updated
Date
2026-01-20
Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/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
References
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Published
Date
2026-01-20
Updated
Date
2026-01-20
Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
References
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle VM VirtualBox accessible data as well as unauthorized access to critical data or complete access to all Oracle VM VirtualBox accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L).

Published
Date
2026-01-20
Updated
Date
2026-01-20
Risk Information
cvss3
Base: 8.1
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L
References
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Published
Date
2026-01-20
Updated
Date
2026-01-20
Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
References
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Published
Date
2026-01-20
Updated
Date
2026-01-20
Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
References