Comparison Overview

PL+US: Paid Leave for the United States

VS

North Star Planning

PL+US: Paid Leave for the United States

PO Box 411075, San Francisco, California, 94141, US
Last Update: 2025-11-24
Between 700 and 749

In 2016, Paid Leave for the U.S. (PL+US) was founded as a time-bound campaign to win paid family and medical leave for every working person in the U.S. In five years, PL+US won paid leave for 8.5 million working people at some of the country’s largest employers and helped advance federal policy through the House of Representatives, a historic achievement. PL+US closed our doors in the summer of 2022, but we invite you to check out paidleave.us to find resources on workplace policies, stats and messaging on paid leave, tips for navigating your own paid leave and some of our organizational lessons learned. For any other inquiries, message [email protected]

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

North Star Planning

49 Pineland Dr, New Gloucester Hall, Suite 102, New Gloucester, Maine, US, 04260
Last Update: 2025-11-28

We're a small Maine based consulting planning firm focusing on good planning process and the ultimate ability to implement planning work. North Star Planning aims to meet both of these goals through these guiding principles: The process should be inclusive The products should be accessible The plan should be specific The progress should be measurable

NAICS: 921
NAICS Definition: Executive, Legislative, and Other General Government Support
Employees: 6
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/north-star-planning.jpeg
North Star Planning
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
PL+US: Paid Leave for the United States
Compliance Rate
0/4 Standards Verified
North Star Planning
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Public Policy Offices Industry Average (This Year)

No incidents recorded for PL+US: Paid Leave for the United States in 2025.

Incidents vs Public Policy Offices Industry Average (This Year)

No incidents recorded for North Star Planning in 2025.

Incident History — PL+US: Paid Leave for the United States (X = Date, Y = Severity)

PL+US: Paid Leave for the United States cyber incidents detection timeline including parent company and subsidiaries

Incident History — North Star Planning (X = Date, Y = Severity)

North Star Planning cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/pl-us.jpeg
PL+US: Paid Leave for the United States
Incidents

No Incident

https://images.rankiteo.com/companyimages/north-star-planning.jpeg
North Star Planning
Incidents

No Incident

FAQ

North Star Planning company demonstrates a stronger AI Cybersecurity Score compared to PL+US: Paid Leave for the United States company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, North Star Planning company has disclosed a higher number of cyber incidents compared to PL+US: Paid Leave for the United States company.

In the current year, North Star Planning company and PL+US: Paid Leave for the United States company have not reported any cyber incidents.

Neither North Star Planning company nor PL+US: Paid Leave for the United States company has reported experiencing a ransomware attack publicly.

Neither North Star Planning company nor PL+US: Paid Leave for the United States company has reported experiencing a data breach publicly.

Neither North Star Planning company nor PL+US: Paid Leave for the United States company has reported experiencing targeted cyberattacks publicly.

Neither PL+US: Paid Leave for the United States company nor North Star Planning company has reported experiencing or disclosing vulnerabilities publicly.

Neither PL+US: Paid Leave for the United States nor North Star Planning holds any compliance certifications.

Neither company holds any compliance certifications.

Neither PL+US: Paid Leave for the United States company nor North Star Planning company has publicly disclosed detailed information about the number of their subsidiaries.

North Star Planning company employs more people globally than PL+US: Paid Leave for the United States company, reflecting its scale as a Public Policy Offices.

Neither PL+US: Paid Leave for the United States nor North Star Planning holds SOC 2 Type 1 certification.

Neither PL+US: Paid Leave for the United States nor North Star Planning holds SOC 2 Type 2 certification.

Neither PL+US: Paid Leave for the United States nor North Star Planning holds ISO 27001 certification.

Neither PL+US: Paid Leave for the United States nor North Star Planning holds PCI DSS certification.

Neither PL+US: Paid Leave for the United States nor North Star Planning holds HIPAA certification.

Neither PL+US: Paid Leave for the United States nor North Star Planning 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