Comparison Overview

Sri Lanka Army

VS

US Navy

Sri Lanka Army

None
Last Update: 2025-11-25
Between 750 and 799

The Army Act was enacted in parliament on the 10th of October 1949 which is recognized as the day, the Ceylon Army was raised. The Army was to be comprised of a Regular and a Volunteer force. In May 1972, when Ceylon became the Republic of Sri Lanka, all Army units were renamed accordingly Regimental Centres # SLAC- Sri Lanka Armoured Corps # SLA - Sri Lanka Artillery # SLE - Sri Lanka Engineers # SLSC - Sri Lanka Signals Corps # SLLI - Sri Lanka Light Infantry # SLSR - Sri Lanka Sinha RegimentM # GW - Gamunu Watch # GR - Gajaba Regiment # VIR - Vijayabahu Infantry Regiment # MIR- Mechanized Infantry Regiment # CDO - Commando Regiment # SF - Special Forces Regiment # MIC - Military Intelligence Corps # CES - Corps of Engineer Services # SLASC - Sri Lanka Army Service Corps # SLAMC - Sri Lanka Army Medical Corps # SLAOC - Sri Lanka Army Ordnance Corps # SLEME - Sri Lanka Electrical and Mechanical Engineers # SLCMP - Sri Lanka Corps of Military Police # SLAGSC - Sri Lanka Army General Service Corps # SLAWC - Sri Lanka Army Women's Corps # SLRC - Sri Lanka Riffle Corps # SLPC - Sri Lanka Army Pioneer Corps # SLNG - Sri Lanka National Guard

NAICS: 928
NAICS Definition:
Employees: 10,001
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

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/sri-lanka-army.jpeg
Sri Lanka 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
Sri Lanka Army
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 Sri Lanka Army in 2025.

Incidents vs Armed Forces Industry Average (This Year)

No incidents recorded for US Navy in 2025.

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

Sri Lanka Army 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/sri-lanka-army.jpeg
Sri Lanka Army
Incidents

No Incident

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

Sri Lanka 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 historically faced a number of disclosed cyber incidents, whereas Sri Lanka Army company has not reported any.

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

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

US Navy company has disclosed at least one data breach, while Sri Lanka Army company has not reported such incidents publicly.

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

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

Neither Sri Lanka Army nor US Navy holds any compliance certifications.

Neither company holds any compliance certifications.

US Navy company has more subsidiaries worldwide compared to Sri Lanka Army company.

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

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

Neither Sri Lanka Army nor US Navy holds SOC 2 Type 2 certification.

Neither Sri Lanka Army nor US Navy holds ISO 27001 certification.

Neither Sri Lanka Army nor US Navy holds PCI DSS certification.

Neither Sri Lanka Army nor US Navy holds HIPAA certification.

Neither Sri Lanka Army 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