Comparison Overview

US Navy

VS

British Army

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

British Army

Trenchard Lines, Andover, GB
Last Update: 2025-11-25
Between 750 and 799

Joining the British Army, you’ll get much more from life than you ever would with a civilian career – you’ll have the opportunity to do something that really matters, with a team that are like family to you. The sense of belonging in the Army is next level: when you’ve trained with each other and overcome new challenges together, you build bonds that last a lifetime that see you through whatever life throws at you – on and off the battlefield. It doesn’t matter where you’ve come from, or what you’ve studied – if you’ve got drive, determination and the will to make an impact, there’s a place for you here. You’ll have access to world-class training and development, and the chance to gain valuable qualifications. You’ll get to see the world – from skiing in Europe, to white-water rafting in the States, to being on operations across the globe. You’ll have the chance to make a difference, realise your potential, and make people proud. Regular or Reserve, Officer or Soldier – whatever role you’re in, the bonds you build here will be unbreakable, and the memories will last forever. If you’re looking for adventure, opportunity, and friends for life, it’s time to find where you belong. You Belong Here: Join the British Army.

NAICS: 92811
NAICS Definition: National Security
Employees: 33,417
Subsidiaries: 6
12-month incidents
0
Known data breaches
1
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/british-army.jpeg
British Army
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
US Navy
Compliance Rate
0/4 Standards Verified
British Army
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Armed Forces Industry Average (This Year)

No incidents recorded for US Navy in 2025.

Incidents vs Armed Forces Industry Average (This Year)

No incidents recorded for British Army in 2025.

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

US Navy cyber incidents detection timeline including parent company and subsidiaries

Incident History — British Army (X = Date, Y = Severity)

British Army cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

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
https://images.rankiteo.com/companyimages/british-army.jpeg
British Army
Incidents

Date Detected: 04/2022
Type:Breach
Motivation: Data Theft
Blog: Blog

FAQ

British Army company demonstrates a stronger AI Cybersecurity Score compared to US Navy company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

US Navy company has faced a higher number of disclosed cyber incidents historically compared to British Army company.

In the current year, British Army company and US Navy company have not reported any cyber incidents.

Neither British Army company nor US Navy company has reported experiencing a ransomware attack publicly.

Both British Army company and US Navy company have disclosed experiencing at least one data breach.

US Navy company has reported targeted cyberattacks, while British Army company has not reported such incidents publicly.

US Navy company has disclosed at least one vulnerability, while British Army company has not reported such incidents publicly.

Neither US Navy nor British Army holds any compliance certifications.

Neither company holds any compliance certifications.

British Army company has more subsidiaries worldwide compared to US Navy company.

US Navy company employs more people globally than British Army company, reflecting its scale as a Armed Forces.

Neither US Navy nor British Army holds SOC 2 Type 1 certification.

Neither US Navy nor British Army holds SOC 2 Type 2 certification.

Neither US Navy nor British Army holds ISO 27001 certification.

Neither US Navy nor British Army holds PCI DSS certification.

Neither US Navy nor British Army holds HIPAA certification.

Neither US Navy nor British Army 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