Comparison Overview

Oregon Department of Transportation

VS

Texas Health and Human Services

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

Texas Health and Human Services

4601 W Guadalupe St. , Austin, TX, US, 78751
Last Update: 2025-11-27
Between 750 and 799

Overview The Texas Health and Human Services Commission (HHSC) is an agency within the Texas Health and Human Services System. In September 2016, Texas began transforming how it delivers health and human services to qualified Texans, with a goal of making the Health and Human Services System more efficient and effective. Sept. 1, 2017, marked another major milestone in this transformation. The new accountable, restructured system: - Makes it easier for people to find out about the services or benefits for which they may qualify. - Better integrates programs by removing bureaucratic silos and grouping similar programs and services together. - Creates clear lines of accountability within the organization. - Includes well-defined and objective performance metrics for all organizational areas. Texas Health and Human Services now consists of 2 agencies: the Texas Health and Human Services Commission and the Texas Department of State Health Services (DSHS). HHS is headquartered in Austin, TX. Services Provided - Medicaid for families and children - Long-term care for people who are older or have disabilities - SNAP (Supplemental Nutrition Assistance Program) food benefits and TANF (Temporary Assistance For Needy Families) cash assistance for families Behavior health services - Services to help keep people who are older or who have disabilities in their homes or communities - Services for women or other people with special health needs Oversight of Regulatory Functions - Licensing and credentialing of long-term care facilities, such as nursing homes and assisted living - Licensing child care providers - Managing the day-to-day operations of state supported living centers and state hospitals

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

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/texashhsc.jpeg
Texas Health and Human Services
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
Texas Health and Human Services
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 Texas Health and Human Services 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 — Texas Health and Human Services (X = Date, Y = Severity)

Texas Health and Human Services 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/texashhsc.jpeg
Texas Health and Human Services
Incidents

No Incident

FAQ

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

Oregon Department of Transportation company has historically faced a number of disclosed cyber incidents, whereas Texas Health and Human Services company has not reported any.

In the current year, Texas Health and Human Services company and Oregon Department of Transportation company have not reported any cyber incidents.

Oregon Department of Transportation company has confirmed experiencing a ransomware attack, while Texas Health and Human Services company has not reported such incidents publicly.

Oregon Department of Transportation company has disclosed at least one data breach, while the other Texas Health and Human Services company has not reported such incidents publicly.

Neither Texas Health and Human Services company nor Oregon Department of Transportation company has reported experiencing targeted cyberattacks publicly.

Neither Oregon Department of Transportation company nor Texas Health and Human Services company has reported experiencing or disclosing vulnerabilities publicly.

Neither Oregon Department of Transportation nor Texas Health and Human Services holds any compliance certifications.

Neither company holds any compliance certifications.

Oregon Department of Transportation company has more subsidiaries worldwide compared to Texas Health and Human Services company.

Texas Health and Human Services company employs more people globally than Oregon Department of Transportation company, reflecting its scale as a Government Administration.

Neither Oregon Department of Transportation nor Texas Health and Human Services holds SOC 2 Type 1 certification.

Neither Oregon Department of Transportation nor Texas Health and Human Services holds SOC 2 Type 2 certification.

Neither Oregon Department of Transportation nor Texas Health and Human Services holds ISO 27001 certification.

Neither Oregon Department of Transportation nor Texas Health and Human Services holds PCI DSS certification.

Neither Oregon Department of Transportation nor Texas Health and Human Services holds HIPAA certification.

Neither Oregon Department of Transportation nor Texas Health and Human Services 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