Comparison Overview

Sumitomo Mitsui Banking Corporation – SMBC Group

VS

Navy Federal Credit Union

Sumitomo Mitsui Banking Corporation – SMBC Group

1丁目 1-2, Marunouchi Chiyoda-Ku,, Tokyo, undefined, undefined, JP
Last Update: 2025-12-09

SMBC Group is a top-tier global financial group. Headquartered in Tokyo and with a 400-year history, SMBC Group offers a diverse range of financial services, including banking, leasing, securities, credit cards, and consumer finance. The Group has more than 150 offices and 86,000 employees worldwide in nearly 40 countries. Sumitomo Mitsui Financial Group, Inc. (SMFG) is the holding company of SMBC Group, one of the three largest banking groups in Japan. SMFG's shares trade on the Tokyo and Nagoya stock exchanges, and its ADRs trade on the New York Stock Exchange (NYSE: SMFG). Americas: https://www.smbcgroup.com/ EMEA: https://www.smbcgroup.com/emea/ APAC: https://www.smbc.co.jp/asia/ Tokyo: https://www.smfg.co.jp/english/

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

Navy Federal Credit Union

820 Follin Lane SE, None, Vienna, VA, US, 22180
Last Update: 2025-12-09
Between 700 and 749

Navy Federal is the world’s largest credit union, with more than 14 million members, $180 billion+ in assets and 24,000+ employees. Throughout campuses in Vienna, VA Pensacola, FL and Winchester, VA, as well as more than 360 branches, we serve the Armed Forces, Department of Defense, Veterans and their families with world-class financial products and services. Navy Federal provides much more than a job. We provide a meaningful career experience, including a culture that is energized, engaged and committed; and fierce appreciation for our teams, who are rewarded with highly competitive pay and generous benefits and perks. Our approach to careers is simple yet powerful: Make our mission your passion. Federally insured by NCUA. Equal opportunity employer. Android™ is a trademark of Google, Inc. iPhone® is a registered trademark of Apple, Inc. iPad® is a registered trademark of Apple, Inc. App Store(SM) is a service mark of Apple, Inc. Message and data rates may apply. FORTUNE and 100 Best Companies to Work For are registered trademarks of Time Inc., and are used under license. FORTUNE and Time Inc., are not affiliated with, and do not endorse products or services of, Navy Federal Credit Union. For more info, visit navyfederal.org. Images used for representational purposes only; do not imply government endorsement. Equal Housing Lender Equal Opportunity Employer, including disability/vets

NAICS: 52
NAICS Definition: Finance and Insurance
Employees: 23,853
Subsidiaries: 1
12-month incidents
1
Known data breaches
1
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/sumitomo-mitsui-banking-corporation.jpeg
Sumitomo Mitsui Banking Corporation – SMBC Group
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
Sumitomo Mitsui Banking Corporation – SMBC Group
100%
Compliance Rate
0/4 Standards Verified
Navy Federal Credit Union
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for Sumitomo Mitsui Banking Corporation – SMBC Group in 2025.

Incidents vs Financial Services Industry Average (This Year)

Navy Federal Credit Union has 20.48% more incidents than the average of same-industry companies with at least one recorded incident.

Incident History — Sumitomo Mitsui Banking Corporation – SMBC Group (X = Date, Y = Severity)

Sumitomo Mitsui Banking Corporation – SMBC Group cyber incidents detection timeline including parent company and subsidiaries

Incident History — Navy Federal Credit Union (X = Date, Y = Severity)

Navy Federal Credit Union cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/sumitomo-mitsui-banking-corporation.jpeg
Sumitomo Mitsui Banking Corporation – SMBC Group
Incidents

No Incident

https://images.rankiteo.com/companyimages/navy-federal-credit-union.jpeg
Navy Federal Credit Union
Incidents

FAQ

Sumitomo Mitsui Banking Corporation – SMBC Group company demonstrates a stronger AI Cybersecurity Score compared to Navy Federal Credit Union company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Navy Federal Credit Union company has historically faced a number of disclosed cyber incidents, whereas Sumitomo Mitsui Banking Corporation – SMBC Group company has not reported any.

In the current year, Navy Federal Credit Union company has reported more cyber incidents than Sumitomo Mitsui Banking Corporation – SMBC Group company.

Neither Navy Federal Credit Union company nor Sumitomo Mitsui Banking Corporation – SMBC Group company has reported experiencing a ransomware attack publicly.

Navy Federal Credit Union company has disclosed at least one data breach, while Sumitomo Mitsui Banking Corporation – SMBC Group company has not reported such incidents publicly.

Neither Navy Federal Credit Union company nor Sumitomo Mitsui Banking Corporation – SMBC Group company has reported experiencing targeted cyberattacks publicly.

Neither Sumitomo Mitsui Banking Corporation – SMBC Group company nor Navy Federal Credit Union company has reported experiencing or disclosing vulnerabilities publicly.

Neither Sumitomo Mitsui Banking Corporation – SMBC Group nor Navy Federal Credit Union holds any compliance certifications.

Neither company holds any compliance certifications.

Sumitomo Mitsui Banking Corporation – SMBC Group company has more subsidiaries worldwide compared to Navy Federal Credit Union company.

Navy Federal Credit Union company employs more people globally than Sumitomo Mitsui Banking Corporation – SMBC Group company, reflecting its scale as a Financial Services.

Neither Sumitomo Mitsui Banking Corporation – SMBC Group nor Navy Federal Credit Union holds SOC 2 Type 1 certification.

Neither Sumitomo Mitsui Banking Corporation – SMBC Group nor Navy Federal Credit Union holds SOC 2 Type 2 certification.

Neither Sumitomo Mitsui Banking Corporation – SMBC Group nor Navy Federal Credit Union holds ISO 27001 certification.

Neither Sumitomo Mitsui Banking Corporation – SMBC Group nor Navy Federal Credit Union holds PCI DSS certification.

Neither Sumitomo Mitsui Banking Corporation – SMBC Group nor Navy Federal Credit Union holds HIPAA certification.

Neither Sumitomo Mitsui Banking Corporation – SMBC Group nor Navy Federal Credit Union 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