Comparison Overview

PCL Construction

VS

Burns & McDonnell

PCL Construction

9915-56th Avenue, Edmonton, Alberta, CA, T6E 5L7
Last Update: 2026-01-16
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: 12,124
Subsidiaries: 1
12-month incidents
0
Known data breaches
1
Attack type number
1

Burns & McDonnell

undefined, Kansas City, MO, 64114, US
Last Update: 2026-01-17
Between 750 and 799

At Burns & McDonnell, our engineers, construction professionals, architects, planners, technologists and scientists do more than plan, design and construct. With a mission unchanged since 1898 — make our clients successful — we partner with you on the toughest challenges, constantly working to make the world an amazing place. Each professional brings an ownership mentality to projects at our 100% employee-owned firm, which has safety performance among the top 5% of AEC firms. As dedicated owners, we work through challenges until they’re resolved, meeting or exceeding our clients’ goals. We apply this commitment to our communities, too. We live and work in the same cities you call home, so we share a passion to keep them strong and healthy. From fundraising events and community cleanups to educational outreach and mentorship — especially when it comes to sharing our passion for STEM — our professionals work to make our communities thrive.

NAICS: 23
NAICS Definition: Construction
Employees: 14,158
Subsidiaries: 4
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

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
https://images.rankiteo.com/companyimages/burns-&-mcdonnell.jpeg
Burns & McDonnell
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
PCL Construction
100%
Compliance Rate
0/4 Standards Verified
Burns & McDonnell
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Construction Industry Average (This Year)

No incidents recorded for PCL Construction in 2026.

Incidents vs Construction Industry Average (This Year)

No incidents recorded for Burns & McDonnell in 2026.

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

PCL Construction cyber incidents detection timeline including parent company and subsidiaries

Incident History — Burns & McDonnell (X = Date, Y = Severity)

Burns & McDonnell cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

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

Date Detected: 2/2020
Type:Breach
Blog: Blog
https://images.rankiteo.com/companyimages/burns-&-mcdonnell.jpeg
Burns & McDonnell
Incidents

No Incident

FAQ

Burns & McDonnell company demonstrates a stronger AI Cybersecurity Score compared to PCL Construction company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

PCL Construction company has historically faced a number of disclosed cyber incidents, whereas Burns & McDonnell company has not reported any.

In the current year, Burns & McDonnell company and PCL Construction company have not reported any cyber incidents.

Neither Burns & McDonnell company nor PCL Construction company has reported experiencing a ransomware attack publicly.

PCL Construction company has disclosed at least one data breach, while the other Burns & McDonnell company has not reported such incidents publicly.

Neither Burns & McDonnell company nor PCL Construction company has reported experiencing targeted cyberattacks publicly.

Neither PCL Construction company nor Burns & McDonnell company has reported experiencing or disclosing vulnerabilities publicly.

Neither PCL Construction nor Burns & McDonnell holds any compliance certifications.

Neither company holds any compliance certifications.

Burns & McDonnell company has more subsidiaries worldwide compared to PCL Construction company.

Burns & McDonnell company employs more people globally than PCL Construction company, reflecting its scale as a Construction.

Neither PCL Construction nor Burns & McDonnell holds SOC 2 Type 1 certification.

Neither PCL Construction nor Burns & McDonnell holds SOC 2 Type 2 certification.

Neither PCL Construction nor Burns & McDonnell holds ISO 27001 certification.

Neither PCL Construction nor Burns & McDonnell holds PCI DSS certification.

Neither PCL Construction nor Burns & McDonnell holds HIPAA certification.

Neither PCL Construction nor Burns & McDonnell holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

SummaryA command injection vulnerability (CWE-78) has been found to exist in the `wrangler pages deploy` command. The issue occurs because the `--commit-hash` parameter is passed directly to a shell command without proper validation or sanitization, allowing an attacker with control of `--commit-hash` to execute arbitrary commands on the system running Wrangler. Root causeThe commitHash variable, derived from user input via the --commit-hash CLI argument, is interpolated directly into a shell command using template literals (e.g.,  execSync(`git show -s --format=%B ${commitHash}`)). Shell metacharacters are interpreted by the shell, enabling command execution. ImpactThis vulnerability is generally hard to exploit, as it requires --commit-hash to be attacker controlled. The vulnerability primarily affects CI/CD environments where `wrangler pages deploy` is used in automated pipelines and the --commit-hash parameter is populated from external, potentially untrusted sources. An attacker could exploit this to: * Run any shell command. * Exfiltrate environment variables. * Compromise the CI runner to install backdoors or modify build artifacts. Credits Disclosed responsibly by kny4hacker. Mitigation * Wrangler v4 users are requested to upgrade to Wrangler v4.59.1 or higher. * Wrangler v3 users are requested to upgrade to Wrangler v3.114.17 or higher. * Users on Wrangler v2 (EOL) should upgrade to a supported major version.

Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/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

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle VM VirtualBox accessible data as well as unauthorized access to critical data or complete access to all Oracle VM VirtualBox accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L).

Risk Information
cvss3
Base: 8.1
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H