Comparison Overview

Post Office Ltd

VS

Old Navy

Post Office Ltd

100 Wood Street, London, England, EC2V 7ER, GB
Last Update: 2025-11-25
Between 750 and 799

We’ve come a long way since it all started over 380 years ago. We’ve built up a network of 11,500 branches across the country. To give you a sense of how big that is, we’ve got more branches than the four biggest banks in the UK put together. Or put simply, we’re the largest retail network in the UK. So we’re there for our customers, wherever they are. But our biggest branch by far is our website, which gets nearly 1 million visitors a week, so we’re building on our digital strategy too. As you can imagine, a business this big has lots of opportunities in lots of different areas. So we’re always looking out for enthusiastic, ambitious and customer-focused people to join us. And we’re striving to become “simpler to run, better for customers and a great place to work”, so innovation is really important. We’re confident the changes we make will be for the best, benefiting both our people and our customers. Social Media Policy: https://bit.ly/3gwSgEl

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

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/post-office.jpeg
Post Office Ltd
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
Post Office Ltd
100%
Compliance Rate
0/4 Standards Verified
Old Navy
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Retail Industry Average (This Year)

No incidents recorded for Post Office Ltd in 2025.

Incidents vs Retail Industry Average (This Year)

No incidents recorded for Old Navy in 2025.

Incident History — Post Office Ltd (X = Date, Y = Severity)

Post Office Ltd cyber incidents detection timeline including parent company and subsidiaries

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

Old Navy cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/post-office.jpeg
Post Office Ltd
Incidents

No Incident

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

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

FAQ

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

Old Navy company has historically faced a number of disclosed cyber incidents, whereas Post Office Ltd company has not reported any.

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

Neither Old Navy company nor Post Office Ltd company has reported experiencing a ransomware attack publicly.

Old Navy company has disclosed at least one data breach, while Post Office Ltd company has not reported such incidents publicly.

Neither Old Navy company nor Post Office Ltd company has reported experiencing targeted cyberattacks publicly.

Neither Post Office Ltd company nor Old Navy company has reported experiencing or disclosing vulnerabilities publicly.

Neither Post Office Ltd nor Old Navy holds any compliance certifications.

Neither company holds any compliance certifications.

Old Navy company has more subsidiaries worldwide compared to Post Office Ltd company.

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

Neither Post Office Ltd nor Old Navy holds SOC 2 Type 1 certification.

Neither Post Office Ltd nor Old Navy holds SOC 2 Type 2 certification.

Neither Post Office Ltd nor Old Navy holds ISO 27001 certification.

Neither Post Office Ltd nor Old Navy holds PCI DSS certification.

Neither Post Office Ltd nor Old Navy holds HIPAA certification.

Neither Post Office Ltd nor Old Navy 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