Comparison Overview

Taisei Corporation 大成建設株式会社

VS

PCL Construction

Taisei Corporation 大成建設株式会社

Shinjuku Center Building 1-25-1 Nishi-Shinjuku, Shinjuku Tokyo, 163-0606, JP
Last Update: 2025-11-25
Between 750 and 799

Taisei Corporation (大成建設株式会社) is one of the oldest and largest Japanese General Construction Contractors and a major International General Contractor. The main areas of business are building construction, civil engineering, and real estate development. Taisei Corporation's head office is in Shinjuku, Tokyo, Japan with overseas offices in Taiwan, Qatar, Malaysia, Indonesia, India, Pakistan, Vietnam, Thailand, Philippines, Myanmar, Sri Lanka, Egypt and Turkey.

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

PCL Construction

9915-56th Avenue, Edmonton, Alberta, CA, T6E 5L7
Last Update: 2025-11-23
Between 750 and 799

PCL is a group of independent construction companies that carries out work across Canada, the United States, the Caribbean, and in Australia. These diverse operations in the civil infrastructure, heavy industrial, and buildings markets are supported by a strategic presence in 31 major centers. PCL is 100% employee-owned. Watch us build at www.pcl.com

NAICS: 23
NAICS Definition: Construction
Employees: 11,853
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/taisei-corporation-.jpeg
Taisei Corporation 大成建設株式会社
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/pcl-construction.jpeg
PCL Construction
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
Taisei Corporation 大成建設株式会社
100%
Compliance Rate
0/4 Standards Verified
PCL Construction
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Construction Industry Average (This Year)

No incidents recorded for Taisei Corporation 大成建設株式会社 in 2025.

Incidents vs Construction Industry Average (This Year)

No incidents recorded for PCL Construction in 2025.

Incident History — Taisei Corporation 大成建設株式会社 (X = Date, Y = Severity)

Taisei Corporation 大成建設株式会社 cyber incidents detection timeline including parent company and subsidiaries

Incident History — PCL Construction (X = Date, Y = Severity)

PCL Construction cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/taisei-corporation-.jpeg
Taisei Corporation 大成建設株式会社
Incidents

No Incident

https://images.rankiteo.com/companyimages/pcl-construction.jpeg
PCL Construction
Incidents

Date Detected: 2/2020
Type:Breach
Blog: Blog

FAQ

Both Taisei Corporation 大成建設株式会社 company and PCL Construction company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

PCL Construction company has historically faced a number of disclosed cyber incidents, whereas Taisei Corporation 大成建設株式会社 company has not reported any.

In the current year, PCL Construction company and Taisei Corporation 大成建設株式会社 company have not reported any cyber incidents.

Neither PCL Construction company nor Taisei Corporation 大成建設株式会社 company has reported experiencing a ransomware attack publicly.

PCL Construction company has disclosed at least one data breach, while Taisei Corporation 大成建設株式会社 company has not reported such incidents publicly.

Neither PCL Construction company nor Taisei Corporation 大成建設株式会社 company has reported experiencing targeted cyberattacks publicly.

Neither Taisei Corporation 大成建設株式会社 company nor PCL Construction company has reported experiencing or disclosing vulnerabilities publicly.

Neither Taisei Corporation 大成建設株式会社 nor PCL Construction holds any compliance certifications.

Neither company holds any compliance certifications.

PCL Construction company has more subsidiaries worldwide compared to Taisei Corporation 大成建設株式会社 company.

PCL Construction company employs more people globally than Taisei Corporation 大成建設株式会社 company, reflecting its scale as a Construction.

Neither Taisei Corporation 大成建設株式会社 nor PCL Construction holds SOC 2 Type 1 certification.

Neither Taisei Corporation 大成建設株式会社 nor PCL Construction holds SOC 2 Type 2 certification.

Neither Taisei Corporation 大成建設株式会社 nor PCL Construction holds ISO 27001 certification.

Neither Taisei Corporation 大成建設株式会社 nor PCL Construction holds PCI DSS certification.

Neither Taisei Corporation 大成建設株式会社 nor PCL Construction holds HIPAA certification.

Neither Taisei Corporation 大成建設株式会社 nor PCL Construction 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