Comparison Overview

California Cannabis Industry Association

VS

The ICCF Group

California Cannabis Industry Association

1225 8th St, Sacramento, California, 95814, US
Last Update: 2025-11-27

CCIA was formed to unite the cannabis industry in California and to allow it to speak with one voice at the state and local levels. We strive to educate and act as a resource to lawmakers regarding all areas of the cannabis industry. We are also dedicated to addressing issues related to driving under the influence, unlawful diversion to minors, and substance abuse.

NAICS: 921
NAICS Definition:
Employees: 23
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

The ICCF Group

25786 Georgetown Station, Washington, DC, 20027, US
Last Update: 2025-11-28
Between 700 and 749

The International Conservation Caucus Foundation (ICCF) is a 501(c)(3) educational foundation promoting the projection of U.S. leadership for international conservation worldwide. For a decade, the mission of ICCF has been to serve as the nucleus for Congressional leadership for U.S. international conservation, in concert with the protection of U.S. business and national security interests worldwide. ICCF underpins the leadership of the bipartisan U.S. Congressional International Conservation Caucus (ICC), which comprises more than a third of the U.S. Congress. We educate policymakers on international issues of natural resource management throughout the legislative process. We are pro-business, pro-development, and pro-environment and are committed to market-oriented solutions for conservation and sustainability worldwide.

NAICS: 921
NAICS Definition:
Employees: 65
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/california-cannabis-industry-association.jpeg
California Cannabis Industry Association
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/international-conservation-caucus-foundation.jpeg
The ICCF Group
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
California Cannabis Industry Association
100%
Compliance Rate
0/4 Standards Verified
The ICCF Group
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Public Policy Offices Industry Average (This Year)

No incidents recorded for California Cannabis Industry Association in 2025.

Incidents vs Public Policy Offices Industry Average (This Year)

No incidents recorded for The ICCF Group in 2025.

Incident History — California Cannabis Industry Association (X = Date, Y = Severity)

California Cannabis Industry Association cyber incidents detection timeline including parent company and subsidiaries

Incident History — The ICCF Group (X = Date, Y = Severity)

The ICCF Group cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/california-cannabis-industry-association.jpeg
California Cannabis Industry Association
Incidents

No Incident

https://images.rankiteo.com/companyimages/international-conservation-caucus-foundation.jpeg
The ICCF Group
Incidents

No Incident

FAQ

The ICCF Group company demonstrates a stronger AI Cybersecurity Score compared to California Cannabis Industry Association company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, The ICCF Group company has disclosed a higher number of cyber incidents compared to California Cannabis Industry Association company.

In the current year, The ICCF Group company and California Cannabis Industry Association company have not reported any cyber incidents.

Neither The ICCF Group company nor California Cannabis Industry Association company has reported experiencing a ransomware attack publicly.

Neither The ICCF Group company nor California Cannabis Industry Association company has reported experiencing a data breach publicly.

Neither The ICCF Group company nor California Cannabis Industry Association company has reported experiencing targeted cyberattacks publicly.

Neither California Cannabis Industry Association company nor The ICCF Group company has reported experiencing or disclosing vulnerabilities publicly.

Neither California Cannabis Industry Association nor The ICCF Group holds any compliance certifications.

Neither company holds any compliance certifications.

Neither California Cannabis Industry Association company nor The ICCF Group company has publicly disclosed detailed information about the number of their subsidiaries.

The ICCF Group company employs more people globally than California Cannabis Industry Association company, reflecting its scale as a Public Policy Offices.

Neither California Cannabis Industry Association nor The ICCF Group holds SOC 2 Type 1 certification.

Neither California Cannabis Industry Association nor The ICCF Group holds SOC 2 Type 2 certification.

Neither California Cannabis Industry Association nor The ICCF Group holds ISO 27001 certification.

Neither California Cannabis Industry Association nor The ICCF Group holds PCI DSS certification.

Neither California Cannabis Industry Association nor The ICCF Group holds HIPAA certification.

Neither California Cannabis Industry Association nor The ICCF Group 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