Comparison Overview
Golden Safeguard

Golden Safeguard
Anderson , 46011, US
Last Update: 13/07/2026
Protect Your CMMC Boundaries Before AI Creates Exposure Artificial intelligence tools are already being used in engineering, development, and operations, often without documentation or oversight. Most organizations don’t discover these risks until an audit, assessment...

Lockheed Martin
6801 Rockledge Drive, Bethesda, 20817, US
Last Update: 20/05/2026
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...
Compliance Ranges Comparison

Golden Safeguard







Lockheed Martin






Benchmark & Cyber Underwriting Signals
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
Golden Safeguard has 52.83% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
Lockheed Martin has 92.31% more incidents than the average of all companies with at least one recorded incident.
Incident History - Golden Safeguard (X = Date, Y = Severity)
Golden Safeguard cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Lockheed Martin (X = Date, Y = Severity)
Lockheed Martin cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Golden Safeguard

Lockheed Martin
FAQ
Latest Global CVEs
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an inadequate encryption strength vulnerability which could allow an attacker to steal admin credentials via weak hash or a pass-the-hash attack.
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an exposure of sensitive system information to an unauthorized control sphere vulnerability which could allow for asset discovery by unauthenticated users.
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an unintended proxy or intermediary vulnerability which could allow an attacker to use an active proxy, which would bypass OT segmentation.
Pronetiqs IntraVUE Versions 3.2.1a14 and prior have a plaintext storage of a password vulnerability that could expose cleartext credentials through the API.
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an exposure of sensitive system information to an unauthorized control sphere vulnerability which could expose the underlying host/share filesystem.