Comparison Overview

Legrand

VS

Honeywell

Legrand

128 avenue du Marechal de Lattre de Tassigny, Limoges, FR, 87045
Last Update: 2026-04-02
Between 800 and 849

Legrand is a global specialist in electrical and digital building infrastructures, dedicated to supporting technological, societal and environmental change around the globe. Our purpose is to improve lives by transforming the spaces where people live, work and meet by delivering electrical and digital infrastructures and connected solutions that are simple, innovative and sustainable. With nearly 38,000 employees around the world, we work hard every day to make the buildings of tomorrow more sustainable for everyone. Legrand reported sales of €8.3 billion in 2022. The company is listed on Euronext Paris and is notably a component stock of the CAC 40, CAC 40 ESG and CAC SBT 1.5 indexes. (code ISIN FR0010307819).

NAICS: 335
NAICS Definition: Electrical Equipment, Appliance, and Component Manufacturing
Employees: 11,700
Subsidiaries: 15
12-month incidents
0
Known data breaches
0
Attack type number
0

Honeywell

Honeywell International Inc., Charlotte, North Carolina, US, 28202
Last Update: 2026-03-28
Between 800 and 849

Honeywell is a Fortune 500 company that invents and manufactures technologies to address tough challenges linked to global macrotrends such as safety, security, and energy. With approximately 110,000 employees worldwide, including more than 19,000 engineers and scientists, we have an unrelenting focus on quality, delivery, value, and technology in everything we make and do. For additional information on how Honeywell processes your personal information please visit https://www.honeywell.com/privacy-statement.

NAICS: 335
NAICS Definition: Electrical Equipment, Appliance, and Component Manufacturing
Employees: 127,082
Subsidiaries: 8
12-month incidents
0
Known data breaches
1
Attack type number
2

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/legrand.jpeg
Legrand
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/honeywell.jpeg
Honeywell
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
Legrand
100%
Compliance Rate
0/4 Standards Verified
Honeywell
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Average (This Year)

No incidents recorded for Legrand in 2026.

Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Average (This Year)

No incidents recorded for Honeywell in 2026.

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

Legrand cyber incidents detection timeline including parent company and subsidiaries

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

Honeywell cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/legrand.jpeg
Legrand
Incidents

No Incident

https://images.rankiteo.com/companyimages/honeywell.jpeg
Honeywell
Incidents

Date Detected: 6/2023
Type:Vulnerability
Attack Vector: Vulnerability Exploitation
Blog: Blog

Date Detected: 5/2023
Type:Vulnerability
Attack Vector: Vulnerability Exploitation
Blog: Blog

Date Detected: 3/2023
Type:Breach
Blog: Blog

FAQ

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

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

In the current year, Honeywell company and Legrand company have not reported any cyber incidents.

Neither Honeywell company nor Legrand company has reported experiencing a ransomware attack publicly.

Honeywell company has disclosed at least one data breach, while Legrand company has not reported such incidents publicly.

Neither Honeywell company nor Legrand company has reported experiencing targeted cyberattacks publicly.

Honeywell company has disclosed at least one vulnerability, while Legrand company has not reported such incidents publicly.

Neither Legrand nor Honeywell holds any compliance certifications.

Neither company holds any compliance certifications.

Legrand company has more subsidiaries worldwide compared to Honeywell company.

Honeywell company employs more people globally than Legrand company, reflecting its scale as a Appliances, Electrical, and Electronics Manufacturing.

Neither Legrand nor Honeywell holds SOC 2 Type 1 certification.

Neither Legrand nor Honeywell holds SOC 2 Type 2 certification.

Neither Legrand nor Honeywell holds ISO 27001 certification.

Neither Legrand nor Honeywell holds PCI DSS certification.

Neither Legrand nor Honeywell holds HIPAA certification.

Neither Legrand nor Honeywell 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