Comparison Overview
United States Space Force

United States Space Force
2020 United States Space Force Pentagon, Washington, 20360, US
Last Update: 01/06/2026
The U.S. Space Force (USSF) is a new branch of the Armed Forces, established on December 20, 2019 with enactment of the Fiscal Year 2020 National Defense Authorization Act. The USSF was established within the Department of the Air Force, meaning the Secretary of the Air...

Aselsan
296. Cadde 16, Mehmet Akif Ersoy, 06200, TR
Last Update: 01/04/2026
ASELSAN is a company of Turkish Armed Forces Foundation, established in 1975 in order to meet the communication needs of the Turkish Armed Forces by national means. Currently 74,20% of the shares are owned by the Foundation whereas the remaining 25,8% runs in İstanbul ...
Compliance Ranges Comparison

United States Space Force







Aselsan






Benchmark & Cyber Underwriting Signals
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
United States Space Force 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)
No incidents recorded for Aselsan in 2026.
Incident History - United States Space Force (X = Date, Y = Severity)
United States Space Force cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Aselsan (X = Date, Y = Severity)
Aselsan cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

United States Space Force

Aselsan
FAQ
Latest Global CVEs
Use after free in Aura in Google Chrome prior to 150.0.7871.128 allowed a local attacker to potentially exploit heap corruption via a malicious file. (Chromium security severity: High)
Use after free in Ozone in Google Chrome on Linux prior to 150.0.7871.128 allowed a remote attacker who convinced a user to engage in specific UI gestures to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
Out of bounds read and write in V8 in Google Chrome prior to 150.0.7871.128 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
Use after free in Cast in Google Chrome prior to 150.0.7871.128 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
Use after free in Network in Google Chrome prior to 150.0.7871.128 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Critical)