Comparison Overview

State Life Insurance Pakistan

VS

Intact

State Life Insurance Pakistan

Karachi, Sindh 75600, PK
Last Update: 2025-11-22
Between 750 and 799

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

Intact

700 University Avenue, Toronto, Ontario, CA, M5G 0A1
Last Update: 2025-11-20

We created a purpose-driven company based on Values and a belief that insurance is about people, not things. This is the foundation on which we have built Intact and it lives every day through our purpose, Values, what we aim to achieve and how. ___ Nous sommes là pour aider les gens, les entreprises et la société à aller de l’avant dans les bons moments et à être résilients dans le moments difficiles. Notre entreprise est basée sur des valeurs et la conviction que l’assurance doit d’abord s’intéresser aux personnes, et non aux choses. C’est dans cette optique que nous avons bâti Intact et ça se reflète chaque jour dans notre raison d’être, nos valeurs, nos facteurs de succès en leadership, notre promesse aux employés, nos objectifs et notre stratégie.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

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
https://images.rankiteo.com/companyimages/intact.jpeg
Intact
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
State Life Insurance Pakistan
100%
Compliance Rate
0/4 Standards Verified
Intact
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Insurance Industry Average (This Year)

No incidents recorded for State Life Insurance Pakistan in 2025.

Incidents vs Insurance Industry Average (This Year)

No incidents recorded for Intact in 2025.

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

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

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

Intact cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/state-life-insurance-pakistan.jpeg
State Life Insurance Pakistan
Incidents

No Incident

https://images.rankiteo.com/companyimages/intact.jpeg
Intact
Incidents

No Incident

FAQ

Intact company demonstrates a stronger AI Cybersecurity Score compared to State Life Insurance Pakistan company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Intact company has disclosed a higher number of cyber incidents compared to State Life Insurance Pakistan company.

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

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

Neither Intact company nor State Life Insurance Pakistan company has reported experiencing a data breach publicly.

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

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

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

Neither company holds any compliance certifications.

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

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

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

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

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

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

Neither State Life Insurance Pakistan nor Intact holds HIPAA certification.

Neither State Life Insurance Pakistan nor Intact 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