Comparison Overview

Oregon Department of Energy

VS

California Association for Nurse Practitioners

Oregon Department of Energy

550 Capitol St. NE, Salem, OR, 97301, US
Last Update: 2025-11-26

Our Vision: A safe, equitable, clean, and sustainable future. Our Mission: The Oregon Department of Energy helps Oregonians make informed decisions and maintain a resilient and affordable energy system. We advance solutions to shape an equitable clean energy transition, protect the environment and public health, and responsibly balance energ​y needs and impacts for current and future generations. On behalf of Oregonians across the state, the Oregon Department of Energy achieves its mission by providing: ​​- A Central Repository of Energy Data, Information, and Analysis: We research, collect, and analyze data and information to inform state energy planning, regulation, program administration, and policy development. - A Venue for Problem-Solving Oregon's Energy Challenges: We convene constructive conversations about Oregon's energy challenges and opportunities that consider a diverse range of perspectives, foster collaboration and innovative solutions, and facilitate the sharing of best practices with consumers and stakeholders. - Energy Education and Technical Assistance: We provide technical assistance, educational resources, and advice to support policy makers, local governments, industry, energy stakeholders, and the general public in solving energy challenges and meeting Oregon's energy, economic, and climate goals. - Regulation and Oversight: We manage the responsible siting of energy facilities in the state, regulate the transport and disposal of radioactive materials, and represent Oregon's interests at the Hanford Nuclear Site. - Energy Programs and Activities: We manage and administer statutorily authorized energy programs to save energy, support the state's decarbonization efforts, make communities more resilient, and position Oregon to lead by example. JOB OPPORTUNITIES: Visit www.tinyurl.com/ODOEJobs

NAICS: 921
NAICS Definition: Executive, Legislative, and Other General Government Support
Employees: 91
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

California Association for Nurse Practitioners

1415 L Street, Suite 1000, Sacramento, California, US, 95814
Last Update: 2025-11-27
Between 700 and 749

The California Association for Nurse Practitioners is the unifying voice and networking forum for all nurse practitioners statewide, providing consistency and expert guidance for the profession, thereby decreasing barriers and elevating the practice of the nurse practitioner. CANP was founded as the California Coalition of Nurse Practitioners in 1977 by nurse practitioners from the University of California at Davis. The organization has grown into a statewide network of 22 regions with nearly 4,300 members. Most regions have active local chapters with regular meetings and activities. The purpose of CANP is to promote a strong nurse practitioner movement through a statewide communication system; to strengthen the public image of the nurse practitioner; and to support legislative action that encourages the development of the role of the nurse practitioner and makes the health care system more responsive to the needs of the consumer.

NAICS: 921
NAICS Definition: Executive, Legislative, and Other General Government Support
Employees: 17
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-energy.jpeg
Oregon Department of Energy
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/canp.jpeg
California Association for Nurse Practitioners
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 Energy
100%
Compliance Rate
0/4 Standards Verified
California Association for Nurse Practitioners
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Public Policy Offices Industry Average (This Year)

No incidents recorded for Oregon Department of Energy in 2025.

Incidents vs Public Policy Offices Industry Average (This Year)

No incidents recorded for California Association for Nurse Practitioners in 2025.

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

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

Incident History — California Association for Nurse Practitioners (X = Date, Y = Severity)

California Association for Nurse Practitioners 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-energy.jpeg
Oregon Department of Energy
Incidents

No Incident

https://images.rankiteo.com/companyimages/canp.jpeg
California Association for Nurse Practitioners
Incidents

No Incident

FAQ

Oregon Department of Energy company demonstrates a stronger AI Cybersecurity Score compared to California Association for Nurse Practitioners company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, California Association for Nurse Practitioners company has disclosed a higher number of cyber incidents compared to Oregon Department of Energy company.

In the current year, California Association for Nurse Practitioners company and Oregon Department of Energy company have not reported any cyber incidents.

Neither California Association for Nurse Practitioners company nor Oregon Department of Energy company has reported experiencing a ransomware attack publicly.

Neither California Association for Nurse Practitioners company nor Oregon Department of Energy company has reported experiencing a data breach publicly.

Neither California Association for Nurse Practitioners company nor Oregon Department of Energy company has reported experiencing targeted cyberattacks publicly.

Neither Oregon Department of Energy company nor California Association for Nurse Practitioners company has reported experiencing or disclosing vulnerabilities publicly.

Neither Oregon Department of Energy nor California Association for Nurse Practitioners holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Oregon Department of Energy company nor California Association for Nurse Practitioners company has publicly disclosed detailed information about the number of their subsidiaries.

Oregon Department of Energy company employs more people globally than California Association for Nurse Practitioners company, reflecting its scale as a Public Policy Offices.

Neither Oregon Department of Energy nor California Association for Nurse Practitioners holds SOC 2 Type 1 certification.

Neither Oregon Department of Energy nor California Association for Nurse Practitioners holds SOC 2 Type 2 certification.

Neither Oregon Department of Energy nor California Association for Nurse Practitioners holds ISO 27001 certification.

Neither Oregon Department of Energy nor California Association for Nurse Practitioners holds PCI DSS certification.

Neither Oregon Department of Energy nor California Association for Nurse Practitioners holds HIPAA certification.

Neither Oregon Department of Energy nor California Association for Nurse Practitioners 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