Comparison Overview

Capital One

VS

Nomura

Capital One

1680 Capital One Drive, McLean, Va, US, 22102
Last Update: 2025-12-09
Between 600 and 649

At Capital One, we're making things better for our customers and associates through innovation and collaboration. We were founded on the belief that everyone deserves financial freedom—and are dedicated to a world where all have equal opportunity to prosper. Banking is in our DNA, but we are so much more than a bank. We always think about what’s next—and how we can bring our customers the tools needed to improve their financial lives. Your ideas, experiences and skills will help make banking better. You’ll be part of a supportive culture while earning amazing benefits. That’s life at Capital One. Capital One is an equal opportunity employer (EOE, including disability/vet) committed to non-discrimination in compliance with applicable federal, state, and local laws. View our Social Media Community Guidelines https://www.capitalone.com/digital/social-media/

NAICS: 52
NAICS Definition: Finance and Insurance
Employees: 81,373
Subsidiaries: 4
12-month incidents
1
Known data breaches
11
Attack type number
1

Nomura

1-9-1 Nihonbashi, Tokyo, undefined, 103-8645, JP
Last Update: 2025-12-09
Between 750 and 799

Nomura is a global financial services group with an integrated network spanning approximately 30 countries and regions. By connecting markets East & West, Nomura services the needs of individuals, institutions, corporates and governments through its three business divisions: Wealth Management, Investment Management, and Wholesale (Global Markets and Investment Banking). Founded in 1925, the firm is built on a tradition of disciplined entrepreneurship, serving clients with creative solutions and considered thought leadership.

NAICS: 52
NAICS Definition: Finance and Insurance
Employees: 15,162
Subsidiaries: 3
12-month incidents
0
Known data breaches
0
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/capital-one.jpeg
Capital One
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/nomura.jpeg
Nomura
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
Capital One
100%
Compliance Rate
0/4 Standards Verified
Nomura
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Financial Services Industry Average (This Year)

Capital One has 20.48% more incidents than the average of same-industry companies with at least one recorded incident.

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for Nomura in 2025.

Incident History — Capital One (X = Date, Y = Severity)

Capital One cyber incidents detection timeline including parent company and subsidiaries

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

Nomura cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/capital-one.jpeg
Capital One
Incidents

Date Detected: 5/2025
Type:Breach
Attack Vector: Misconfigured Firewall
Motivation: Data Theft
Blog: Blog

Date Detected: 2/2023
Type:Breach
Blog: Blog

Date Detected: 8/2022
Type:Breach
Attack Vector: Insider Wrongdoing
Blog: Blog
https://images.rankiteo.com/companyimages/nomura.jpeg
Nomura
Incidents

Date Detected: 05/2020
Type:Data Leak
Attack Vector: Insider Threat
Blog: Blog

FAQ

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

Capital One company has faced a higher number of disclosed cyber incidents historically compared to Nomura company.

In the current year, Capital One company has reported more cyber incidents than Nomura company.

Neither Nomura company nor Capital One company has reported experiencing a ransomware attack publicly.

Capital One company has disclosed at least one data breach, while the other Nomura company has not reported such incidents publicly.

Neither Nomura company nor Capital One company has reported experiencing targeted cyberattacks publicly.

Neither Capital One company nor Nomura company has reported experiencing or disclosing vulnerabilities publicly.

Neither Capital One nor Nomura holds any compliance certifications.

Neither company holds any compliance certifications.

Capital One company has more subsidiaries worldwide compared to Nomura company.

Capital One company employs more people globally than Nomura company, reflecting its scale as a Financial Services.

Neither Capital One nor Nomura holds SOC 2 Type 1 certification.

Neither Capital One nor Nomura holds SOC 2 Type 2 certification.

Neither Capital One nor Nomura holds ISO 27001 certification.

Neither Capital One nor Nomura holds PCI DSS certification.

Neither Capital One nor Nomura holds HIPAA certification.

Neither Capital One nor Nomura 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