Comparison Overview

Shriram Finance Limited

VS

Citi

Shriram Finance Limited

Wockhardt Towers, Level-3, West Wing, C-2, G-Block, Bandra-Kurla Complex, Bandra (East), Mumbai, IN, 400051
Last Update: 2025-11-27

Shriram Finance is the country’s biggest retail NBFC offering credit solutions for commercial vehicles, two-wheeler loans, car loans, home loans, gold loans, personal and small business loans. We are part of the 50-year-old Shriram Group, a financial conglomerate that has emerged as a trusted partner in creating transformative experiences and lasting impressions in customers’ lives. In November 2022, Shriram Group’s entities – Shriram Transport Finance Company Limited, Shriram City Union Finance Limited , and Shriram Capital Limited – merged to form Shriram Finance Limited . As on September 30, 2024, with a network of 3,149 branches and a workforce of more than 77,764, Shriram Finance has combined Assets Under Management (AUM) worth ₹243,042 crores.

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

Citi

388 Greenwich Street, New York, New York, US, 10013
Last Update: 2025-11-20
Between 800 and 849

Citi's mission is to serve as a trusted partner to our clients by responsibly providing financial services that enable growth and economic progress. Our core activities are safeguarding assets, lending money, making payments and accessing the capital markets on behalf of our clients. We have over 200 years of experience helping our clients meet the world's toughest challenges and embrace its greatest opportunities. We are Citi, the global bank – an institution connecting millions of people across hundreds of countries and cities. For information on Citi’s commitment to privacy, visit on.citi/privacy.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/shriramfinance.jpeg
Shriram Finance Limited
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/citi.jpeg
Citi
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
Shriram Finance Limited
100%
Compliance Rate
0/4 Standards Verified
Citi
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for Shriram Finance Limited in 2025.

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for Citi in 2025.

Incident History — Shriram Finance Limited (X = Date, Y = Severity)

Shriram Finance Limited cyber incidents detection timeline including parent company and subsidiaries

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

Citi cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/shriramfinance.jpeg
Shriram Finance Limited
Incidents

No Incident

https://images.rankiteo.com/companyimages/citi.jpeg
Citi
Incidents

Date Detected: 02/2022
Type:Cyber Attack
Attack Vector: Email
Motivation: Financial Gain
Blog: Blog

Date Detected: 3/2013
Type:Breach
Attack Vector: Accidental Exposure
Blog: Blog

FAQ

Citi company demonstrates a stronger AI Cybersecurity Score compared to Shriram Finance Limited company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Citi company has historically faced a number of disclosed cyber incidents, whereas Shriram Finance Limited company has not reported any.

In the current year, Citi company and Shriram Finance Limited company have not reported any cyber incidents.

Neither Citi company nor Shriram Finance Limited company has reported experiencing a ransomware attack publicly.

Citi company has disclosed at least one data breach, while Shriram Finance Limited company has not reported such incidents publicly.

Citi company has reported targeted cyberattacks, while Shriram Finance Limited company has not reported such incidents publicly.

Neither Shriram Finance Limited company nor Citi company has reported experiencing or disclosing vulnerabilities publicly.

Neither Shriram Finance Limited nor Citi holds any compliance certifications.

Neither company holds any compliance certifications.

Citi company has more subsidiaries worldwide compared to Shriram Finance Limited company.

Citi company employs more people globally than Shriram Finance Limited company, reflecting its scale as a Financial Services.

Neither Shriram Finance Limited nor Citi holds SOC 2 Type 1 certification.

Neither Shriram Finance Limited nor Citi holds SOC 2 Type 2 certification.

Neither Shriram Finance Limited nor Citi holds ISO 27001 certification.

Neither Shriram Finance Limited nor Citi holds PCI DSS certification.

Neither Shriram Finance Limited nor Citi holds HIPAA certification.

Neither Shriram Finance Limited nor Citi holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.

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

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.

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

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Integer Overflow vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 6.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/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

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, working with large buffers in Lua scripts can lead to a stack overflow. Users of Lua rules and output scripts may be affected when working with large buffers. This includes a rule passing a large buffer to a Lua script. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves disabling Lua rules and output scripts, or making sure limits, such as stream.depth.reassembly and HTTP response body limits (response-body-limit), are set to less than half the stack size.

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

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions from 8.0.0 to before 8.0.2, a NULL dereference can occur when the entropy keyword is used in conjunction with base64_data. This issue has been patched in version 8.0.2. A workaround involves disabling rules that use entropy in conjunction with base64_data.

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