Comparison Overview

Financial Crimes Enforcement Network, US Treasury

VS

State of Oregon

Financial Crimes Enforcement Network, US Treasury

Washington, DC, US
Last Update: 2025-12-01
Between 700 and 749

Official LinkedIn account of the Financial Crimes Enforcement Network, a U.S. Treasury bureau. Learn more at www.fincen.gov

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

State of Oregon

Salem, 97301, US
Last Update: 2025-12-01
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/fincen.jpeg
Financial Crimes Enforcement Network, US Treasury
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
Financial Crimes Enforcement Network, US Treasury
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)

Financial Crimes Enforcement Network, US Treasury has 53.85% more incidents than the average of same-industry companies with at least one recorded incident.

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for State of Oregon in 2025.

Incident History — Financial Crimes Enforcement Network, US Treasury (X = Date, Y = Severity)

Financial Crimes Enforcement Network, US Treasury 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/fincen.jpeg
Financial Crimes Enforcement Network, US Treasury
Incidents

Date Detected: 3/2025
Type:Cyber Attack
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 Financial Crimes Enforcement Network, US Treasury company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

State of Oregon company has faced a higher number of disclosed cyber incidents historically compared to Financial Crimes Enforcement Network, US Treasury company.

In the current year, Financial Crimes Enforcement Network, US Treasury company has reported more cyber incidents than State of Oregon company.

State of Oregon company has confirmed experiencing a ransomware attack, while Financial Crimes Enforcement Network, US Treasury company has not reported such incidents publicly.

State of Oregon company has disclosed at least one data breach, while Financial Crimes Enforcement Network, US Treasury company has not reported such incidents publicly.

Financial Crimes Enforcement Network, US Treasury company has reported targeted cyberattacks, while State of Oregon company has not reported such incidents publicly.

Neither Financial Crimes Enforcement Network, US Treasury company nor State of Oregon company has reported experiencing or disclosing vulnerabilities publicly.

Neither Financial Crimes Enforcement Network, US Treasury nor State of Oregon holds any compliance certifications.

Neither company holds any compliance certifications.

State of Oregon company has more subsidiaries worldwide compared to Financial Crimes Enforcement Network, US Treasury company.

State of Oregon company employs more people globally than Financial Crimes Enforcement Network, US Treasury company, reflecting its scale as a Government Administration.

Neither Financial Crimes Enforcement Network, US Treasury nor State of Oregon holds SOC 2 Type 1 certification.

Neither Financial Crimes Enforcement Network, US Treasury nor State of Oregon holds SOC 2 Type 2 certification.

Neither Financial Crimes Enforcement Network, US Treasury nor State of Oregon holds ISO 27001 certification.

Neither Financial Crimes Enforcement Network, US Treasury nor State of Oregon holds PCI DSS certification.

Neither Financial Crimes Enforcement Network, US Treasury nor State of Oregon holds HIPAA certification.

Neither Financial Crimes Enforcement Network, US Treasury nor State of Oregon holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.11.1, vllm has a critical remote code execution vector in a config class named Nemotron_Nano_VL_Config. When vllm loads a model config that contains an auto_map entry, the config class resolves that mapping with get_class_from_dynamic_module(...) and immediately instantiates the returned class. This fetches and executes Python from the remote repository referenced in the auto_map string. Crucially, this happens even when the caller explicitly sets trust_remote_code=False in vllm.transformers_utils.config.get_config. In practice, an attacker can publish a benign-looking frontend repo whose config.json points via auto_map to a separate malicious backend repo; loading the frontend will silently run the backend’s code on the victim host. This vulnerability is fixed in 0.11.1.

Risk Information
cvss3
Base: 7.1
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
Description

fastify-reply-from is a Fastify plugin to forward the current HTTP request to another server. Prior to 12.5.0, by crafting a malicious URL, an attacker could access routes that are not allowed, even though the reply.from is defined for specific routes in @fastify/reply-from. This vulnerability is fixed in 12.5.0.

Risk Information
cvss4
Base: 6.9
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/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

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 21.0.2, 20.3.15, and 19.2.17, A Stored Cross-Site Scripting (XSS) vulnerability has been identified in the Angular Template Compiler. It occurs because the compiler's internal security schema is incomplete, allowing attackers to bypass Angular's built-in security sanitization. Specifically, the schema fails to classify certain URL-holding attributes (e.g., those that could contain javascript: URLs) as requiring strict URL security, enabling the injection of malicious scripts. This vulnerability is fixed in 21.0.2, 20.3.15, and 19.2.17.

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

Gin-vue-admin is a backstage management system based on vue and gin. In 2.8.6 and earlier, attackers can delete any file on the server at will, causing damage or unavailability of server resources. Attackers can control the 'FileMd5' parameter to delete any file and folder.

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

Portkey.ai Gateway is a blazing fast AI Gateway with integrated guardrails. Prior to 1.14.0, the gateway determined the destination baseURL by prioritizing the value in the x-portkey-custom-host request header. The proxy route then appends the client-specified path to perform an external fetch. This can be maliciously used by users for SSRF attacks. This vulnerability is fixed in 1.14.0.

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