Comparison Overview

GEOshare

VS

NASA - National Aeronautics and Space Administration

GEOshare

1750 Tysons Blvd, Tysons, VA, 22102, US
Last Update: 2025-03-07 (UTC)
Between 700 and 749

GEOshare is a global condosat services provider that offers satellite capabilities at an affordable price. Welcome to the LinkedIn page of GEOshare. We’re proud to offer satellite-sharing and mission support services to commercial customers worldwide. From construction through launch, GEOshare does all the work to bring you satellite capabilities at an affordable price. We meet your satellite needs by: • Matching customers to shared satellites and orbit locations • Building satellites and customized payloads • Offering insurance and facilitating financing when needed • Providing launch services and mission assurance As a wholly owned subsidiary of Lockheed Martin, GEOshare combines the proven reliability of Lockheed Martin products and engineering with the flexibility of an independent entrepreneurial venture. Connect and engage with us to learn more about the latest in satellite-sharing services and affordable access to space. GEOshare. We Do All the Work.

NAICS: 336
NAICS Definition:
Employees: 2
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

NASA - National Aeronautics and Space Administration

300 E Street SW, None, Washington, DC, US, 20546
Last Update: 2025-06-17 (UTC)
Between 750 and 799

For more than 60 years, NASA has been breaking barriers to achieve the seemingly impossible—from walking on the Moon to pushing the boundaries of human spaceflight farther than ever before. We work in space and around the world in laboratories and wind tunnels, on airfields and in control rooms to explore some of life’s fundamental mysteries: What’s out there in space? How do we get there? And what can we learn that will make life better here on Earth? We are passionate professionals united by a common purpose: to pioneer the future in space exploration, scientific discovery and aeronautics research. Today, we continue NASA’s legacy of excellence and innovation through an unprecedented array of missions. We are developing the most advanced rockets and spacecraft ever designed, studying the Earth for answers to critical challenges facing our planet, improving the air transportation experience, and so much more. Join us as we reach for new heights and reveal the unknown for the benefit of humanity.

NAICS: 3364
NAICS Definition: Aerospace Product and Parts Manufacturing
Employees: 47,729
Subsidiaries: 8
12-month incidents
2
Known data breaches
1
Attack type number
3

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/geoshare.jpeg
GEOshare
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/nasa.jpeg
NASA - National Aeronautics and Space Administration
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
GEOshare
100%
Compliance Rate
0/4 Standards Verified
NASA - National Aeronautics and Space Administration
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 GEOshare in 2025.

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

NASA - National Aeronautics and Space Administration has 300.0% more incidents than the average of same-industry companies with at least one recorded incident.

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

GEOshare cyber incidents detection timeline including parent company and subsidiaries

Incident History — NASA - National Aeronautics and Space Administration (X = Date, Y = Severity)

NASA - National Aeronautics and Space Administration cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/geoshare.jpeg
GEOshare
Incidents

No Incident

https://images.rankiteo.com/companyimages/nasa.jpeg
NASA - National Aeronautics and Space Administration
Incidents

Date Detected: 6/2025
Type:Breach
Blog: Blog

Date Detected: 5/2025
Type:Vulnerability
Attack Vector: Exploitation of vulnerabilities in software
Motivation: To compromise computer systems at NASA and other institutions using the vulnerable software
Blog: Blog

Date Detected: 01/1999
Type:Cyber Attack
Attack Vector: Unauthorized Access
Blog: Blog

FAQ

NASA - National Aeronautics and Space Administration company demonstrates a stronger AI Cybersecurity Score compared to GEOshare company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

NASA - National Aeronautics and Space Administration company has historically faced a number of disclosed cyber incidents, whereas GEOshare company has not reported any.

In the current year, NASA - National Aeronautics and Space Administration company has reported more cyber incidents than GEOshare company.

Neither NASA - National Aeronautics and Space Administration company nor GEOshare company has reported experiencing a ransomware attack publicly.

NASA - National Aeronautics and Space Administration company has disclosed at least one data breach, while GEOshare company has not reported such incidents publicly.

NASA - National Aeronautics and Space Administration company has reported targeted cyberattacks, while GEOshare company has not reported such incidents publicly.

NASA - National Aeronautics and Space Administration company has disclosed at least one vulnerability, while GEOshare company has not reported such incidents publicly.

Neither GEOshare nor NASA - National Aeronautics and Space Administration holds any compliance certifications.

Neither company holds any compliance certifications.

NASA - National Aeronautics and Space Administration company has more subsidiaries worldwide compared to GEOshare company.

