Comparison Overview

JCPenney

VS

Walmart

JCPenney

6502 Legacy Drive, Plano, Texas, 75024, US
Last Update: 2025-11-21
Between 800 and 849

As we reinvent ourselves to fit the diversity of America, we are looking for motivated, talented people who can emerge as Warriors in our organization. JCPenney offers an inclusive environment and culture where you can find and define yourself - your style, your purpose and your career. We know success is built from the inside out, and our associates are the heartbeat of our Company! JCPenney is now part of Catalyst Brands.

NAICS: 43
NAICS Definition: Retail Trade
Employees: 39,384
Subsidiaries: 7
12-month incidents
0
Known data breaches
1
Attack type number
2

Walmart

702 SW 8th St, Bentonville, Arkansas, US, 72712
Last Update: 2025-11-27
Between 800 and 849

Sixty years ago, Sam Walton started a single mom-and-pop shop and transformed it into the world’s biggest retailer. Since those founding days, one thing has remained consistent: our commitment to helping our customers save money so they can live better. Today, we’re reinventing the shopping experience and our associates are at the heart of it. When you join our Walmart family of brands, you’ll play a crucial role in shaping the future of retail, improving millions of lives around the world. We are ecstatic to have been named a Great Place to Work® Certified May 2023 – May 2024, Disability: IN 2023 Best Places to Work, and Fast Company 100 Best Workplaces for Innovators 2023. This is that place where your passions meet purpose. Join our family and build a career you’re proud of.

NAICS: 43
NAICS Definition: Retail Trade
Employees: 562,029
Subsidiaries: 26
12-month incidents
0
Known data breaches
7
Attack type number
2

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/jcpenney.jpeg
JCPenney
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/walmart.jpeg
Walmart
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
JCPenney
100%
Compliance Rate
0/4 Standards Verified
Walmart
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Retail Industry Average (This Year)

No incidents recorded for JCPenney in 2025.

Incidents vs Retail Industry Average (This Year)

No incidents recorded for Walmart in 2025.

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

JCPenney cyber incidents detection timeline including parent company and subsidiaries

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

Walmart cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/jcpenney.jpeg
JCPenney
Incidents

Date Detected: 05/2017
Type:Breach
Blog: Blog

Date Detected: 4/2016
Type:Cyber Attack
Attack Vector: Malicious Software
Blog: Blog

Date Detected: 1/2016
Type:Cyber Attack
Attack Vector: Malware
Blog: Blog
https://images.rankiteo.com/companyimages/walmart.jpeg
Walmart
Incidents

Date Detected: 4/2025
Type:Ransomware
Attack Vector: Zero-day vulnerabilities in MOVEit and Cleo file transfer software
Motivation: Data extortion
Blog: Blog

Date Detected: 1/2024
Type:Breach
Attack Vector: Hacking
Blog: Blog

Date Detected: 12/2023
Type:Breach
Attack Vector: External System Breach (Hacking)
Blog: Blog

FAQ

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

Walmart company has faced a higher number of disclosed cyber incidents historically compared to JCPenney company.

In the current year, Walmart company has reported more cyber incidents than JCPenney company.

Walmart company has confirmed experiencing a ransomware attack, while JCPenney company has not reported such incidents publicly.

Both Walmart company and JCPenney company have disclosed experiencing at least one data breach.

JCPenney company has reported targeted cyberattacks, while Walmart company has not reported such incidents publicly.

Neither JCPenney company nor Walmart company has reported experiencing or disclosing vulnerabilities publicly.

Neither JCPenney nor Walmart holds any compliance certifications.

Neither company holds any compliance certifications.

Walmart company has more subsidiaries worldwide compared to JCPenney company.

Walmart company employs more people globally than JCPenney company, reflecting its scale as a Retail.

Neither JCPenney nor Walmart holds SOC 2 Type 1 certification.

Neither JCPenney nor Walmart holds SOC 2 Type 2 certification.

Neither JCPenney nor Walmart holds ISO 27001 certification.

Neither JCPenney nor Walmart holds PCI DSS certification.

Neither JCPenney nor Walmart holds HIPAA certification.

Neither JCPenney nor Walmart 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