Comparison Overview

Marks and Spencer

VS

H-E-B

Marks and Spencer

Waterside House, 35 North Wharf Rd, London, London, GB, W2 1NW
Last Update: 2025-11-27

At M&S, we're dedicated to being the most trusted retailer, prioritising quality and delivering value. Every day, we bring the magic of M&S to our customers, whenever, wherever and however they want to shop with us. For over a century, we've set the standard, doing the right thing and embracing innovation. Today, with over 65,000 colleagues serving 32 million customers globally, we're putting quality products at the heart of everything we do. Tomorrow holds boundless opportunities with us. We're pioneering digital innovation and shaping the future of retail where our values drive every action. We stay close to customers and colleagues, always curious and connected. Our decisions are bold, our actions ambitious. Transparency is paramount, with straightforward, honest communication. We're constantly innovating, always striving for the best. Our focus is on aiming higher and winning together, combined with wise financial decisions to secure our future. Join us at M&S to shape the future of retail.

NAICS: 43
NAICS Definition: Retail Trade
Employees: 39,274
Subsidiaries: 0
12-month incidents
27
Known data breaches
1
Attack type number
3

H-E-B

646 South Flores, San Antonio, TX, 78204, US
Last Update: 2025-11-20
Between 800 and 849

H-E-B is headquartered in San Antonio, Texas with approximately $32 billion in revenue and 117,000+ Partners. Founded in 1905, H-E-B operates more than 400 stores in a number of formats, including superstores, supermarkets and gourmet markets. H-E-B is the #1 food retailer in the Austin, San Antonio, Houston, Corpus Christi and Rio Grande Valley markets. Our company is the largest private company in Texas and one of the 15 largest privately held companies in the U.S. Our employees are called Partners. That's because we work together to build our company and create a sense of community here in Texas. Working here is more than a job. It's a chance work with many great people and blaze an exciting career path.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/marks-and-spencer.jpeg
Marks and Spencer
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/heb.jpeg
H-E-B
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
Marks and Spencer
100%
Compliance Rate
0/4 Standards Verified
H-E-B
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Retail Industry Average (This Year)

Marks and Spencer has 7614.29% more incidents than the average of same-industry companies with at least one recorded incident.

Incidents vs Retail Industry Average (This Year)

No incidents recorded for H-E-B in 2025.

Incident History — Marks and Spencer (X = Date, Y = Severity)

Marks and Spencer cyber incidents detection timeline including parent company and subsidiaries

Incident History — H-E-B (X = Date, Y = Severity)

H-E-B cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/marks-and-spencer.jpeg
Marks and Spencer
Incidents

Date Detected: 9/2025
Type:Ransomware
Motivation: financial gain (ransom demand), disruption of operations
Blog: Blog

Date Detected: 9/2025
Type:Ransomware
Attack Vector: SMB (Server Message Block) exploitation, lateral movement via network shares, recruitment of affiliates for branded variants, partnerships with initial access brokers (e.g., Scattered Spider)
Motivation: financial gain, dominance in ransomware ecosystem, recruitment of affiliates, disruption of rival groups
Blog: Blog

Date Detected: 8/2025
Type:Cyber Attack
Attack Vector: AI-driven attacks, Cybercrime-as-a-Service (CaaS), Ransomware, Phishing, Supply Chain Compromise
Motivation: Financial gain, Disruption, Data theft
Blog: Blog
https://images.rankiteo.com/companyimages/heb.jpeg
H-E-B
Incidents

No Incident

FAQ

H-E-B company demonstrates a stronger AI Cybersecurity Score compared to Marks and Spencer company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Marks and Spencer company has historically faced a number of disclosed cyber incidents, whereas H-E-B company has not reported any.

In the current year, Marks and Spencer company has reported more cyber incidents than H-E-B company.

Marks and Spencer company has confirmed experiencing a ransomware attack, while H-E-B company has not reported such incidents publicly.

Marks and Spencer company has disclosed at least one data breach, while the other H-E-B company has not reported such incidents publicly.

Marks and Spencer company has reported targeted cyberattacks, while H-E-B company has not reported such incidents publicly.

Neither Marks and Spencer company nor H-E-B company has reported experiencing or disclosing vulnerabilities publicly.

Neither Marks and Spencer nor H-E-B holds any compliance certifications.

Neither company holds any compliance certifications.

H-E-B company has more subsidiaries worldwide compared to Marks and Spencer company.

H-E-B company employs more people globally than Marks and Spencer company, reflecting its scale as a Retail.

Neither Marks and Spencer nor H-E-B holds SOC 2 Type 1 certification.

Neither Marks and Spencer nor H-E-B holds SOC 2 Type 2 certification.

Neither Marks and Spencer nor H-E-B holds ISO 27001 certification.

Neither Marks and Spencer nor H-E-B holds PCI DSS certification.

Neither Marks and Spencer nor H-E-B holds HIPAA certification.

Neither Marks and Spencer nor H-E-B 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