Comparison Overview

Life Insurance Corporation of India

VS

Lockton

Life Insurance Corporation of India

Jeevan Bima Marg Yogakshema Building Mumbai, Maharashtra 400021, IN
Last Update: 2025-11-26
Between 800 and 849

The Life Insurance Corporation of India (LIC) is a state-owned Life Insurance Company of India. Founded in 1956, it operates as a Government-Owned Corporation, headquartered in Mumbai, Maharashtra, and is a key player in the life insurance sector in India. LIC offers a wide range of insurance products to cater to different needs of individuals, including Life Insurance, Health Insurance, Pension Plans, ULIPs, Group Schemes and Micro Insurance. We have a vast network of agents and branches across the country and overseas, making it accessible to a large section of the nation's residential and non residential population.

NAICS: 524
NAICS Definition: Insurance Carriers and Related Activities
Employees: 10,001
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Lockton

Global, US
Last Update: 2025-11-24
Between 700 and 749

What makes Lockton stand apart is also what makes us better: independence. Our private ownership empowers our 13,100+ Associates doing business in over 140+ countries to focus solely on clients' risk and insurance needs. With expertise that reaches around the globe, we deliver the deep understanding needed to accomplish remarkable results.

NAICS: 524
NAICS Definition: Insurance Carriers and Related Activities
Employees: 13,887
Subsidiaries: 1
12-month incidents
0
Known data breaches
1
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/lic-india-forever-27b83226.jpeg
Life Insurance Corporation 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/lockton-companies.jpeg
Lockton
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
Life Insurance Corporation of India
100%
Compliance Rate
0/4 Standards Verified
Lockton
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Insurance Industry Average (This Year)

No incidents recorded for Life Insurance Corporation of India in 2025.

Incidents vs Insurance Industry Average (This Year)

No incidents recorded for Lockton in 2025.

Incident History — Life Insurance Corporation of India (X = Date, Y = Severity)

Life Insurance Corporation of India cyber incidents detection timeline including parent company and subsidiaries

Incident History — Lockton (X = Date, Y = Severity)

Lockton cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/lic-india-forever-27b83226.jpeg
Life Insurance Corporation of India
Incidents

No Incident

https://images.rankiteo.com/companyimages/lockton-companies.jpeg
Lockton
Incidents

Date Detected: 11/2024
Type:Breach
Attack Vector: Unauthorized Access
Blog: Blog

FAQ

Life Insurance Corporation of India company demonstrates a stronger AI Cybersecurity Score compared to Lockton company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Lockton company has historically faced a number of disclosed cyber incidents, whereas Life Insurance Corporation of India company has not reported any.

In the current year, Lockton company and Life Insurance Corporation of India company have not reported any cyber incidents.

Neither Lockton company nor Life Insurance Corporation of India company has reported experiencing a ransomware attack publicly.

Lockton company has disclosed at least one data breach, while Life Insurance Corporation of India company has not reported such incidents publicly.

Neither Lockton company nor Life Insurance Corporation of India company has reported experiencing targeted cyberattacks publicly.

Neither Life Insurance Corporation of India company nor Lockton company has reported experiencing or disclosing vulnerabilities publicly.

Neither Life Insurance Corporation of India nor Lockton holds any compliance certifications.

Neither company holds any compliance certifications.

Lockton company has more subsidiaries worldwide compared to Life Insurance Corporation of India company.

Lockton company employs more people globally than Life Insurance Corporation of India company, reflecting its scale as a Insurance.

Neither Life Insurance Corporation of India nor Lockton holds SOC 2 Type 1 certification.

Neither Life Insurance Corporation of India nor Lockton holds SOC 2 Type 2 certification.

Neither Life Insurance Corporation of India nor Lockton holds ISO 27001 certification.

Neither Life Insurance Corporation of India nor Lockton holds PCI DSS certification.

Neither Life Insurance Corporation of India nor Lockton holds HIPAA certification.

Neither Life Insurance Corporation of India nor Lockton 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