Comparison Overview

Office of the Privacy Commissioner of Canada/Commissariat à la protection de la vie privée du Canada

VS

State of Oregon

Office of the Privacy Commissioner of Canada/Commissariat à la protection de la vie privée du Canada

Gatineau, CA
Last Update: 2026-01-18
View Profile
Between 650 and 699
http://www.priv.gc.ca/

The Privacy Commissioner of Canada is an Officer of Parliament, mandated to protect and promote privacy rights. The Office of the Privacy Commissioner (OPC) hosts a page on LinkedIn to communicate with people about future career opportunities at the OPC, to offer privacy tips and guidance to small businesses to increase their awareness of, and therefore compliance with, PIPEDA, and to share important announcements. Privacy notice: https://www.priv.gc.ca/en/privacy-and-transparency-at-the-opc/social-media-policies-notices/#_LinkedIn Comment policy: https://www.priv.gc.ca/en/privacy-and-transparency-at-the-opc/social-media-policies-notices/#_Comment About the OPC: https://www.priv.gc.ca/en/about-the-opc/ ********* Le commissaire à la protection de la vie privée du Canada est un haut fonctionnaire du Parlement qui a pour mandat de protéger le droit des personnes à la vie privée et d'en faire la promotion. Le Commissariat à la protection de la vie privée du Canada a créé une page sur LinkedIn pour faire connaître les possibilités de carrière au sein de l’organisation, offrir des conseils et des orientations en matière de protection de la vie privée aux petites entreprises pour accroître leur sensibilisation au droit à la vie privée et les aider à se conformer à la LPRPDE, ainsi que partager des annonces importantes. Avis de confidentialité : https://www.priv.gc.ca/fr/protection-de-la-vie-privee-et-transparence-au-commissariat/medias-sociaux-politiques-avis/#_LinkedIn Politiques relatives aux commentaires : https://www.priv.gc.ca/fr/protection-de-la-vie-privee-et-transparence-au-commissariat/medias-sociaux-politiques-avis/#_Comment À propos du Commissariat : https://www.priv.gc.ca/fr/a-propos-du-commissariat/

NAICS: 92
NAICS Definition: Public Administration
Employees: 173
Subsidiaries: 59
12-month incidents
0
Known data breaches
4
Attack type number
3
View Profile

State of Oregon

Salem, 97301, US
Last Update: 2026-01-18
Between 750 and 799
http://www.oregon.gov/

Official LinkedIn page for the state of Oregon. Oregon is a state in the Pacific Northwest region of the United States. It is located on the Pacific coast, with Washington to the north, California to the south, Nevada on the southeast and Idaho to the east. The Columbia and Snake rivers delineate much of Oregon's northern and eastern boundaries, respectively. The area was inhabited by many indigenous tribes before the arrival of traders, explorers, and settlers who formed an autonomous government in Oregon Country in 1843. The Oregon Territory was created in 1848, and Oregon became the 33rd state on February 14, 1859.

NAICS: 92
NAICS Definition: Public Administration
Employees: 10,454
Subsidiaries: 8
12-month incidents
0
Known data breaches
1
Attack type number
2

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/office-of-the-privacy-commissioner-of-canada.jpeg
Office of the Privacy Commissioner of Canada/Commissariat à la protection de la vie privée du Canada
—
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-of-oregon.jpeg
State of Oregon
—
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
Office of the Privacy Commissioner of Canada/Commissariat à la protection de la vie privée du Canada
100%
Compliance Rate
0/4 Standards Verified
State of Oregon
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for Office of the Privacy Commissioner of Canada/Commissariat à la protection de la vie privée du Canada in 2026.

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for State of Oregon in 2026.

Incident History — Office of the Privacy Commissioner of Canada/Commissariat à la protection de la vie privée du Canada (X = Date, Y = Severity)

Office of the Privacy Commissioner of Canada/Commissariat à la protection de la vie privée du Canada cyber incidents detection timeline including parent company and subsidiaries

