Comparison Overview

Goldman Sachs

VS

SBI Card

Goldman Sachs

200 West Street, New York, New York, US, 10282
Last Update: 2025-12-09
Between 800 and 849

We aspire to be the world’s most exceptional financial institution, united by our shared values of partnership, client service, integrity, and excellence. Operating at the center of capital markets, we act as one firm, mobilizing our people, capital, and ideas to deliver superior results across our clients’ most complex challenges. For 156 years, Goldman Sachs has delivered world-class execution on a global scale across our leading Global Banking & Markets and Asset & Wealth Management businesses. Apprenticeship is central to our culture, with hands-on coaching and access to leaders who bring decades of experience and expertise. With office locations around the world, we offer a broad range of career opportunities to those who insist on excellence and thrive on performance. Find our Social Media Disclosures here: gs.com/social-media-disclosures

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

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/goldman-sachs.jpeg
Goldman Sachs
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/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
Compliance Summary
Goldman Sachs
100%
Compliance Rate
0/4 Standards Verified
SBI Card
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for Goldman Sachs in 2025.

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for SBI Card in 2025.

Incident History — Goldman Sachs (X = Date, Y = Severity)

Goldman Sachs cyber incidents detection timeline including parent company and subsidiaries

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

SBI Card cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/goldman-sachs.jpeg
Goldman Sachs
Incidents

No Incident

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

No Incident

FAQ

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

Historically, SBI Card company has disclosed a higher number of cyber incidents compared to Goldman Sachs company.

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

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

Neither SBI Card company nor Goldman Sachs company has reported experiencing a data breach publicly.

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

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

Neither Goldman Sachs nor SBI Card holds any compliance certifications.

Neither company holds any compliance certifications.

Goldman Sachs company has more subsidiaries worldwide compared to SBI Card company.

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

Neither Goldman Sachs nor SBI Card holds SOC 2 Type 1 certification.

Neither Goldman Sachs nor SBI Card holds SOC 2 Type 2 certification.

Neither Goldman Sachs nor SBI Card holds ISO 27001 certification.

Neither Goldman Sachs nor SBI Card holds PCI DSS certification.

Neither Goldman Sachs nor SBI Card holds HIPAA certification.

Neither Goldman Sachs nor SBI Card holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

FreePBX Endpoint Manager is a module for managing telephony endpoints in FreePBX systems. Versions prior to 16.0.96 and 17.0.1 through 17.0.9 have a weak default password. By default, this is a 6 digit numeric value which can be brute forced. (This is the app_password parameter). Depending on local configuration, this password could be the extension, voicemail, user manager, DPMA or EPM phone admin password. This issue is fixed in versions 16.0.96 and 17.0.10.

Risk Information
cvss4
Base: 6.9
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/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
Description

Neuron is a PHP framework for creating and orchestrating AI Agents. In versions 2.8.11 and below, the MySQLWriteTool executes arbitrary SQL provided by the caller using PDO::prepare() + execute() without semantic restrictions. This is consistent with the name (“write tool”), but in an LLM/agent context it becomes a high-risk capability: prompt injection or indirect prompt manipulation can cause execution of destructive queries such as DROP TABLE, TRUNCATE, DELETE, ALTER, or privilege-related statements (subject to DB permissions). Deployments that expose an agent with MySQLWriteTool enabled to untrusted input and/or run the tool with a DB user that has broad privileges are impacted. This issue is fixed in version 2.8.12.

Risk Information
cvss3
Base: 9.4
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H
Description

Neuron is a PHP framework for creating and orchestrating AI Agents. Versions 2.8.11 and below use MySQLSelectTool, which is vulnerable to Read-Only Bypass. MySQLSelectTool is intended to be a read-only SQL tool (e.g., for LLM agent querying, however, validation based on the first keyword (e.g., SELECT) and a forbidden-keyword list does not block file-writing constructs such as INTO OUTFILE / INTO DUMPFILE. As a result, an attacker who can influence the tool input (e.g., via prompt injection through a public agent endpoint) may write arbitrary files to the DB server if the MySQL/MariaDB account has the FILE privilege and server configuration permits writes to a useful location (e.g., a web-accessible directory). This issue is fixed in version 2.8.12.

Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
Description

Okta Java Management SDK facilitates interactions with the Okta management API. In versions 11.0.0 through 20.0.0, race conditions may arise from concurrent requests using the ApiClient class. This could cause a status code or response header from one request’s response to influence another request’s response. This issue is fixed in version 20.0.1.

Risk Information
cvss3
Base: 8.4
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L
Description

The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. When using versions 4.11.0 through 4.11.2 and 4.12.0, simultaneous requests on the same client may result in improper lookups in the TokenRequestCache for the request results. This issue is fixed in versions 4.11.2 and 4.12.1.

Risk Information
cvss3
Base: 5.4
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N