Comparison Overview

Kmart

VS

MC

Kmart

33 W Monroe Street, Chicago, 60603, US
Last Update: 2026-03-28
View Profile
Between 750 and 799
http://www.kmart.com

Life is ridiculously awesome. That’s a bold statement. But hey, bold statements are our thing. So here’s another one: Kmart is ridiculously awesome, too. Know why? Because we work at it. We don’t do anything halfway. We go out and crush it. We’re about more than the products we sell. And more than creating a great experience in-store and online. We’re about giving our all, making every day as ridiculously awesome as we believe it can be, and having a great time doing it.

NAICS: 43
NAICS Definition: Retail Trade
Employees: 19,339
Subsidiaries: 1
12-month incidents
0
Known data breaches
1
Attack type number
3
View Profile

MC

Rua João Mendonça 529, Senhora da Hora, Porto, PT, 4460-282
Last Update: 2026-04-02
Between 750 and 799
https://mc.sonae.pt/

MC is a company from the SONAE group, and is a leader in the food retail industry in Portugal. We are a company made by all, to all. With a history of over 35 years of continuous growth, MC has a distinctive positioning in different business areas, with a vast portfolio of high quality products, services and brands. Currently, MC owns the following brands: Continente (hypermarkets), Continente Modelo (large dimension supermarkets), Continente Bom Dia (small dimension supermarkets), Continente Online (e-commerce), Meu Super (franchising small dimension supermarkets), Bagga (coffee stores and bakeries), Go Natural (bio supermarkets and restaurants), note! (books and stationery), Wells and Arenal (drugstores). With a solid and inclusive base of action, at MC we focus on people, creating value with the contribution of all. We innovate everyday, leading the way to a better tomorrow, always taking into consideration everyone's needs. Everything we are, we built together. And there's nothing more inspiring than this.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/kmart.jpeg
Kmart
—
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/mc-sonae.jpeg
MC
—
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
Kmart
100%
Compliance Rate
0/4 Standards Verified
MC
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Retail Industry Average (This Year)

No incidents recorded for Kmart in 2026.

Incidents vs Retail Industry Average (This Year)

No incidents recorded for MC in 2026.

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

Kmart cyber incidents detection timeline including parent company and subsidiaries

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

MC cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/kmart.jpeg
Kmart
Incidents

Date Detected: 2/2026
Type:Breach
Attack Vector: Unsecured Database
Blog: Blog

Date Detected: 9/2017
Type:Cyber Attack
Attack Vector: Malicious Script
Blog: Blog

Date Detected: 10/2015
Type:Data Leak
Blog: Blog
https://images.rankiteo.com/companyimages/mc-sonae.jpeg
MC
Incidents

No Incident

FAQ

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

Kmart company has historically faced a number of disclosed cyber incidents, whereas MC company has not reported any.

In the current year, Kmart company has reported more cyber incidents than MC company.

Neither MC company nor Kmart company has reported experiencing a ransomware attack publicly.

Kmart company has disclosed at least one data breach, while the other MC company has not reported such incidents publicly.

Kmart company has reported targeted cyberattacks, while MC company has not reported such incidents publicly.

Neither Kmart company nor MC company has reported experiencing or disclosing vulnerabilities publicly.

Neither Kmart nor MC holds any compliance certifications.

Neither company holds any compliance certifications.

MC company has more subsidiaries worldwide compared to Kmart company.

Kmart company employs more people globally than MC company, reflecting its scale as a Retail.

Neither Kmart nor MC holds SOC 2 Type 1 certification.

Neither Kmart nor MC holds SOC 2 Type 2 certification.

Neither Kmart nor MC holds ISO 27001 certification.

Neither Kmart nor MC holds PCI DSS certification.

Neither Kmart nor MC holds HIPAA certification.

Neither Kmart nor MC 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.

Published
Date
2026-04-03
Updated
Date
2026-04-03
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
References
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.

Published
Date
2026-04-03
Updated
Date
2026-04-03
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
References
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.

Published
Date
2026-04-03
Updated
Date
2026-04-03
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
References
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.

Published
Date
2026-04-03
Updated
Date
2026-04-03
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
References
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.

Published
Date
2026-04-03
Updated
Date
2026-04-03
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
References