Comparison Overview

Involve

VS

Partnership for Safety and Justice

Involve

Oxford House, Derbyshire Street, London, undefined, E2 6HG, GB
Last Update: 2025-11-23
Between 700 and 749

We’re the UK’s public participation charity. We work towards creating a more vibrant democracy, with people at the heart of decision-making. We know that politics often does not work as it should, leaving people and politicians feeling divided, distrustful and powerless. We demonstrate how democracy can be different. We support people and decision-makers to work together to solve our biggest challenges. Our mission is to develop, support and campaign for new ways of involving people in the decisions that affect their lives.

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

Partnership for Safety and Justice

221 NW 2nd Ave, Portland, OR, 97232, US
Last Update: 2025-11-27

Partnership for Safety and Justice is leading the way. We have developed an innovative and provocative model for criminal justice reform, one that engages survivors of crime, people convicted of crime, and the families of both. Together, we advance policy solutions to curb the unsustainable growth of our prison system, invest in programs that prevent crime, and promote healing for people harmed by crime and violence. Our groundbreaking approach has been adopted by groups across the country and continues to serve as a model for public safety reform solutions. To learn more, visit safetyandjustice.org.

NAICS: 921
NAICS Definition: Executive, Legislative, and Other General Government Support
Employees: 15
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/involve_2.jpeg
Involve
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/partnership-for-safety-and-justice.jpeg
Partnership for Safety and Justice
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
Involve
100%
Compliance Rate
0/4 Standards Verified
Partnership for Safety and Justice
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Public Policy Offices Industry Average (This Year)

No incidents recorded for Involve in 2025.

Incidents vs Public Policy Offices Industry Average (This Year)

No incidents recorded for Partnership for Safety and Justice in 2025.

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

Involve cyber incidents detection timeline including parent company and subsidiaries

Incident History — Partnership for Safety and Justice (X = Date, Y = Severity)

Partnership for Safety and Justice cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/involve_2.jpeg
Involve
Incidents

No Incident

https://images.rankiteo.com/companyimages/partnership-for-safety-and-justice.jpeg
Partnership for Safety and Justice
Incidents

No Incident

FAQ

Involve company demonstrates a stronger AI Cybersecurity Score compared to Partnership for Safety and Justice company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Partnership for Safety and Justice company has disclosed a higher number of cyber incidents compared to Involve company.

In the current year, Partnership for Safety and Justice company and Involve company have not reported any cyber incidents.

Neither Partnership for Safety and Justice company nor Involve company has reported experiencing a ransomware attack publicly.

Neither Partnership for Safety and Justice company nor Involve company has reported experiencing a data breach publicly.

Neither Partnership for Safety and Justice company nor Involve company has reported experiencing targeted cyberattacks publicly.

Neither Involve company nor Partnership for Safety and Justice company has reported experiencing or disclosing vulnerabilities publicly.

Neither Involve nor Partnership for Safety and Justice holds any compliance certifications.

Neither company holds any compliance certifications.

Involve company has more subsidiaries worldwide compared to Partnership for Safety and Justice company.

Involve company employs more people globally than Partnership for Safety and Justice company, reflecting its scale as a Public Policy Offices.

Neither Involve nor Partnership for Safety and Justice holds SOC 2 Type 1 certification.

Neither Involve nor Partnership for Safety and Justice holds SOC 2 Type 2 certification.

Neither Involve nor Partnership for Safety and Justice holds ISO 27001 certification.

Neither Involve nor Partnership for Safety and Justice holds PCI DSS certification.

Neither Involve nor Partnership for Safety and Justice holds HIPAA certification.

Neither Involve nor Partnership for Safety and Justice 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