Comparison Overview

Blue Origin

VS

B/E Aerospace

Blue Origin

Kent, US
Last Update: 2026-04-02
View Profile
Between 750 and 799
https://www.blueorigin.com/

We are building a road to space for the benefit of Earth, humanity’s blue origin. Our team is focused on radically reducing the cost of access to space and harnessing its vast resources while mobilizing future generations to realize this mission. Blue Origin builds reusable rocket engines, launch vehicles, in-space systems, and lunar landers. Discover more at BlueOrigin.com. *We hope you engage with us and our community. However, we reserve the right to remove derogatory or off-topic comments from our social media accounts. Thank you for understanding.*

NAICS: 3364
NAICS Definition: Aerospace Product and Parts Manufacturing
Employees: 11,215
Subsidiaries: 1
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

B/E Aerospace

Corporate Headquarters, Cedar Rapids, US
Last Update: 2026-04-01
Between 750 and 799
http://www.beaerospace.com

B/E Aerospace is now part of Rockwell Collins. With the acquisition of B/E Aerospace in April 2017, Rockwell Collins is now a world leader in designing, developing and manufacturing cabin interior products and services that deliver innovation, reliability and efficiency. Our broad range of offerings include aircraft cabin seating, lighting and engineering solutions, oxygen systems, food and beverage preparation and storage equipment, galley systems, water and waste systems, and advanced lavatory systems. We also collaborate closely with our customers to provide customized cabin interior reconfiguration, program management and certification services.

NAICS: 3364
NAICS Definition: Aerospace Product and Parts Manufacturing
Employees: 12,025
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/blue-origin.jpeg
Blue Origin
—
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/be-aerospace.jpeg
B/E Aerospace
—
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
Blue Origin
100%
Compliance Rate
0/4 Standards Verified
B/E Aerospace
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Aviation and Aerospace Component Manufacturing Industry Average (This Year)

No incidents recorded for Blue Origin in 2026.

Incidents vs Aviation and Aerospace Component Manufacturing Industry Average (This Year)

No incidents recorded for B/E Aerospace in 2026.

Incident History — Blue Origin (X = Date, Y = Severity)

Blue Origin cyber incidents detection timeline including parent company and subsidiaries

Incident History — B/E Aerospace (X = Date, Y = Severity)

B/E Aerospace cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/blue-origin.jpeg
Blue Origin
Incidents

No Incident

https://images.rankiteo.com/companyimages/be-aerospace.jpeg
B/E Aerospace
Incidents

No Incident

FAQ

Blue Origin company demonstrates a stronger AI Cybersecurity Score compared to B/E Aerospace company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, B/E Aerospace company has disclosed a higher number of cyber incidents compared to Blue Origin company.

In the current year, B/E Aerospace company and Blue Origin company have not reported any cyber incidents.

Neither B/E Aerospace company nor Blue Origin company has reported experiencing a ransomware attack publicly.

Neither B/E Aerospace company nor Blue Origin company has reported experiencing a data breach publicly.

Neither B/E Aerospace company nor Blue Origin company has reported experiencing targeted cyberattacks publicly.

Neither Blue Origin company nor B/E Aerospace company has reported experiencing or disclosing vulnerabilities publicly.

Neither Blue Origin nor B/E Aerospace holds any compliance certifications.

Neither company holds any compliance certifications.

Blue Origin company has more subsidiaries worldwide compared to B/E Aerospace company.

B/E Aerospace company employs more people globally than Blue Origin company, reflecting its scale as a Aviation and Aerospace Component Manufacturing.

Neither Blue Origin nor B/E Aerospace holds SOC 2 Type 1 certification.

Neither Blue Origin nor B/E Aerospace holds SOC 2 Type 2 certification.

Neither Blue Origin nor B/E Aerospace holds ISO 27001 certification.

Neither Blue Origin nor B/E Aerospace holds PCI DSS certification.

Neither Blue Origin nor B/E Aerospace holds HIPAA certification.

Neither Blue Origin nor B/E Aerospace 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