Rankiteo Logo
Rankiteo
Leader in Cyber Underwriting
Loading...
NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop
WindowsmacOSLinux
Download

Comparison Overview

ST Engineering North AmericaST Engineering North America
VS
Lockheed MartinLockheed Martin
ST Engineering North America

ST Engineering North America

2011 Crystal Dr, Arlington, Virginia, US, 22202

Last Update: 31/12/2025

View Profile
Between 700 and 749
https://www.stengg.com/
746/1000Moderate

ST Engineering is a global technology, defense and engineering group with a diverse portfolio of businesses across the aerospace, smart city, defense and public security segments. In the U.S., we operate in over 50 cities across 21 states with our headquarters in Arlin...

NAICS:336414
NAICS Definition:Guided Missile and Space Vehicle Manufacturing
Employees:81
Subsidiaries:5
12-month incidents
0
Known data breaches
0
Attack type number
0
Lockheed Martin

Lockheed Martin

6801 Rockledge Drive, Bethesda, 20817, US

Last Update: 20/05/2026

View Profile
755/1000Fair

The world relies on what we do. Headquartered in Bethesda, Maryland, with offices across the U.S. and around the globe, our team delivers solutions that strengthen national security, shape industries and push engineering and technology to new levels. We collaborate t...

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

Compliance Ranges Comparison

Based On Specific Ai Models Category
ST Engineering North America

ST Engineering North America

-
ISO 27001Not verified
ISO 27001
-
SOC2 Type 1Not verified
SOC2 Type 1
-
SOC2 Type 2Not verified
SOC2 Type 2
-
GDPRNot verified
GDPR
-
PCI DSSNot verified
PCI DSS
-
HIPAANot verified
HIPAA
Lockheed Martin

Lockheed Martin

-
ISO 27001Not verified
ISO 27001
-
SOC2 Type 1Not verified
SOC2 Type 1
-
SOC2 Type 2Not verified
SOC2 Type 2
-
GDPRNot verified
GDPR
-
PCI DSSNot verified
PCI DSS
-
HIPAANot verified
HIPAA

Benchmark & Cyber Underwriting Signals

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

No incidents recorded for ST Engineering North America in 2026.

Incidents

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

Lockheed Martin has 85.19% more incidents than the average of all companies with at least one recorded incident.

Incidents

Incident History - ST Engineering North America (X = Date, Y = Severity)

ST Engineering North America cyber incidents detection timeline including parent company and subsidiaries.

No timeline data available
R - Ransomware
C - Cyber Attack
D - Data Breach
V - Vulnerability

Incident History - Lockheed Martin (X = Date, Y = Severity)

Lockheed Martin cyber incidents detection timeline including parent company and subsidiaries.

R - Ransomware
C - Cyber Attack
D - Data Breach
V - Vulnerability

Notable Incidents

Last Cyber / HR Incidents / Global...
ST Engineering North America

ST Engineering North America

Incidents
No explicit notable incidents reported.
Lockheed Martin

Lockheed Martin

Incidents
🔒 Incident : Cyber Attack
LOC1774283448
🔒 Incident : Breach
LOCULANOR1777876145
🔒 Incident : Cyber Attack
LOC621092125

FAQ

Between ST Engineering North America company and Lockheed Martin company, which one has the best AI Cybersecurity Score ?
Between ST Engineering North America company and Lockheed Martin company, which one has experienced more cyber incidents in the past ?
Between ST Engineering North America company and Lockheed Martin company, which one has experienced more cyber incidents this year ?
Between ST Engineering North America company and Lockheed Martin company, which one has experienced at least one ransomware attack ?
Between ST Engineering North America company and Lockheed Martin company, which one has experienced at least one data breach ?
Between ST Engineering North America company and Lockheed Martin company, which one has experienced at least one targeted cyberattack ?
Between ST Engineering North America company and Lockheed Martin company, which one has experienced at least one vulnerability ?
Between ST Engineering North America company and Lockheed Martin company, which one holds the most compliance certifications ?
Between ST Engineering North America company and Lockheed Martin company, which one holds the fewest compliance certifications ?
Between ST Engineering North America company and Lockheed Martin company, which one has the most subsidiaries ?
Between ST Engineering North America company and Lockheed Martin company, which one has the largest number of employees ?
Between ST Engineering North America and Lockheed Martin, which company holds both SOC 2 Type 1 certifications ?
Between ST Engineering North America and Lockheed Martin, which company holds both SOC 2 Type 2 certifications ?
Which company is ISO 27001 certified - ST Engineering North America or Lockheed Martin ?
Which company is PCI DSS compliant - ST Engineering North America or Lockheed Martin ?
Between ST Engineering North America and Lockheed Martin, which company complies with HIPAA regulations for healthcare data ?
Between ST Engineering North America and Lockheed Martin, which company complies with GDPR requirements ?

Latest Global CVEs

CVE-2026-9754
SUMMARY

An authenticated user with the read role may read limited amounts of uninitialized stack memory via specially-crafted issuances of the filemd5 command

PUBLISHED
Date2026-06-09
UPDATED
Date2026-06-09
RISK INFORMATION (Score: 6.5)
CVSS3
Base Score: 6.5
Complexity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CVSS4
Base Score: 7.1
Complexity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/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
IMPACT SCORE
3.6
EXPLOITABILITY
2.8
CVE-2026-9753
SUMMARY

The $_internalApplyOplogUpdate aggregation pipeline stage can be used to execute a document diff containing a malformed binary diff to return memory out-of-bounds or crash the server. $_internalApplyOplogUpdate can be executed by any authenticated user with access to the aggregate command.

PUBLISHED
Date2026-06-09
UPDATED
Date2026-06-09
RISK INFORMATION (Score: 8.1)
CVSS3
Base Score: 8.1
Complexity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
CVSS4
Base Score: 7.2
Complexity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/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
IMPACT SCORE
5.2
EXPLOITABILITY
2.8
CVE-2026-9752
SUMMARY

An authorized user could trigger a server crash by running a query with a 2dsphere index on a field that stores a GeoJSON GeometryCollection containing a Polygon with a strict-winding CRS. Strict-winding polygons are intentionally unsupported for indexing, but the guard that rejects them does not inspect members of a GeometryCollection, allowing the unsafe path to be reached which ends with an ensuing null-pointer dereference.

PUBLISHED
Date2026-06-09
UPDATED
Date2026-06-09
RISK INFORMATION (Score: 6.5)
CVSS3
Base Score: 6.5
Complexity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CVSS4
Base Score: 7.1
Complexity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/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
IMPACT SCORE
3.6
EXPLOITABILITY
2.8
CVE-2026-9751
SUMMARY

The ldapQueryPassword parameter, when set through the runtime setParameter command, will log the new password to the mongod.log file in plain text.

PUBLISHED
Date2026-06-09
UPDATED
Date2026-06-09
RISK INFORMATION (Score: 5.5)
CVSS3
Base Score: 5.5
Complexity: LOW
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CVSS4
Base Score: 6.8
Complexity: LOW
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/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
IMPACT SCORE
3.6
EXPLOITABILITY
1.8
CVE-2026-9750
SUMMARY

An authenticated user can cause a MongoDB server to crash or return incorrect results by creating documents that interfere with internal metadata processing during query execution. This stems from insufficient separation between user-controlled document fields and internal metadata in certain execution paths.

PUBLISHED
Date2026-06-09
UPDATED
Date2026-06-09
RISK INFORMATION (Score: 6.5)
CVSS3
Base Score: 6.5
Complexity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CVSS4
Base Score: 7.1
Complexity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/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
IMPACT SCORE
3.6
EXPLOITABILITY
2.8