Comparison Overview

Paytm

VS

Discover

Paytm

undefined, Noida, Uttar Pradesh, 201301, IN
Last Update: 2025-11-20
Between 800 and 849

Paytm started the Digital Revolution in India. And we went on to become India’s leading Payments App. Today, more than 20 Million merchants & businesses are powered by Paytm to Accept Payments digitally. This is because more than 300 million Indians use Paytm to Pay at their stores. And that’s not all, Paytm App is used to Pay bills, do Recharges, Send money to friends & family, Book movies & travel tickets. With innovations to Financial services & products in pipeline, this is but one of the milestones achieved towards our mission – to bring 500 million unserved and underserved Indians to the mainstream economy.

NAICS: 52
NAICS Definition:
Employees: 24,919
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Discover

2500 Lake Cook Road, None, Riverwoods, IL, US, 60015
Last Update: 2025-11-27
Between 650 and 699

Discover® is now part of Capital One. Together, we’ll continue to deliver exceptional financial products and experiences, drive innovation, and serve customers. Find the latest updates at https://capitalonediscover.com. Discover is one of the most recognized brands in the U.S. with the Discover® card, America's cash rewards pioneer, and offers personal loans, home loans, checking and savings accounts and certificates of deposit. The Discover Global Network® is comprised of Discover Network, with millions of merchants and cash access locations; PULSE®, one of the nation's leading ATM/debit networks; and Diners Club International®, a global payments network with acceptance around the world.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/paytm-mobile-solutions-pvt-ltd-.jpeg
Paytm
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/discover-financial-services.jpeg
Discover
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
Paytm
100%
Compliance Rate
0/4 Standards Verified
Discover
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for Paytm in 2025.

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for Discover in 2025.

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

Paytm cyber incidents detection timeline including parent company and subsidiaries

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

Discover cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/paytm-mobile-solutions-pvt-ltd-.jpeg
Paytm
Incidents

No Incident

https://images.rankiteo.com/companyimages/discover-financial-services.jpeg
Discover
Incidents

Date Detected: 9/2020
Type:Breach
Attack Vector: Inadvertent Disclosure
Blog: Blog

Date Detected: 8/2018
Type:Breach
Blog: Blog

Date Detected: 1/2018
Type:Breach
Blog: Blog

FAQ

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

Discover company has historically faced a number of disclosed cyber incidents, whereas Paytm company has not reported any.

In the current year, Discover company and Paytm company have not reported any cyber incidents.

Neither Discover company nor Paytm company has reported experiencing a ransomware attack publicly.

Discover company has disclosed at least one data breach, while Paytm company has not reported such incidents publicly.

Discover company has reported targeted cyberattacks, while Paytm company has not reported such incidents publicly.

Neither Paytm company nor Discover company has reported experiencing or disclosing vulnerabilities publicly.

Neither Paytm nor Discover holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Paytm company nor Discover company has publicly disclosed detailed information about the number of their subsidiaries.

Paytm company employs more people globally than Discover company, reflecting its scale as a Financial Services.

Neither Paytm nor Discover holds SOC 2 Type 1 certification.

Neither Paytm nor Discover holds SOC 2 Type 2 certification.

Neither Paytm nor Discover holds ISO 27001 certification.

Neither Paytm nor Discover holds PCI DSS certification.

Neither Paytm nor Discover holds HIPAA certification.

Neither Paytm nor Discover 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