Comparison Overview

Vermont Department of Labor

VS

State of Oregon

Vermont Department of Labor

5 Green Mountain Drive, None, Montpelier, Vermont, US, 05601
Last Update: 2025-11-28
Between 650 and 699

The Vermont Department of Labor is comprised of four major divisions; Workforce Development, Labor Market Information, Unemployment Insurance, and Workers’ Compensation & Workplace Safety. The Department serves both individuals and employers with equal dedication and energy. The ultimate goal is the protection and growth of Vermont’s working landscape.

NAICS: 92
NAICS Definition: Public Administration
Employees: 117
Subsidiaries: 0
12-month incidents
0
Known data breaches
3
Attack type number
1

State of Oregon

Salem, 97301, US
Last Update: 2025-11-21
Between 750 and 799

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/vermont-department-of-labor.jpeg
Vermont Department of Labor
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
Vermont Department of Labor
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 Vermont Department of Labor in 2025.

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for State of Oregon in 2025.

Incident History — Vermont Department of Labor (X = Date, Y = Severity)

Vermont Department of Labor 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/vermont-department-of-labor.jpeg
Vermont Department of Labor
Incidents

Date Detected: 8/2023
Type:Breach
Attack Vector: Unauthorized Access
Blog: Blog

Date Detected: 02/2021
Type:Breach
Attack Vector: Mailing Error
Blog: Blog

Date Detected: 3/2017
Type:Breach
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 Vermont Department of Labor company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Vermont Department of Labor 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 Vermont Department of Labor company have not reported any cyber incidents.

State of Oregon company has confirmed experiencing a ransomware attack, while Vermont Department of Labor company has not reported such incidents publicly.

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

Neither State of Oregon company nor Vermont Department of Labor company has reported experiencing targeted cyberattacks publicly.

Neither Vermont Department of Labor company nor State of Oregon company has reported experiencing or disclosing vulnerabilities publicly.

Neither Vermont Department of Labor nor State of Oregon holds any compliance certifications.

Neither company holds any compliance certifications.

State of Oregon company has more subsidiaries worldwide compared to Vermont Department of Labor company.

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

Neither Vermont Department of Labor nor State of Oregon holds SOC 2 Type 1 certification.

Neither Vermont Department of Labor nor State of Oregon holds SOC 2 Type 2 certification.

Neither Vermont Department of Labor nor State of Oregon holds ISO 27001 certification.

Neither Vermont Department of Labor nor State of Oregon holds PCI DSS certification.

Neither Vermont Department of Labor nor State of Oregon holds HIPAA certification.

Neither Vermont Department of Labor nor State of Oregon holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

ThingsBoard in versions prior to v4.2.1 allows an authenticated user to upload malicious SVG images via the "Image Gallery", leading to a Stored Cross-Site Scripting (XSS) vulnerability. The exploit can be triggered when any user accesses the public API endpoint of the malicious SVG images, or if the malicious images are embedded in an `iframe` element, during a widget creation, deployed to any page of the platform (e.g., dashboards), and accessed during normal operations. The vulnerability resides in the `ImageController`, which fails to restrict the execution of JavaScript code when an image is loaded by the user's browser. This vulnerability can lead to the execution of malicious code in the context of other users' sessions, potentially compromising their accounts and allowing unauthorized actions.

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

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to to verify that the token used during the code exchange originates from the same authentication flow, which allows an authenticated user to perform account takeover via a specially crafted email address used when switching authentication methods and sending a request to the /users/login/sso/code-exchange endpoint. The vulnerability requires ExperimentalEnableAuthenticationTransfer to be enabled (default: enabled) and RequireEmailVerification to be disabled (default: disabled).

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

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to sanitize team email addresses to be visible only to Team Admins, which allows any authenticated user to view team email addresses via the GET /api/v4/channels/{channel_id}/common_teams endpoint

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
Description

Exposure of email service credentials to users without administrative rights in Devolutions Server.This issue affects Devolutions Server: before 2025.2.21, before 2025.3.9.

Description

Exposure of credentials in unintended requests in Devolutions Server.This issue affects Server: through 2025.2.20, through 2025.3.8.