Incident History — State of Oregon (X = Date, Y = Severity)

State of Oregon cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/office-of-the-privacy-commissioner-of-canada.jpeg
Office of the Privacy Commissioner of Canada/Commissariat à la protection de la vie privée du Canada
Incidents

Date Detected: 10/2025
Type:Breach
Blog: Blog

Date Detected: 5/2025
Type:Breach
Blog: Blog

Date Detected: 10/2022
Type:Breach
Attack Vector: Unpatched and decommissioned server
Blog: Blog
https://images.rankiteo.com/companyimages/state-of-oregon.jpeg
State of Oregon
Incidents

Date Detected: 11/2023
Type:Ransomware
Motivation: Data exfiltration and ransom
Blog: Blog

Date Detected: 06/2023
Type:Breach
Blog: Blog

FAQ

State of Oregon company demonstrates a stronger AI Cybersecurity Score compared to Office of the Privacy Commissioner of Canada/Commissariat à la protection de la vie privée du Canada company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Office of the Privacy Commissioner of Canada/Commissariat à la protection de la vie privée du Canada company has faced a higher number of disclosed cyber incidents historically compared to State of Oregon company.

In the current year, State of Oregon company and Office of the Privacy Commissioner of Canada/Commissariat à la protection de la vie privée du Canada company have not reported any cyber incidents.

State of Oregon company has confirmed experiencing a ransomware attack, while Office of the Privacy Commissioner of Canada/Commissariat à la protection de la vie privée du Canada company has not reported such incidents publicly.

Both State of Oregon company and Office of the Privacy Commissioner of Canada/Commissariat à la protection de la vie privée du Canada company have disclosed experiencing at least one data breach.

Office of the Privacy Commissioner of Canada/Commissariat à la protection de la vie privée du Canada company has reported targeted cyberattacks, while State of Oregon company has not reported such incidents publicly.

Neither Office of the Privacy Commissioner of Canada/Commissariat à la protection de la vie privée du Canada company nor State of Oregon company has reported experiencing or disclosing vulnerabilities publicly.

Neither Office of the Privacy Commissioner of Canada/Commissariat à la protection de la vie privée du Canada nor State of Oregon holds any compliance certifications.

Neither company holds any compliance certifications.

Office of the Privacy Commissioner of Canada/Commissariat à la protection de la vie privée du Canada company has more subsidiaries worldwide compared to State of Oregon company.

State of Oregon company employs more people globally than Office of the Privacy Commissioner of Canada/Commissariat à la protection de la vie privée du Canada company, reflecting its scale as a Government Administration.

Neither Office of the Privacy Commissioner of Canada/Commissariat à la protection de la vie privée du Canada nor State of Oregon holds SOC 2 Type 1 certification.

Neither Office of the Privacy Commissioner of Canada/Commissariat à la protection de la vie privée du Canada nor State of Oregon holds SOC 2 Type 2 certification.

Neither Office of the Privacy Commissioner of Canada/Commissariat à la protection de la vie privée du Canada nor State of Oregon holds ISO 27001 certification.

Neither Office of the Privacy Commissioner of Canada/Commissariat à la protection de la vie privée du Canada nor State of Oregon holds PCI DSS certification.

Neither Office of the Privacy Commissioner of Canada/Commissariat à la protection de la vie privée du Canada nor State of Oregon holds HIPAA certification.

Neither Office of the Privacy Commissioner of Canada/Commissariat à la protection de la vie privée du Canada nor State of Oregon 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.

Published
Date
2026-01-20
Updated
Date
2026-01-20
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
References
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).

Published
Date
2026-01-20
Updated
Date
2026-01-20
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
References
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).

Published
Date
2026-01-20
Updated
Date
2026-01-20
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
References
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).

Published
Date
2026-01-20
Updated
Date
2026-01-20
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
References
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).

Published
Date
2026-01-20
Updated
Date
2026-01-20
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
References