Comparison Overview

State of Oregon

VS

Ontario Government | Gouvernement de l’Ontario

State of Oregon

Salem, 97301, US
Last Update: 2025-12-17
View Profile
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
View Profile

Ontario Government | Gouvernement de l’Ontario

undefined, undefined, Ontario, undefined, CA
Last Update: 2025-12-17
Between 750 and 799
http://www.ontario.ca

Ontario Government | Gouvernement de l’Ontario The Ontario Government works to serve the public interest and uphold the public trust by providing Ministers with objective advice and expert guidance. The Ontario Public Service carries out the decisions and policies of the elected government with integrity and accountability and administers public services to the highest professional standards. Le gouvernement de l’Ontario sert l’intérêt public et conserve la confiance du public en fournissant aux ministres des conseils objectifs et spécialisés. La fonction publique de l’Ontario applique les décisions et les politiques du gouvernement élu. En respectant le principe de reddition des comptes et avec intégrité, elle administre les services à la population selon les normes professionnelles les plus rigoureuses.

NAICS: 92
NAICS Definition: Public Administration
Employees: 34,157
Subsidiaries: 28
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-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
https://images.rankiteo.com/companyimages/government-of-ontario.jpeg
Ontario Government | Gouvernement de l’Ontario
—
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 of Oregon
100%
Compliance Rate
0/4 Standards Verified
Ontario Government | Gouvernement de l’Ontario
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for State of Oregon in 2025.

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for Ontario Government | Gouvernement de l’Ontario in 2025.

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

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

Incident History — Ontario Government | Gouvernement de l’Ontario (X = Date, Y = Severity)

Ontario Government | Gouvernement de l’Ontario cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

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
https://images.rankiteo.com/companyimages/government-of-ontario.jpeg
Ontario Government | Gouvernement de l’Ontario
Incidents

No Incident

FAQ

Ontario Government | Gouvernement de l’Ontario company demonstrates a stronger AI Cybersecurity Score compared to State of Oregon company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

State of Oregon company has historically faced a number of disclosed cyber incidents, whereas Ontario Government | Gouvernement de l’Ontario company has not reported any.

In the current year, Ontario Government | Gouvernement de l’Ontario company and State of Oregon company have not reported any cyber incidents.

State of Oregon company has confirmed experiencing a ransomware attack, while Ontario Government | Gouvernement de l’Ontario company has not reported such incidents publicly.

State of Oregon company has disclosed at least one data breach, while the other Ontario Government | Gouvernement de l’Ontario company has not reported such incidents publicly.

Neither Ontario Government | Gouvernement de l’Ontario company nor State of Oregon company has reported experiencing targeted cyberattacks publicly.

Neither State of Oregon company nor Ontario Government | Gouvernement de l’Ontario company has reported experiencing or disclosing vulnerabilities publicly.

Neither State of Oregon nor Ontario Government | Gouvernement de l’Ontario holds any compliance certifications.

Neither company holds any compliance certifications.

Ontario Government | Gouvernement de l’Ontario company has more subsidiaries worldwide compared to State of Oregon company.

Ontario Government | Gouvernement de l’Ontario company employs more people globally than State of Oregon company, reflecting its scale as a Government Administration.

Neither State of Oregon nor Ontario Government | Gouvernement de l’Ontario holds SOC 2 Type 1 certification.

Neither State of Oregon nor Ontario Government | Gouvernement de l’Ontario holds SOC 2 Type 2 certification.

Neither State of Oregon nor Ontario Government | Gouvernement de l’Ontario holds ISO 27001 certification.

Neither State of Oregon nor Ontario Government | Gouvernement de l’Ontario holds PCI DSS certification.

Neither State of Oregon nor Ontario Government | Gouvernement de l’Ontario holds HIPAA certification.

Neither State of Oregon nor Ontario Government | Gouvernement de l’Ontario holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Improper Authorization (CWE-285) in Kibana can lead to privilege escalation (CAPEC-233) by allowing an authenticated user to bypass intended permission restrictions via a crafted HTTP request. This allows an attacker who lacks the live queries - read permission to successfully retrieve the list of live queries.

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

Weblate is a web based localization tool. In versions prior to 5.15.1, it was possible to overwrite Git configuration remotely and override some of its behavior. Version 5.15.1 fixes the issue.

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

Allocation of Resources Without Limits or Throttling (CWE-770) in Elasticsearch can allow an authenticated user with snapshot restore privileges to cause Excessive Allocation (CAPEC-130) of memory and a denial of service (DoS) via crafted HTTP request.

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

Allocation of Resources Without Limits or Throttling (CWE-770) in Kibana can allow a low-privileged authenticated user to cause Excessive Allocation (CAPEC-130) of computing resources and a denial of service (DoS) of the Kibana process via a crafted HTTP request.

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

Improper neutralization of input during web page generation ('Cross-site Scripting') (CWE-79) allows an unauthenticated user to embed a malicious script in content that will be served to web browsers causing cross-site scripting (XSS) (CAPEC-63) via a vulnerability a function handler in the Vega AST evaluator.

Published
Date
2025-12-18
Updated
Date
2025-12-18
Risk Information
cvss3
Base: 6.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
References