Comparison Overview

Krispy Kreme

VS

Compass Group

Krispy Kreme

2116 Hawkins St, Charlotte, North Carolina, US, 28203
Last Update: 2026-04-04

Headquartered in Charlotte, N.C., Krispy Kreme is one of the most beloved and well-known sweet treat brands in the world. Our iconic Original Glazed® doughnut is universally recognized for its hot-off-the-line, melt-in-your-mouth experience. Krispy Kreme operates in more than 40 countries through its unique network of fresh doughnut shops, partnerships with leading retailers, and a rapidly growing digital business. Our purpose of touching and enhancing lives through the joy that is Krispy Kreme guides how we operate every day and is reflected in the love we have for our people, our communities, and the planet.

NAICS: 722
NAICS Definition: Food Services and Drinking Places
Employees: 10,305
Subsidiaries: 0
12-month incidents
0
Known data breaches
2
Attack type number
3

Compass Group

Compass House, Chertsey, KT16 9BQ, GB
Last Update: 2026-04-02
Between 800 and 849

Compass Group is a global leader in food services operating in over 25 countries with around 590,000 employees worldwide and generating underlying revenues of over $46 billion for the 2025 fiscal year. Our vision is to be a world-class provider of contract food services and support services, renowned for our great people, our great service, and our great results.

NAICS: 722
NAICS Definition: Food Services and Drinking Places
Employees: 61,892
Subsidiaries: 8
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/krispy-kreme.jpeg
Krispy Kreme
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/compass-group.jpeg
Compass Group
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
Krispy Kreme
100%
Compliance Rate
0/4 Standards Verified
Compass Group
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Food and Beverage Services Industry Average (This Year)

No incidents recorded for Krispy Kreme in 2026.

Incidents vs Food and Beverage Services Industry Average (This Year)

No incidents recorded for Compass Group in 2026.

Incident History — Krispy Kreme (X = Date, Y = Severity)

Krispy Kreme cyber incidents detection timeline including parent company and subsidiaries

Incident History — Compass Group (X = Date, Y = Severity)

Compass Group cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/krispy-kreme.jpeg
Krispy Kreme
Incidents

Date Detected: 6/2025
Type:Ransomware
Attack Vector: Exploitation of vulnerabilities in SimpleHelp RMM software, Initial access brokers
Motivation: Financial gain, Data extortion
Blog: Blog

Date Detected: 12/2024
Type:Cyber Attack
Motivation: financial gain, data theft
Blog: Blog

Date Detected: 11/2024
Type:Breach
Attack Vector: Unauthorized Access
Blog: Blog
https://images.rankiteo.com/companyimages/compass-group.jpeg
Compass Group
Incidents

No Incident

FAQ

Compass Group company demonstrates a stronger AI Cybersecurity Score compared to Krispy Kreme company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Krispy Kreme company has historically faced a number of disclosed cyber incidents, whereas Compass Group company has not reported any.

In the current year, Compass Group company and Krispy Kreme company have not reported any cyber incidents.

Krispy Kreme company has confirmed experiencing a ransomware attack, while Compass Group company has not reported such incidents publicly.

Krispy Kreme company has disclosed at least one data breach, while the other Compass Group company has not reported such incidents publicly.

Krispy Kreme company has reported targeted cyberattacks, while Compass Group company has not reported such incidents publicly.

Neither Krispy Kreme company nor Compass Group company has reported experiencing or disclosing vulnerabilities publicly.

Neither Krispy Kreme nor Compass Group holds any compliance certifications.

Neither company holds any compliance certifications.

Compass Group company has more subsidiaries worldwide compared to Krispy Kreme company.

Compass Group company employs more people globally than Krispy Kreme company, reflecting its scale as a Food and Beverage Services.

Neither Krispy Kreme nor Compass Group holds SOC 2 Type 1 certification.

Neither Krispy Kreme nor Compass Group holds SOC 2 Type 2 certification.

Neither Krispy Kreme nor Compass Group holds ISO 27001 certification.

Neither Krispy Kreme nor Compass Group holds PCI DSS certification.

Neither Krispy Kreme nor Compass Group holds HIPAA certification.

Neither Krispy Kreme nor Compass Group holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, two peer-facing consensus request handlers assume that the history index is always available and call blockchain.history_store.history_index().unwrap() directly. That assumption is false by construction. HistoryStoreProxy::history_index() explicitly returns None for the valid HistoryStoreProxy::WithoutIndex state. when a full node is syncing or otherwise running without the history index, a remote peer can send RequestTransactionsProof or RequestTransactionReceiptsByAddress and trigger an Option::unwrap() panic on the request path. This issue has been patched in version 1.3.0.

Risk Information
cvss3
Base: 5.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Description

PraisonAI is a multi-agent teams system. Prior to version 1.5.95, FileTools.download_file() in praisonaiagents validates the destination path but performs no validation on the url parameter, passing it directly to httpx.stream() with follow_redirects=True. An attacker who controls the URL can reach any host accessible from the server including cloud metadata services and internal network services. This issue has been patched in version 1.5.95.

Risk Information
cvss3
Base: 8.6
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.97, OAuthManager.validate_token() returns True for any token not found in its internal store, which is empty by default. Any HTTP request to the MCP server with an arbitrary Bearer token is treated as authenticated, granting full access to all registered tools and agent capabilities. This issue has been patched in version 4.5.97.

Risk Information
cvss3
Base: 9.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.97, the PraisonAI Gateway server accepts WebSocket connections at /ws and serves agent topology at /info with no authentication. Any network client can connect, enumerate registered agents, and send arbitrary messages to agents and their tool sets. This issue has been patched in version 4.5.97.

Risk Information
cvss3
Base: 9.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.90, MCPToolIndex.search_tools() compiles a caller-supplied string directly as a Python regular expression with no validation, sanitization, or timeout. A crafted regex causes catastrophic backtracking in the re engine, blocking the Python thread for hundreds of seconds and causing a complete service outage. This issue has been patched in version 4.5.90.

Risk Information
cvss3
Base: 6.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H