Comparison Overview

Lockton

VS

State Life Insurance Pakistan

Lockton

Global, US
Last Update: 2025-12-09
View Profile
Between 700 and 749
http://www.lockton.com

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
View Profile

State Life Insurance Pakistan

Karachi, Sindh 75600, PK
Last Update: 2025-12-09
Between 750 and 799
https://www.facebook.com

The Life Insurance Business in Pakistan was nationalized in March 1972. Initially, the Life Insurance business of 32 Insurance Companies was merged and placed under three Beema Units named “A”, “B” and “C” Beema Units. However, later these Beema Units were merged, and effective November 1, 1972, the Management of the Life Insurance Business was consolidated and entrusted to the State Life Insurance Corporation of Pakistan.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

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
https://images.rankiteo.com/companyimages/state-life-insurance-pakistan.jpeg
State Life Insurance Pakistan
—
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
Lockton
100%
Compliance Rate
0/4 Standards Verified
State Life Insurance Pakistan
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Insurance Industry Average (This Year)

No incidents recorded for Lockton in 2025.

Incidents vs Insurance Industry Average (This Year)

No incidents recorded for State Life Insurance Pakistan in 2025.

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

Lockton cyber incidents detection timeline including parent company and subsidiaries

Incident History — State Life Insurance Pakistan (X = Date, Y = Severity)

State Life Insurance Pakistan cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

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

Date Detected: 11/2024
Type:Breach
Attack Vector: Unauthorized Access
Blog: Blog
https://images.rankiteo.com/companyimages/state-life-insurance-pakistan.jpeg
State Life Insurance Pakistan
Incidents

No Incident

FAQ

State Life Insurance Pakistan 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 State Life Insurance Pakistan company has not reported any.

In the current year, State Life Insurance Pakistan company and Lockton company have not reported any cyber incidents.

Neither State Life Insurance Pakistan company nor Lockton company has reported experiencing a ransomware attack publicly.

Lockton company has disclosed at least one data breach, while the other State Life Insurance Pakistan company has not reported such incidents publicly.

Neither State Life Insurance Pakistan company nor Lockton company has reported experiencing targeted cyberattacks publicly.

Neither Lockton company nor State Life Insurance Pakistan company has reported experiencing or disclosing vulnerabilities publicly.

Neither Lockton nor State Life Insurance Pakistan holds any compliance certifications.

Neither company holds any compliance certifications.

Lockton company has more subsidiaries worldwide compared to State Life Insurance Pakistan company.

Lockton company employs more people globally than State Life Insurance Pakistan company, reflecting its scale as a Insurance.

Neither Lockton nor State Life Insurance Pakistan holds SOC 2 Type 1 certification.

Neither Lockton nor State Life Insurance Pakistan holds SOC 2 Type 2 certification.

Neither Lockton nor State Life Insurance Pakistan holds ISO 27001 certification.

Neither Lockton nor State Life Insurance Pakistan holds PCI DSS certification.

Neither Lockton nor State Life Insurance Pakistan holds HIPAA certification.

Neither Lockton nor State Life Insurance Pakistan holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

NXLog Agent before 6.11 can load a file specified by the OPENSSL_CONF environment variable.

Published
Date
2025-12-14
Updated
Date
2025-12-14
Risk Information
cvss3
Base: 8.1
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
References
Description

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

Published
Date
2025-12-14
Updated
Date
2025-12-14
Risk Information
cvss3
Base: 2.9
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
References
Description

A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. You should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."

Published
Date
2025-12-14
Updated
Date
2025-12-14
Risk Information
cvss2
Base: 5.0
Severity: LOW
AV:N/AC:L/Au:N/C:N/I:P/A:N
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/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
References
Description

MJML through 4.18.0 allows mj-include directory traversal to test file existence and (in the type="css" case) read files. NOTE: this issue exists because of an incomplete fix for CVE-2020-12827.

Published
Date
2025-12-14
Updated
Date
2025-12-14
Risk Information
cvss3
Base: 4.5
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:L
References
Description

A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).

Published
Date
2025-12-14
Updated
Date
2025-12-14
Risk Information
cvss3
Base: 5.8
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N
References