Comparison Overview

State of Oregon

VS

Vlaamse overheid

State of Oregon

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

Vlaamse overheid

Havenlaan 88 Brussels, Brussels Region, BE
Last Update: 2025-12-17

Bij de Vlaamse overheid geef je elke dag opnieuw het beste van jezelf, in een job die een verschil maakt in de maatschappij. Pas afgestudeerd of al een aantal jaren professionele ervaring achter de rug? Op zoek naar een job als arbeider, bediende, leidinggevende, administratief medewerker, ingenieur of ICT-expert? Bij de Vlaamse overheid - de meest aantrekkelijke werkgever in de publieke sector volgens Randstad (2019) - vind je stuk voor stuk uitdagende functies in uiteenlopende vakgebieden, op verschillende locaties in Vlaanderen. Je talent en inzet vinden we veel belangrijker dan je geslacht, gender, afkomst, leeftijd, geaardheid, handicap of chronische ziekte. Stel je vandaag nog kandidaat en bouw mee aan het divers Vlaanderen van morgen. Meer weten over werken voor Vlaanderen en onze openstaande vacatures? www.werkenvoorvlaanderen.be Je kan er ook inschrijven op onze wekelijkse vacaturenieuwsbrief!

NAICS: 922
NAICS Definition:
Employees: 10,001
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/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/vlaamse-overheid.jpeg
Vlaamse overheid
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
Vlaamse overheid
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 Vlaamse overheid 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 — Vlaamse overheid (X = Date, Y = Severity)

Vlaamse overheid 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/vlaamse-overheid.jpeg
Vlaamse overheid
Incidents

No Incident

FAQ

Vlaamse overheid 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 Vlaamse overheid company has not reported any.

In the current year, Vlaamse overheid company and State of Oregon company have not reported any cyber incidents.

State of Oregon company has confirmed experiencing a ransomware attack, while Vlaamse overheid company has not reported such incidents publicly.

State of Oregon company has disclosed at least one data breach, while the other Vlaamse overheid company has not reported such incidents publicly.

Neither Vlaamse overheid company nor State of Oregon company has reported experiencing targeted cyberattacks publicly.

Neither State of Oregon company nor Vlaamse overheid company has reported experiencing or disclosing vulnerabilities publicly.

Neither State of Oregon nor Vlaamse overheid holds any compliance certifications.

Neither company holds any compliance certifications.

State of Oregon company has more subsidiaries worldwide compared to Vlaamse overheid company.

State of Oregon company employs more people globally than Vlaamse overheid company, reflecting its scale as a Government Administration.

Neither State of Oregon nor Vlaamse overheid holds SOC 2 Type 1 certification.

Neither State of Oregon nor Vlaamse overheid holds SOC 2 Type 2 certification.

Neither State of Oregon nor Vlaamse overheid holds ISO 27001 certification.

Neither State of Oregon nor Vlaamse overheid holds PCI DSS certification.

Neither State of Oregon nor Vlaamse overheid holds HIPAA certification.

Neither State of Oregon nor Vlaamse overheid 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.

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

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.

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
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.

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
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.

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
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.

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