NASA - National Aeronautics and Space Administration company employs more people globally than GEOshare company, reflecting its scale as a Aviation and Aerospace Component Manufacturing.

Neither GEOshare nor NASA - National Aeronautics and Space Administration holds SOC 2 Type 1 certification.

Neither GEOshare nor NASA - National Aeronautics and Space Administration holds SOC 2 Type 2 certification.

Neither GEOshare nor NASA - National Aeronautics and Space Administration holds ISO 27001 certification.

Neither GEOshare nor NASA - National Aeronautics and Space Administration holds PCI DSS certification.

Neither GEOshare nor NASA - National Aeronautics and Space Administration holds HIPAA certification.

Neither GEOshare nor NASA - National Aeronautics and Space Administration holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Deck Mate 1 executes firmware directly from an external EEPROM without verifying authenticity or integrity. An attacker with physical access can replace or reflash the EEPROM to run arbitrary code that persists across reboots. Because this design predates modern secure-boot or signed-update mechanisms, affected systems should be physically protected or retired from service. The vendor has not indicated that firmware updates are available for this legacy model.

Risk Information
cvss4
Base: 7.0
Severity: LOW
CVSS:4.0/AV:P/AC:L/AT:N/PR:N/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

Deck Mate 2 lacks a verified secure-boot chain and runtime integrity validation for its controller and display modules. Without cryptographic boot verification, an attacker with physical access can modify or replace the bootloader, kernel, or filesystem and gain persistent code execution on reboot. This weakness allows long-term firmware tampering that survives power cycles. The vendor indicates that more recent firmware updates strengthen update-chain integrity and disable physical update ports to mitigate related attack avenues.

Risk Information
cvss4
Base: 7.0
Severity: LOW
CVSS:4.0/AV:P/AC:L/AT:N/PR:N/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

Deck Mate 2's firmware update mechanism accepts packages without cryptographic signature verification, encrypts them with a single hard-coded AES key shared across devices, and uses a truncated HMAC for integrity validation. Attackers with access to the update interface - typically via the unit's USB update port - can craft or modify firmware packages to execute arbitrary code as root, allowing persistent compromise of the device's integrity and deck randomization process. Physical or on-premises access remains the most likely attack path, though network-exposed or telemetry-enabled deployments could theoretically allow remote exploitation if misconfigured. The vendor confirmed that firmware updates have been issued to correct these update-chain weaknesses and that USB update access has been disabled on affected units.

Risk Information
cvss4
Base: 7.0
Severity: LOW
CVSS:4.0/AV:P/AC:L/AT:N/PR:N/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

Uncontrolled Resource Consumption vulnerability in Legion of the Bouncy Castle Inc. Bouncy Castle for Java FIPS bc-fips on All (API modules), Legion of the Bouncy Castle Inc. Bouncy Castle for Java LTS bcprov-lts8on on All (API modules) allows Excessive Allocation. This vulnerability is associated with program files core/src/main/jdk1.9/org/bouncycastle/crypto/fips/AESNativeCFB.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/fips/AESNativeGCM.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/fips/SHA256NativeDigest.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/fips/AESNativeEngine.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/fips/AESNativeCBC.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/fips/AESNativeCTR.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/engines/AESNativeCFB.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/engines/AESNativeGCM.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/engines/AESNativeEngine.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/engines/AESNativeCBC.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/engines/AESNativeGCMSIV.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/engines/AESNativeCCM.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/engines/AESNativeCTR.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/digests/SHA256NativeDigest.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/digests/SHA224NativeDigest.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/digests/SHA3NativeDigest.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/digests/SHAKENativeDigest.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/digests/SHA512NativeDigest.Java, core/src/main/jdk1.9/org/bouncycastle/crypto/digests/SHA384NativeDigest.Java. This issue affects Bouncy Castle for Java FIPS: from 2.1.0 through 2.1.1; Bouncy Castle for Java LTS: from 2.73.0 through 2.73.7.

Risk Information
cvss4
Base: 5.9
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/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:P/AU:N/R:U/V:C/RE:M/U:Amber
Description

Wasmtime is a runtime for WebAssembly. In versions from 38.0.0 to before 38.0.3, the implementation of component-model related host-to-wasm trampolines in Wasmtime contained a bug where it's possible to carefully craft a component, which when called in a specific way, would crash the host with a segfault or assert failure. Wasmtime 38.0.3 has been released and is patched to fix this issue. There are no workarounds.

Risk Information
cvss4
Base: 2.1
Severity: HIGH
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L/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