Comparison Overview

U.S. Coast Guard

VS

US Navy

U.S. Coast Guard

2703 Martin Luther King Jr. Ave SE, Washington, DC, US, 20593
Last Update: 2025-11-25
Between 750 and 799

The mission of the U.S. Coast Guard is to protect the public, the environment, and U.S. economic interests — along the coast and our coastal borders, in the nation's ports and waterways, in international waters, or in any maritime region as required to support national security. As one of the six branches of the Armed Forces, the U.S. Coast Guard is vital to our nation's safety and security. U.S. Coast Guard personnel are the backbone of America’s maritime security. The U.S. Coast Guard employs a topnotch civilian workforce, with more than 7,000 positions in nearly 100 locations nationwide. Search for Jobs and Internships at USAJobs.gov.

NAICS: 92811
NAICS Definition: National Security
Employees: 31,602
Subsidiaries: 28
12-month incidents
0
Known data breaches
13
Attack type number
5

US Navy

1200 Navy Pentagon, Washington, DC, US, 20350
Last Update: 2025-11-26
Between 750 and 799

The United States is a maritime nation, and the U.S. Navy protects America at sea. Alongside our allies and partners, we defend freedom, preserve economic prosperity, and keep the seas open and free. Our nation is engaged in long-term competition. To defend American interests around the globe, the U.S. Navy must remain prepared to execute our timeless role, as directed by Congress and the President.

NAICS: 92811
NAICS Definition: National Security
Employees: 158,925
Subsidiaries: 2
12-month incidents
0
Known data breaches
2
Attack type number
4

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/uscoastguard.jpeg
U.S. Coast Guard
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
U.S. Coast Guard
100%
Compliance Rate
0/4 Standards Verified
US Navy
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Armed Forces Industry Average (This Year)

No incidents recorded for U.S. Coast Guard in 2025.

Incidents vs Armed Forces Industry Average (This Year)

No incidents recorded for US Navy in 2025.

Incident History — U.S. Coast Guard (X = Date, Y = Severity)

U.S. Coast Guard cyber incidents detection timeline including parent company and subsidiaries

Incident History — US Navy (X = Date, Y = Severity)

US Navy cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/uscoastguard.jpeg
U.S. Coast Guard
Incidents

Date Detected: 11/2025
Type:Breach
Motivation: Financial Gain (e.g., unauthorized loans, employment fraud, government benefits fraud)
Blog: Blog

Date Detected: 9/2025
Type:Breach
Attack Vector: Exploitation of Citrix Remote Access Software, Lateral Movement, Privilege Escalation
Motivation: Espionage, Data Theft, Potential Sabotage
Blog: Blog

Date Detected: 7/2025
Type:Breach
Attack Vector: Exploitation of Citrix Remote Access Software, Lateral Movement within Network
Motivation: Espionage, Data Theft
Blog: Blog
https://images.rankiteo.com/companyimages/us-navy.jpeg
US Navy
Incidents

Date Detected: 9/2024
Type:Vulnerability
Attack Vector: Unauthorized Disclosure of Information
Blog: Blog

Date Detected: 9/2024
Type:Breach
Blog: Blog

Date Detected: 10/2021
Type:Cyber Attack
Blog: Blog

FAQ

U.S. Coast Guard company demonstrates a stronger AI Cybersecurity Score compared to US Navy company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

U.S. Coast Guard company has faced a higher number of disclosed cyber incidents historically compared to US Navy company.

In the current year, U.S. Coast Guard company has reported more cyber incidents than US Navy company.

U.S. Coast Guard company has confirmed experiencing a ransomware attack, while US Navy company has not reported such incidents publicly.

Both US Navy company and U.S. Coast Guard company have disclosed experiencing at least one data breach.

Both US Navy company and U.S. Coast Guard company have reported experiencing targeted cyberattacks.

Both U.S. Coast Guard company and US Navy company have disclosed vulnerabilities.

Neither U.S. Coast Guard nor US Navy holds any compliance certifications.

Neither company holds any compliance certifications.

U.S. Coast Guard company has more subsidiaries worldwide compared to US Navy company.

US Navy company employs more people globally than U.S. Coast Guard company, reflecting its scale as a Armed Forces.

Neither U.S. Coast Guard nor US Navy holds SOC 2 Type 1 certification.

Neither U.S. Coast Guard nor US Navy holds SOC 2 Type 2 certification.

Neither U.S. Coast Guard nor US Navy holds ISO 27001 certification.

Neither U.S. Coast Guard nor US Navy holds PCI DSS certification.

Neither U.S. Coast Guard nor US Navy holds HIPAA certification.

Neither U.S. Coast Guard nor US Navy holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.

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

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/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:X/AU:X/R:X/V:X/RE:X/U:X
Description

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Integer Overflow vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions. This issue has been patched in version 1.3.2.

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

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, working with large buffers in Lua scripts can lead to a stack overflow. Users of Lua rules and output scripts may be affected when working with large buffers. This includes a rule passing a large buffer to a Lua script. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves disabling Lua rules and output scripts, or making sure limits, such as stream.depth.reassembly and HTTP response body limits (response-body-limit), are set to less than half the stack size.

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

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions from 8.0.0 to before 8.0.2, a NULL dereference can occur when the entropy keyword is used in conjunction with base64_data. This issue has been patched in version 8.0.2. A workaround involves disabling rules that use entropy in conjunction with base64_data.

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