Comparison Overview

SBI Card

VS

MassMutual

SBI Card

Infinity Tower, DLF City Phase 2, Gurgaon, Haryana, 122002, IN
Last Update: 2025-12-09
Between 750 and 799

SBI Card was launched in 1998 with the State Bank of India, India's largest bank, as the majority stakeholder. In March 2020, SBI Card was listed on BSE and NSE. Today, SBI Card is India’s largest pure-play credit card issuer with over 19.5 million cards in force, as of September 2024. Its wide array of products and services caters to a diverse range of customer segments across India, right from new-to-credit to super premium. The SBI Card brand is based on the value proposition of 'Make Life Simple'. The proposition manifests in SBI Card’s continuous efforts to simplify the lives of its customers, employees and other key stakeholders. Customer-centricity, supported by the values of trust and transparency, is core to SBI Card’s ethos.

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

MassMutual

1295 State Street, None, Springfield, Massachusetts, US, 01111
Last Update: 2025-12-09
Between 600 and 649

Living mutual has always been at the core of our human existence, and it's the principle that's guided us since our founding in 1851. It's not a concept we invented, but one we champion for the simple reason that people take it for granted today. While the world would have us strive for independence, the truth is when we depend on one another, we aren't just more secure - life is happier and more fulfilling. So as we celebrate our new identity, we're reminding everyone that who we are stays the same. Learn more at: www.MassMutual.com Disclosures about MassMutual’s LinkedIn Company Page and other social media sites are located at: https://www.massmutual.com/social-media-guidelines. CRN201905-212768

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/sbi-card.jpeg
SBI Card
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/massmutual-financial-group.jpeg
MassMutual
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
SBI Card
100%
Compliance Rate
0/4 Standards Verified
MassMutual
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for SBI Card in 2025.

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for MassMutual in 2025.

Incident History — SBI Card (X = Date, Y = Severity)

SBI Card cyber incidents detection timeline including parent company and subsidiaries

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

MassMutual cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/sbi-card.jpeg
SBI Card
Incidents

No Incident

https://images.rankiteo.com/companyimages/massmutual-financial-group.jpeg
MassMutual
Incidents

Date Detected: 4/2024
Type:Breach
Blog: Blog

Date Detected: 5/2023
Type:Breach
Attack Vector: Zero-day vulnerability exploitation
Blog: Blog

Date Detected: 2/2023
Type:Breach
Attack Vector: Unauthorized Access
Blog: Blog

FAQ

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

MassMutual company has historically faced a number of disclosed cyber incidents, whereas SBI Card company has not reported any.

In the current year, MassMutual company and SBI Card company have not reported any cyber incidents.

Neither MassMutual company nor SBI Card company has reported experiencing a ransomware attack publicly.

MassMutual company has disclosed at least one data breach, while SBI Card company has not reported such incidents publicly.

Neither MassMutual company nor SBI Card company has reported experiencing targeted cyberattacks publicly.

Neither SBI Card company nor MassMutual company has reported experiencing or disclosing vulnerabilities publicly.

Neither SBI Card nor MassMutual holds any compliance certifications.

Neither company holds any compliance certifications.

MassMutual company has more subsidiaries worldwide compared to SBI Card company.

SBI Card company employs more people globally than MassMutual company, reflecting its scale as a Financial Services.

Neither SBI Card nor MassMutual holds SOC 2 Type 1 certification.

Neither SBI Card nor MassMutual holds SOC 2 Type 2 certification.

Neither SBI Card nor MassMutual holds ISO 27001 certification.

Neither SBI Card nor MassMutual holds PCI DSS certification.

Neither SBI Card nor MassMutual holds HIPAA certification.

Neither SBI Card nor MassMutual 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