Comparison Overview

Cannabis Information Sharing & Analysis Organization (Cannabis ISAO)

VS

CASA

Cannabis Information Sharing & Analysis Organization (Cannabis ISAO)

Leesburg, 20176, US
Last Update: 2025-12-10
Between 700 and 749

The Cannabis Information Sharing & Analysis Center

NAICS: 519
NAICS Definition: Other Information Services
Employees: 4
Subsidiaries: 0
12-month incidents
0
Known data breaches
1
Attack type number
1

CASA

CASA Building, Bedfordview, Gauteng, 2008, ZA
Last Update: 2025-12-10
Between 750 and 799

CASA is an industry leading association that can provide you with the edge you need to be an effective business owner with a substantial property portfolio and gives you the power to confidently manage your business and structures to enable you, the business owner, to later on become a member of our exclusive business and investment consortiums.

NAICS: 519
NAICS Definition:
Employees: 17,713
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/casa_2.jpeg
CASA
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
Cannabis Information Sharing & Analysis Organization (Cannabis ISAO)
Compliance Rate
0/4 Standards Verified
CASA
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Information Services Industry Average (This Year)

No incidents recorded for Cannabis Information Sharing & Analysis Organization (Cannabis ISAO) in 2025.

Incidents vs Information Services Industry Average (This Year)

No incidents recorded for CASA in 2025.

Incident History — Cannabis Information Sharing & Analysis Organization (Cannabis ISAO) (X = Date, Y = Severity)

Cannabis Information Sharing & Analysis Organization (Cannabis ISAO) cyber incidents detection timeline including parent company and subsidiaries

Incident History — CASA (X = Date, Y = Severity)

CASA cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/cannabis-isao.jpeg
Cannabis Information Sharing & Analysis Organization (Cannabis ISAO)
Incidents

Date Detected: 6/2020
Type:Breach
Attack Vector: Defacement of Tor leak site
Motivation: Potential backlash from the cyber community or an inside exit scam
Blog: Blog
https://images.rankiteo.com/companyimages/casa_2.jpeg
CASA
Incidents

No Incident

FAQ

CASA company demonstrates a stronger AI Cybersecurity Score compared to Cannabis Information Sharing & Analysis Organization (Cannabis ISAO) company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Cannabis Information Sharing & Analysis Organization (Cannabis ISAO) company has historically faced a number of disclosed cyber incidents, whereas CASA company has not reported any.

In the current year, CASA company and Cannabis Information Sharing & Analysis Organization (Cannabis ISAO) company have not reported any cyber incidents.

Neither CASA company nor Cannabis Information Sharing & Analysis Organization (Cannabis ISAO) company has reported experiencing a ransomware attack publicly.

Cannabis Information Sharing & Analysis Organization (Cannabis ISAO) company has disclosed at least one data breach, while the other CASA company has not reported such incidents publicly.

Neither CASA company nor Cannabis Information Sharing & Analysis Organization (Cannabis ISAO) company has reported experiencing targeted cyberattacks publicly.

Neither Cannabis Information Sharing & Analysis Organization (Cannabis ISAO) company nor CASA company has reported experiencing or disclosing vulnerabilities publicly.

Neither Cannabis Information Sharing & Analysis Organization (Cannabis ISAO) nor CASA holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Cannabis Information Sharing & Analysis Organization (Cannabis ISAO) company nor CASA company has publicly disclosed detailed information about the number of their subsidiaries.

CASA company employs more people globally than Cannabis Information Sharing & Analysis Organization (Cannabis ISAO) company, reflecting its scale as a Information Services.

Neither Cannabis Information Sharing & Analysis Organization (Cannabis ISAO) nor CASA holds SOC 2 Type 1 certification.

Neither Cannabis Information Sharing & Analysis Organization (Cannabis ISAO) nor CASA holds SOC 2 Type 2 certification.

Neither Cannabis Information Sharing & Analysis Organization (Cannabis ISAO) nor CASA holds ISO 27001 certification.

Neither Cannabis Information Sharing & Analysis Organization (Cannabis ISAO) nor CASA holds PCI DSS certification.

Neither Cannabis Information Sharing & Analysis Organization (Cannabis ISAO) nor CASA holds HIPAA certification.

Neither Cannabis Information Sharing & Analysis Organization (Cannabis ISAO) nor CASA holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

NXLog Agent before 6.11 can load a file specified by the OPENSSL_CONF environment variable.

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

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

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

A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. You should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."

Risk Information
cvss2
Base: 5.0
Severity: LOW
AV:N/AC:L/Au:N/C:N/I:P/A:N
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/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

MJML through 4.18.0 allows mj-include directory traversal to test file existence and (in the type="css" case) read files. NOTE: this issue exists because of an incomplete fix for CVE-2020-12827.

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

A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).

Risk Information
cvss3
Base: 5.8
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N