Comparison Overview

Oregon Department of Transportation

VS

State of California

Oregon Department of Transportation

355 Capitol St. NE, MS 11, Salem, Oregon, US, 97301-3871
Last Update: 2025-11-28
Between 550 and 599

The Oregon Department of Transportation is an award-winning organization, more than 4,500 employees strong. Together, ​we provide a safe and reliable multimodal transportation system that connects people and helps Oregon's communities and economy thrive. Transportation in Oregon is a multi-billion dollar investment in our people, our environment and our state. Almost every aspect of life is affected one way or another by transportation. With 96,000 square miles of land, we must have a safe, dependable system — and in Oregon, that includes highways, passenger and freight rail, public transit and non-motorized transportation. Over the past several years, Oregonians have opted to invest in the state’s transportation infrastructure. This commitment to a sound transportation system is creating opportunities for engineers, planners, maintenance and construction workers, information systems specialists, accountants, customer service representatives, inspectors, policy analysts and other knowledgeable employees. Consider a career with the Oregon Department of Transportation. Live and work among tall mountains, surrounded by sandy ocean beaches and clear blue lakes, in the grassy valleys or on the high desert, in the big city or in a small country town. Oregon has it all — just waiting for you to discover; waiting for you to make your mark. For job opportunities, visit www.odotjobs.com or email [email protected]. For general questions, call (888) ASK-ODOT.

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

State of California

Sacramento, None, Sacramento, California, US, 95814
Last Update: 2025-11-21
Between 750 and 799

Californians deserve a government that works for them and with them. One that will work to ensure opportunity and justice. We are building a California not for the few, but for all — including those who have historically been left out. We are doing the work to make our state a place for every Californian and all the diversity that makes us strong. Our state will be known as a place where everyone is respected, protected, and connected.

NAICS: 92
NAICS Definition: Public Administration
Employees: 44,043
Subsidiaries: 29
12-month incidents
0
Known data breaches
29
Attack type number
3

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/oregon-department-of-transportation.jpeg
Oregon Department of Transportation
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-california.jpeg
State of California
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
Oregon Department of Transportation
100%
Compliance Rate
0/4 Standards Verified
State of California
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for Oregon Department of Transportation in 2025.

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for State of California in 2025.

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

Oregon Department of Transportation cyber incidents detection timeline including parent company and subsidiaries

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

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

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/oregon-department-of-transportation.jpeg
Oregon Department of Transportation
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/state-of-california.jpeg
State of California
Incidents

Date Detected: 1/2025
Type:Breach
Attack Vector: Inadvertent Email
Blog: Blog

Date Detected: 6/2024
Type:Breach
Attack Vector: Unauthorized Access
Blog: Blog

Date Detected: 2/2024
Type:Breach
Attack Vector: Unauthorized Dissemination
Blog: Blog

FAQ

State of California company demonstrates a stronger AI Cybersecurity Score compared to Oregon Department of Transportation company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

State of California company has faced a higher number of disclosed cyber incidents historically compared to Oregon Department of Transportation company.

In the current year, State of California company has reported more cyber incidents than Oregon Department of Transportation company.

Both State of California company and Oregon Department of Transportation company have confirmed experiencing at least one ransomware attack.

Both State of California company and Oregon Department of Transportation company have disclosed experiencing at least one data breach.

Neither State of California company nor Oregon Department of Transportation company has reported experiencing targeted cyberattacks publicly.

Neither Oregon Department of Transportation company nor State of California company has reported experiencing or disclosing vulnerabilities publicly.

Neither Oregon Department of Transportation nor State of California holds any compliance certifications.

Neither company holds any compliance certifications.

State of California company has more subsidiaries worldwide compared to Oregon Department of Transportation company.

State of California company employs more people globally than Oregon Department of Transportation company, reflecting its scale as a Government Administration.

Neither Oregon Department of Transportation nor State of California holds SOC 2 Type 1 certification.

Neither Oregon Department of Transportation nor State of California holds SOC 2 Type 2 certification.

Neither Oregon Department of Transportation nor State of California holds ISO 27001 certification.

Neither Oregon Department of Transportation nor State of California holds PCI DSS certification.

Neither Oregon Department of Transportation nor State of California holds HIPAA certification.

Neither Oregon Department of Transportation nor State of California 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