Comparison Overview

Old Navy

VS

Nordstrom

Old Navy

2 Folsom Street, San Francisco, CA, US, 94158
Last Update: 2025-11-22

Forget what you know about old-school industry rules. When you work at Old Navy, you’re choosing a different path. From day one, we’ve been on a mission to democratize fashion and make shopping fun again. Our teams make style accessible to everyone, creating high-quality, must-have fashion essentials for the whole family, with love, season after season. We opened our first store in 1994 in San Francisco and have been on a roll ever since. Today, customers can find fabulous fashion at affordable prices online and in one of our 1,000+ stores globally. Old Navy celebrates a workplace that’s just as diverse as our customers. Fun, fashion, family and value are at the heart of everything we do. We cultivate a community of playful personalities that thrive in a fast-paced environment where our employees can be their most authentic selves. Here, we’re family. Old Navy – a brand for everyone, a place for you!

NAICS: 43
NAICS Definition: Retail Trade
Employees: 28,565
Subsidiaries: 4
12-month incidents
0
Known data breaches
1
Attack type number
1

Nordstrom

1600 7th Ave, Seattle, Washington, US, 98101
Last Update: 2025-11-23
Between 750 and 799

At Nordstrom, we empower our employees to set their sights high and blaze their own trails. This is a place where your success and growth are truly a result of your own efforts and achievements. Our teams are made up of motivated people who work hard to become leaders within the company, at all levels of the organization. These well-traveled paths show how hard work, loyalty, a competitive spirit and your unwavering commitment to the customer can take you and your career to new places. In addition to being a great place to have a career, we’re also committed to respecting the environment and supporting our communities. To learn more, check out NordstromCares.com. Interested in joining the Nordstrom team? See some of our current opportunities under our Careers tab or visit careers.nordstrom.com to apply today.

NAICS: 43
NAICS Definition: Retail Trade
Employees: 46,897
Subsidiaries: 1
12-month incidents
0
Known data breaches
1
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/nordstrom.jpeg
Nordstrom
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
Old Navy
Compliance Rate
0/4 Standards Verified
Nordstrom
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Retail Industry Average (This Year)

No incidents recorded for Old Navy in 2025.

Incidents vs Retail Industry Average (This Year)

No incidents recorded for Nordstrom in 2025.

Incident History — Old Navy (X = Date, Y = Severity)

Old Navy cyber incidents detection timeline including parent company and subsidiaries

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

Nordstrom cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/gap-inc.-old-navy.jpeg
Old Navy
Incidents

Date Detected: 1/2010
Type:Breach
Blog: Blog
https://images.rankiteo.com/companyimages/nordstrom.jpeg
Nordstrom
Incidents

Date Detected: 10/2018
Type:Breach
Attack Vector: Improper handling of employee data
Blog: Blog

FAQ

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

Old Navy and Nordstrom have experienced a similar number of publicly disclosed cyber incidents.

In the current year, Nordstrom company and Old Navy company have not reported any cyber incidents.

Neither Nordstrom company nor Old Navy company has reported experiencing a ransomware attack publicly.

Both Nordstrom company and Old Navy company have disclosed experiencing at least one data breach.

Neither Nordstrom company nor Old Navy company has reported experiencing targeted cyberattacks publicly.

Neither Old Navy company nor Nordstrom company has reported experiencing or disclosing vulnerabilities publicly.

Neither Old Navy nor Nordstrom holds any compliance certifications.

Neither company holds any compliance certifications.

Old Navy company has more subsidiaries worldwide compared to Nordstrom company.

Nordstrom company employs more people globally than Old Navy company, reflecting its scale as a Retail.

Neither Old Navy nor Nordstrom holds SOC 2 Type 1 certification.

Neither Old Navy nor Nordstrom holds SOC 2 Type 2 certification.

Neither Old Navy nor Nordstrom holds ISO 27001 certification.

Neither Old Navy nor Nordstrom holds PCI DSS certification.

Neither Old Navy nor Nordstrom holds HIPAA certification.

Neither Old Navy nor Nordstrom 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