Comparison Overview

BC Treaty Commission

VS

Seattle Community Police Commission

BC Treaty Commission

700-1111 Melville St., Vancouver, V6E 3V6, CA
Last Update: 2025-12-10
Between 750 and 799

The British Columbia Treaty Commission advocates for and facilitates the recognition and protection of First Nations rights and title, and the implementation of the UN Declaration on the Rights of Indigenous Peoples through the negotiation of modern treaties and agreements. It is the only independent tripartite statutory body in the country whose mandate is to support reconciliation. The Treaty Commission is the independent body responsible for facilitating treaty negotiations among First Nations in BC and the governments of Canada and BC. The Treaty Commission does not negotiate treaties — that is done by the three parties at each negotiation table. The Treaty Commission and the negotiations framework were established in 1992 by agreement among Canada, BC, and the First Nations Summit. They are guided by those agreements and the 1991 Report of the BC Claims Task Force, which is the blueprint for the made-in-BC treaty process. The Treaty Commission and the six-stage treaty negotiations framework were designed to advance negotiations and facilitate fair and durable treaties. The Treaty Commission has three main roles: Facilitating treaty negotiations, including assisting the Parties in finding solutions and resolving disputes; Allocating negotiation support funding to enable First Nations to participate in negotiations; and Educating the public and providing information about treaty negotiations. In 2018 this mandate was expanded to include supporting negotiating Parties in implementing the United Nations Declaration on the Rights of Indigenous Peoples, the Truth and Reconciliation Commission of Canada: Calls to Action, the Principles Respecting the Government of Canada’s Relationship with Indigenous Peoples, and the recognition of First Nations title and rights.

NAICS: None
NAICS Definition: Others
Employees: 18
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Seattle Community Police Commission

Seattle Municipal Tower Building, PO Box 94765, Seattle, WA, US, 98124-7065
Last Update: 2025-12-11

The Seattle Community Police Commission is unique. A number of U.S. cities are under consent decrees with the federal government to reform their police departments. Seattle is the only one with a civilian commission with a mandate to develop reform recommendations and represent community interests and perspectives. The CPC actively engages the public to obtain community input on its current and future work.

NAICS: None
NAICS Definition: Others
Employees: 10
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/bc-treaty-commission.jpeg
BC Treaty Commission
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/seattle-community-police-commission.jpeg
Seattle Community Police Commission
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
BC Treaty Commission
100%
Compliance Rate
0/4 Standards Verified
Seattle Community Police Commission
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Government Relations Industry Average (This Year)

No incidents recorded for BC Treaty Commission in 2025.

Incidents vs Government Relations Industry Average (This Year)

No incidents recorded for Seattle Community Police Commission in 2025.

Incident History — BC Treaty Commission (X = Date, Y = Severity)

BC Treaty Commission cyber incidents detection timeline including parent company and subsidiaries

Incident History — Seattle Community Police Commission (X = Date, Y = Severity)

Seattle Community Police Commission cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/bc-treaty-commission.jpeg
BC Treaty Commission
Incidents

No Incident

https://images.rankiteo.com/companyimages/seattle-community-police-commission.jpeg
Seattle Community Police Commission
Incidents

No Incident

FAQ

Both BC Treaty Commission company and Seattle Community Police Commission company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Seattle Community Police Commission company has disclosed a higher number of cyber incidents compared to BC Treaty Commission company.

In the current year, Seattle Community Police Commission company and BC Treaty Commission company have not reported any cyber incidents.

Neither Seattle Community Police Commission company nor BC Treaty Commission company has reported experiencing a ransomware attack publicly.

Neither Seattle Community Police Commission company nor BC Treaty Commission company has reported experiencing a data breach publicly.

Neither Seattle Community Police Commission company nor BC Treaty Commission company has reported experiencing targeted cyberattacks publicly.

Neither BC Treaty Commission company nor Seattle Community Police Commission company has reported experiencing or disclosing vulnerabilities publicly.

Neither BC Treaty Commission nor Seattle Community Police Commission holds any compliance certifications.

Neither company holds any compliance certifications.

Neither BC Treaty Commission company nor Seattle Community Police Commission company has publicly disclosed detailed information about the number of their subsidiaries.

BC Treaty Commission company employs more people globally than Seattle Community Police Commission company, reflecting its scale as a Government Relations.

Neither BC Treaty Commission nor Seattle Community Police Commission holds SOC 2 Type 1 certification.

Neither BC Treaty Commission nor Seattle Community Police Commission holds SOC 2 Type 2 certification.

Neither BC Treaty Commission nor Seattle Community Police Commission holds ISO 27001 certification.

Neither BC Treaty Commission nor Seattle Community Police Commission holds PCI DSS certification.

Neither BC Treaty Commission nor Seattle Community Police Commission holds HIPAA certification.

Neither BC Treaty Commission nor Seattle Community Police Commission holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Nagios XI versions prior to 2026R1.1 are vulnerable to local privilege escalation due to an unsafe interaction between sudo permissions and application file permissions. A user‑accessible maintenance script may be executed as root via sudo and includes an application file that is writable by a lower‑privileged user. A local attacker with access to the application account can modify this file to introduce malicious code, which is then executed with elevated privileges when the script is run. Successful exploitation results in arbitrary code execution as the root user.

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

Out of bounds read and write in V8 in Google Chrome prior to 143.0.7499.147 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

Description

Use after free in WebGPU in Google Chrome prior to 143.0.7499.147 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

Description

SIPGO is a library for writing SIP services in the GO language. Starting in version 0.3.0 and prior to version 1.0.0-alpha-1, a nil pointer dereference vulnerability is in the SIPGO library's `NewResponseFromRequest` function that affects all normal SIP operations. The vulnerability allows remote attackers to crash any SIP application by sending a single malformed SIP request without a To header. The vulnerability occurs when SIP message parsing succeeds for a request missing the To header, but the response creation code assumes the To header exists without proper nil checks. This affects routine operations like call setup, authentication, and message handling - not just error cases. This vulnerability affects all SIP applications using the sipgo library, not just specific configurations or edge cases, as long as they make use of the `NewResponseFromRequest` function. Version 1.0.0-alpha-1 contains a patch for the issue.

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

GLPI is a free asset and IT management software package. Starting in version 9.1.0 and prior to version 10.0.21, an unauthorized user with an API access can read all knowledge base entries. Users should upgrade to 10.0.21 to receive a patch.

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