Comparison Overview

BAE Systems

VS

L3 Technologies

BAE Systems

BAE Systems, 6 Carlton Gardens, London, None, GB, SW1Y 5AD
Last Update: 2025-12-17
Between 800 and 849

At BAE Systems, we help our customers to stay a step ahead when protecting people and national security, critical infrastructure and vital information. We provide some of the world’s most advanced, technology-led defence, aerospace and security solutions and employ a skilled workforce of 107,000 people in more than 40 countries. From state of the art cyber threat detection to flight control systems that enable pilots to make better decisions, we never stop innovating to ensure that our customers maintain their advantage. This is a long-term commitment involving significant investments in skills. We also work closely with local partners to support economic development through the transfer of knowledge, skills and technology.

NAICS: 336414
NAICS Definition: Guided Missile and Space Vehicle Manufacturing
Employees: 43,390
Subsidiaries: 2
12-month incidents
0
Known data breaches
0
Attack type number
0

L3 Technologies

600 Third Ave, New York, NY, US, 10016
Last Update: 2025-12-17
Between 750 and 799

With headquarters in New York City and approximately 31,000 employees worldwide, L3 develops advanced defense technologies and commercial solutions in pilot training, aviation security, night vision and EO/IR, weapons, maritime systems and space. The company reported 2018 sales of $10.2 billion. To learn more about L3, please visit the company’s website.

NAICS: 336414
NAICS Definition: Guided Missile and Space Vehicle Manufacturing
Employees: 15,458
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/bae-systems.jpeg
BAE Systems
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/l3.jpeg
L3 Technologies
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
BAE Systems
100%
Compliance Rate
0/4 Standards Verified
L3 Technologies
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Defense and Space Manufacturing Industry Average (This Year)

No incidents recorded for BAE Systems in 2025.

Incidents vs Defense and Space Manufacturing Industry Average (This Year)

No incidents recorded for L3 Technologies in 2025.

Incident History — BAE Systems (X = Date, Y = Severity)

BAE Systems cyber incidents detection timeline including parent company and subsidiaries

Incident History — L3 Technologies (X = Date, Y = Severity)

L3 Technologies cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/bae-systems.jpeg
BAE Systems
Incidents

No Incident

https://images.rankiteo.com/companyimages/l3.jpeg
L3 Technologies
Incidents

No Incident

FAQ

BAE Systems company demonstrates a stronger AI Cybersecurity Score compared to L3 Technologies company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, L3 Technologies company has disclosed a higher number of cyber incidents compared to BAE Systems company.

In the current year, L3 Technologies company and BAE Systems company have not reported any cyber incidents.

Neither L3 Technologies company nor BAE Systems company has reported experiencing a ransomware attack publicly.

Neither L3 Technologies company nor BAE Systems company has reported experiencing a data breach publicly.

Neither L3 Technologies company nor BAE Systems company has reported experiencing targeted cyberattacks publicly.

Neither BAE Systems company nor L3 Technologies company has reported experiencing or disclosing vulnerabilities publicly.

Neither BAE Systems nor L3 Technologies holds any compliance certifications.

Neither company holds any compliance certifications.

Both L3 Technologies company and BAE Systems company have a similar number of subsidiaries worldwide.

BAE Systems company employs more people globally than L3 Technologies company, reflecting its scale as a Defense and Space Manufacturing.

Neither BAE Systems nor L3 Technologies holds SOC 2 Type 1 certification.

Neither BAE Systems nor L3 Technologies holds SOC 2 Type 2 certification.

Neither BAE Systems nor L3 Technologies holds ISO 27001 certification.

Neither BAE Systems nor L3 Technologies holds PCI DSS certification.

Neither BAE Systems nor L3 Technologies holds HIPAA certification.

Neither BAE Systems nor L3 Technologies holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

n8n is an open source workflow automation platform. Versions starting with 0.211.0 and prior to 1.120.4, 1.121.1, and 1.122.0 contain a critical Remote Code Execution (RCE) vulnerability in their workflow expression evaluation system. Under certain conditions, expressions supplied by authenticated users during workflow configuration may be evaluated in an execution context that is not sufficiently isolated from the underlying runtime. An authenticated attacker could abuse this behavior to execute arbitrary code with the privileges of the n8n process. Successful exploitation may lead to full compromise of the affected instance, including unauthorized access to sensitive data, modification of workflows, and execution of system-level operations. This issue has been fixed in versions 1.120.4, 1.121.1, and 1.122.0. Users are strongly advised to upgrade to a patched version, which introduces additional safeguards to restrict expression evaluation. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only; and/or deploy n8n in a hardened environment with restricted operating system privileges and network access to reduce the impact of potential exploitation. These workarounds do not fully eliminate the risk and should only be used as short-term measures.

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

FastAPI Users allows users to quickly add a registration and authentication system to their FastAPI project. Prior to version 15.0.2, the OAuth login state tokens are completely stateless and carry no per-request entropy or any data that could link them to the session that initiated the OAuth flow. `generate_state_token()` is always called with an empty `state_data` dict, so the resulting JWT only contains the fixed audience claim plus an expiration timestamp. On callback, the library merely checks that the JWT verifies under `state_secret` and is unexpired; there is no attempt to match the state value to the browser that initiated the OAuth request, no correlation cookie, and no server-side cache. Any attacker can hit `/authorize`, capture the server-generated state, finish the upstream OAuth flow with their own provider account, and then trick a victim into loading `.../callback?code=<attacker_code>&state=<attacker_state>`. Because the state JWT is valid for any client for \~1 hour, the victim’s browser will complete the flow. This leads to login CSRF. Depending on the app’s logic, the login CSRF can lead to an account takeover of the victim account or to the victim user getting logged in to the attacker's account. Version 15.0.2 contains a patch for the issue.

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

FileZilla Client 3.63.1 contains a DLL hijacking vulnerability that allows attackers to execute malicious code by placing a crafted TextShaping.dll in the application directory. Attackers can generate a reverse shell payload using msfvenom and replace the missing DLL to achieve remote code execution when the application launches.

Risk Information
cvss3
Base: 9.8
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
cvss4
Base: 8.5
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/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

LDAP Tool Box Self Service Password 1.5.2 contains a password reset vulnerability that allows attackers to manipulate HTTP Host headers during token generation. Attackers can craft malicious password reset requests that generate tokens sent to a controlled server, enabling potential account takeover by intercepting and using stolen reset tokens.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
cvss4
Base: 8.6
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/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

Kimai 1.30.10 contains a SameSite cookie vulnerability that allows attackers to steal user session cookies through malicious exploitation. Attackers can trick victims into executing a crafted PHP script that captures and writes session cookie information to a file, enabling potential session hijacking.

Risk Information
cvss3
Base: 9.8
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
cvss4
Base: 8.5
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/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