In Progress
Crowdstrike integration Master SID support
Summary Add Master SID-level integration support for CrowdStrike Falcon, allowing customers to integrate at a higher organizational level so that fewer individual integrations are needed, reducing customer friction. Background We currently have a CrowdStrike Falcon integration, but it operates at the individual SID level. Customers with multiple SIDs must configure each one separately, which creates unnecessary friction. Integrating at the Master SID level will allow a single integration to cover all child SIDs, significantly simplifying the setup process for customers managing multiple environments. Scope Add Master SID authentication support to the CrowdStrike Falcon integration Enable automatic discovery/coverage of child SIDs under a Master SID Maintain backward compatibility with existing individual SID integrations Acceptance Criteria Customers can authenticate using a Master SID API key All child SIDs under the Master SID are accessible through the single integration Existing individual SID integrations continue to work without changes Tests passing / Documentation updated References PR: (If applicable) Related: Existing CrowdStrike Falcon integration
Linear 6 days ago
Feature
In Progress
Crowdstrike integration Master SID support
Summary Add Master SID-level integration support for CrowdStrike Falcon, allowing customers to integrate at a higher organizational level so that fewer individual integrations are needed, reducing customer friction. Background We currently have a CrowdStrike Falcon integration, but it operates at the individual SID level. Customers with multiple SIDs must configure each one separately, which creates unnecessary friction. Integrating at the Master SID level will allow a single integration to cover all child SIDs, significantly simplifying the setup process for customers managing multiple environments. Scope Add Master SID authentication support to the CrowdStrike Falcon integration Enable automatic discovery/coverage of child SIDs under a Master SID Maintain backward compatibility with existing individual SID integrations Acceptance Criteria Customers can authenticate using a Master SID API key All child SIDs under the Master SID are accessible through the single integration Existing individual SID integrations continue to work without changes Tests passing / Documentation updated References PR: (If applicable) Related: Existing CrowdStrike Falcon integration
Linear 6 days ago
Feature
Threat Connect Integration
Summary ThreatConnect integration needed Background [Context, problem being solved, or opportunity being addressed] Scope Deliverable 1 Deliverable 2 Deliverable 3 Acceptance Criteria Criterion 1 Criterion 2 Tests passing / Documentation updated References PR: (If applicable) Related: (If applicable)
Linear 6 days ago
Feature
Threat Connect Integration
Summary ThreatConnect integration needed Background [Context, problem being solved, or opportunity being addressed] Scope Deliverable 1 Deliverable 2 Deliverable 3 Acceptance Criteria Criterion 1 Criterion 2 Tests passing / Documentation updated References PR: (If applicable) Related: (If applicable)
Linear 6 days ago
Feature
Completed
Date Range Filtering - Vulnerabilities
Customers can pick a date range (in conjunction with other filters and search) that present all of the vulnerabilities that were either first seen or last seen (according to their choice) date range selected.
Dan Crawford 16 days ago
Feature
Completed
Date Range Filtering - Vulnerabilities
Customers can pick a date range (in conjunction with other filters and search) that present all of the vulnerabilities that were either first seen or last seen (according to their choice) date range selected.
Dan Crawford 16 days ago
Feature
Completed
LLM Service Fingerprinting Tool (Julius)
Julius is an HTTP probe-based tool for fingerprinting exposed LLM services and chat interfaces. It sends HTTP probes to targets and matches responses against YAML-defined rules to identify LLM hosting platforms, API endpoints, and chat UIs.
Dan Crawford 21 days ago
Feature
Completed
LLM Service Fingerprinting Tool (Julius)
Julius is an HTTP probe-based tool for fingerprinting exposed LLM services and chat interfaces. It sends HTTP probes to targets and matches responses against YAML-defined rules to identify LLM hosting platforms, API endpoints, and chat UIs.
Dan Crawford 21 days ago
Feature
Completed
Deprecate ProductBoard and redirect customers to Featurebase
Deprecate ProductBoard and redirect customers to Featurebase Security Decisions R-002: SRI Hash for Featurebase SDK — Risk Accepted Decision: SRI (Subresource Integrity) is intentionally omitted for the Featurebase SDK script (https://do.featurebase.app/js/sdk.js). Rationale: Featurebase manages their SDK on their CDN and updates it without notice. A static SRI hash would cause silent load failures on every vendor update (hash mismatch → browser refuses to execute script), effectively breaking the changelog widget for all users until we detect and update the hash. Mitigations in place: HTTPS transport (integrity in transit) Statsig feature gate (featurebase_widget_enabled) provides kill-switch Scoped JWT from broker (not Chariot platform token) — limits blast radius Auth-gated loading (widget only loads for authenticated users) Error handling prevents SDK failures from crashing the application Review date: Re-evaluate if Featurebase provides versioned/pinned SDK URLs or SRI hashes.
Linear 24 days ago
Feature
Completed
Deprecate ProductBoard and redirect customers to Featurebase
Deprecate ProductBoard and redirect customers to Featurebase Security Decisions R-002: SRI Hash for Featurebase SDK — Risk Accepted Decision: SRI (Subresource Integrity) is intentionally omitted for the Featurebase SDK script (https://do.featurebase.app/js/sdk.js). Rationale: Featurebase manages their SDK on their CDN and updates it without notice. A static SRI hash would cause silent load failures on every vendor update (hash mismatch → browser refuses to execute script), effectively breaking the changelog widget for all users until we detect and update the hash. Mitigations in place: HTTPS transport (integrity in transit) Statsig feature gate (featurebase_widget_enabled) provides kill-switch Scoped JWT from broker (not Chariot platform token) — limits blast radius Auth-gated loading (widget only loads for authenticated users) Error handling prevents SDK failures from crashing the application Review date: Re-evaluate if Featurebase provides versioned/pinned SDK URLs or SRI hashes.
Linear 24 days ago
Feature
Completed
Date Range Filter Vulnerabilities
Summary Create a filter that allows customers to search custom date ranges for First Seen or Last Seen This should work in conjunction with other filters and search. Customers will have to chose first seen or last seen. A calendar will allow customers to pick that start date and end date of a range. Result: customers can pick a date range (in conjunction with filters and search) that present all of the vulnerabilities that were either first seen or last seen (according to their choice) date range selected. If no vulnerabilities were found in the date range with the chosen filter and/or search term, customers should be informed that no results match their critera Match pre-existing UI paterns. Background customers consistently ask for date range filtering. Scope full delivery of date range filter on vulnerability page Acceptance Criteria users can create a date ranger filter on vulnerabilities page graceful fails Tests passing / Documentation updated
Linear 27 days ago
Feature
Completed
Date Range Filter Vulnerabilities
Summary Create a filter that allows customers to search custom date ranges for First Seen or Last Seen This should work in conjunction with other filters and search. Customers will have to chose first seen or last seen. A calendar will allow customers to pick that start date and end date of a range. Result: customers can pick a date range (in conjunction with filters and search) that present all of the vulnerabilities that were either first seen or last seen (according to their choice) date range selected. If no vulnerabilities were found in the date range with the chosen filter and/or search term, customers should be informed that no results match their critera Match pre-existing UI paterns. Background customers consistently ask for date range filtering. Scope full delivery of date range filter on vulnerability page Acceptance Criteria users can create a date ranger filter on vulnerabilities page graceful fails Tests passing / Documentation updated
Linear 27 days ago
Feature