Comparison Overview

Ministry of Defence of India

VS

State of Ohio

Ministry of Defence of India

None
Last Update: 2025-11-27
Between 700 and 749

The Government of India is responsible for ensuring the defence of India and every part thereof. The Supreme Command of the Armed Forces vests in the President. The responsibility for national defence rests with the Cabinet. This is discharged through the Ministry of Defence, which provides the policy framework and wherewithal to the Armed Forces to discharge their responsibilities in the context of the defence of the country. The Raksha Mantri (Defence Minister) is the head of the Ministry of Defence. The principal task of the Defence Ministry is to obtain policy directions of the Government on all defence and security related matters and communicate them for implementation to the Services Headquarters, Inter-Services Organisations, Production Establishments and Research and Development Organisations. It is also required to ensure effective implementation of the Government's policy directions and the execution of approved programmes within the allocated resources. Ministry of Defence comprises of four Departments viz. Department of Defence (DOD), Department of Defence Production (DDP), Department of Defence Research & Development (DDR&D) and Department of Ex-Servicemen Welfare and also Finance Division.

NAICS: 92
NAICS Definition: Public Administration
Employees: 5,199
Subsidiaries: 0
12-month incidents
0
Known data breaches
1
Attack type number
2

State of Ohio

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

Employment with the State of Ohio is more than ‘just a job’ – it is a privilege to serve our families, friends and neighbors who rely on us throughout our great state. We are a team of dedicated public servants committed to high performance, innovative thinking, and delivering excellent and efficient services. Our goal is to recruit and retain the best talent for our positions, because when we have the best talent, we get the best results for our community. We are #TeamOhio.

NAICS: 92
NAICS Definition: Public Administration
Employees: 27,825
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/defaultcompany.jpeg
Ministry of Defence of India
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/state-of-ohio.jpeg
State of Ohio
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
Ministry of Defence of India
100%
Compliance Rate
0/4 Standards Verified
State of Ohio
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for Ministry of Defence of India in 2025.

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for State of Ohio in 2025.

Incident History — Ministry of Defence of India (X = Date, Y = Severity)

Ministry of Defence of India cyber incidents detection timeline including parent company and subsidiaries

Incident History — State of Ohio (X = Date, Y = Severity)

State of Ohio cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/defaultcompany.jpeg
Ministry of Defence of India
Incidents

Date Detected: 2/2022
Type:Breach
Attack Vector: Human Error
Blog: Blog

Date Detected: 3/2018
Type:Data Leak
Attack Vector: Insider Threat
Blog: Blog
https://images.rankiteo.com/companyimages/state-of-ohio.jpeg
State of Ohio
Incidents

No Incident

FAQ

State of Ohio company demonstrates a stronger AI Cybersecurity Score compared to Ministry of Defence of India company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Ministry of Defence of India company has historically faced a number of disclosed cyber incidents, whereas State of Ohio company has not reported any.

In the current year, State of Ohio company and Ministry of Defence of India company have not reported any cyber incidents.

Neither State of Ohio company nor Ministry of Defence of India company has reported experiencing a ransomware attack publicly.

Ministry of Defence of India company has disclosed at least one data breach, while the other State of Ohio company has not reported such incidents publicly.

Neither State of Ohio company nor Ministry of Defence of India company has reported experiencing targeted cyberattacks publicly.

Neither Ministry of Defence of India company nor State of Ohio company has reported experiencing or disclosing vulnerabilities publicly.

Neither Ministry of Defence of India nor State of Ohio holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Ministry of Defence of India company nor State of Ohio company has publicly disclosed detailed information about the number of their subsidiaries.

State of Ohio company employs more people globally than Ministry of Defence of India company, reflecting its scale as a Government Administration.

Neither Ministry of Defence of India nor State of Ohio holds SOC 2 Type 1 certification.

Neither Ministry of Defence of India nor State of Ohio holds SOC 2 Type 2 certification.

Neither Ministry of Defence of India nor State of Ohio holds ISO 27001 certification.

Neither Ministry of Defence of India nor State of Ohio holds PCI DSS certification.

Neither Ministry of Defence of India nor State of Ohio holds HIPAA certification.

Neither Ministry of Defence of India nor State of Ohio 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