Changelog

Have something to say?

Tell us how we could make the product more useful to you.

Add "First Seen Date" for Discovered Hostnames/Subdomains in Dashboard & CSV Exports

Currently, domain discovery displays active hostnames/subdomains but does not indicate when each asset was first observed as publicly accessible. It would be nice to have the visibility into when a domain or subdomain was initially discovered. This would help with tracking changes in asset exposure over time, identifying newly emerged or reappearing infrastructure, and supporting incident response.

kevin.cisan 20 days ago

💡 Feature Request

Integration with TeamDynamix

Enable a native integration between Halo Security and TeamDynamix to automatically create, update, and track tickets based on vulnerability and asset findings in Halo Security. This integration will streamline incident response, reduce manual effort, improve SLA compliance, and enhance cross-team collaboration by syncing security events with existing ITSM workflows in TeamDynamix. Use Case / Problem Statement: Security teams using Halo Security currently identify vulnerabilities and risks across their external attack surface. However, translating those findings into actionable, tracked tasks in TeamDynamix requires manual ticket creation and updates. This creates delays, increases the risk of miscommunication, and causes security findings to slip through internal processes or SLA requirements. Proposed Solution: Develop a bi-directional integration between Halo Security and TeamDynamix that includes: Automated Ticket Creation: When new critical or high vulnerabilities are discovered (configurable thresholds), automatically open a ticket in TeamDynamix with relevant context (affected asset, risk score, CVE, remediation steps, severity, reporter). Ticket Updates & Sync: Sync status changes from TeamDynamix back to Halo Security — e.g., when a ticket is acknowledged, in progress, or fixed — so Halo Security reflects current remediation state in dashboards and reporting. Field Mapping & Customization: Allow admins to map Halo fields to TeamDynamix fields (priority, category, assignment group, due dates, custom fields) and set rules for auto-updates. Comment & Attachment Sync: Pass comments in both directions to preserve context and audit trails. Trigger & Threshold Controls: Configurable triggers: by severity, asset criticality, vulnerability age, or custom tags to control when a ticket is created or updated. Benefits: Operational Efficiency: Reduces manual ticketing effort and frees security analysts to focus on remediation rather than administrative tasks. Improved Visibility: Development, operations, and IT teams get security findings directly in their workflows with appropriate context for faster remediation. Better SLA & Compliance Tracking: Automatically ensuring vulnerabilities enter formal remediation workflows with tracking and notifications improves accountability and SLA adherence. Consistent Audit Trails: Two-way sync preserves audit logs and remediation evidence across tools. Custom Workflows: Align security findings with existing TeamDynamix workflow rules and approval processes. Optional Advanced Enhancements: Bulk Ticket Operations for handling multiple findings at once. Dashboards & Metrics in TeamDynamix showing security metrics (e.g., open vulnerabilities by severity). Role-Based Permissions to control what data flows between systems. Example Workflow: Halo Security discovers a new critical vulnerability on a client-facing asset. Halo triggers the integration and creates a new ticket in TeamDynamix with all relevant details. The IT team picks up the ticket in TeamDynamix and begins remediation. Status updates and comments in TeamDynamix sync back to Halo for centralized reporting. Once remediated, the ticket closes in TeamDynamix, and Halo marks the finding as resolved.

Brady Seiberlich About 1 month ago

💡 Feature Request

Jira Integration at Partner (Parent) Account Level

As a partner managing multiple child accounts, we would like the ability to configure the Jira integration at the parent account level. Currently, the integration must be set up individually per child account, which can complicate centralized issue tracking. This feature would allow events and scan findings from child accounts to generate Jira tickets through a single integration configured on the parent account. This would be a valuable addition for resellers and MSSPs who require unified alerting and ticket management across their customer base.

Luke Warren About 1 month ago

💡 Feature Request

Need More Votes

Align Target Risk Meter Color With Severity Context

Update the Target Risk Meter color logic so that targets with only low-severity findings (e.g., Severity 3) are visually represented as low risk, with a color that reflects minor exposure rather than a misleading “perfect/fully healthy” state. Current Behavior A target with a Severity 3 vulnerability (example: TLS 1.1 enabled) may have an overall risk score of 100. Based on current thresholds: Low risk: 0–299 Medium risk: 300–599 High risk: 600+ The target is marked green on the risk meter, visually implying no meaningful risk, even though an actionable vulnerability exists. Problem The current green risk meter conflates “low risk” with “no risk.” Customers interpret a fully green meter as “nothing to address,” which reduces visibility of: Minor but actionable hygiene issues (TLS 1.1, weak ciphers, minor headers, legacy protocols). This causes confusion when: An issue list clearly shows open vulnerabilities But the target visually appears “perfect” Requested Enhancement Red - High Risk Target Orange - Medium Risk Target Yellow - Low Risk Target Green or another color - Fully Clean Target

Maurizio Ruvolo 2 months ago

1

💡 Feature Request

Need More Votes

Integration with Salesforce Commerce Cloud

Description: Requesting a native integration between Halo Security and Salesforce Commerce Cloud (SFCC) to automatically ingest assets, URLs, and environments associated with SFCC stores. The integration should enable users to authenticate via API credentials or OAuth, detect staging and production storefront endpoints, and continuously monitor for exposed assets, misconfigurations, and vulnerabilities tied to SFCC deployments. Business Justification: Automating discovery and risk monitoring for SFCC domains would streamline onboarding, reduce manual target creation, and provide better visibility into managed SaaS environments that host critical public-facing applications. Requested Capabilities: Secure connection via SFCC API (Client ID/Secret or OAuth) Automated discovery of storefronts, sandboxes, and production URLs Tagging of discovered assets by organization and environment

Gerry - AdminA Dalton 3 months ago

💡 Feature Request

In Progress

Integration with Linear Issue Tracking

Description: Request to add a native integration between Halo Security and Linear (https://linear.app/) to streamline vulnerability management workflows. When Halo Security detects a new issue or vulnerability, the integration should automatically create a corresponding Linear issue with key details (target, severity, summary, remediation notes, and a link back to the Halo finding). Status updates and closures in Halo should sync back to Linear, ensuring both systems stay in sync. Use Case: Customers and internal teams using Linear for engineering and security operations can manage vulnerabilities directly from their existing workflow without manual duplication or exports from Halo. Requirements: Create Linear tickets automatically from new Halo issues based on configurable severity or tag filters Sync issue status, notes, and remediation updates bi-directionally Allow mapping of fields between Halo and Linear (e.g., severity → priority) Support linking back to the Halo Security finding from Linear Include authentication and workspace configuration options within the Halo Integrations settings Value / Impact: Eliminates manual ticket creation for vulnerability triage Reduces missed issues and improves remediation tracking Increases Halo’s integration coverage and appeal for teams already using Linear

Nikhil Amin 3 months ago

1

💡 Feature Request

Include Event Details in Alert Emails

I created some new Event Rules which send emails if a condition is met/triggered. Would it be possible to included the following in those emails to get some more information, more efficiently? Subject Event Rule I created Both Target full name and nickname I’ve given some targets that are more important to us nicknames so I can locate them in the list easier, but since we have targets with very similar/repeating domains, it would be nice to see the exact domain AND nickname rather than primarily being the nickname.

Michael DiMambro 3 months ago

💡 Feature Request

Include “Organizations” Hierarchy in Executive Summary PDF Report

Description: The Executive Summary PDF currently provides a consolidated view of security posture across assets, issues, and trends. However, it does not include the Organization’s hierarchy, which visually represents the relationship between parent and subsidiary organizations. Requested Enhancement: Enhance the Executive Summary PDF (example: Report Link) to include the Organization’s hierarchy as an optional section. This section should visually display the same structure shown in the Organizations view and summarize key metrics for each organization. Proposed Layout: A new “Organizational Hierarchy Overview” section within the Executive Summary PDF. Include the hierarchy tree (visual diagram) or a summarized table view. Each node/organization should list: Organization Name Risk Score Total Assets Open Issues Count Use Case / Rationale: Including the Organization’s hierarchy in the Executive Summary PDF provides executives and auditors with a top-down perspective of the organization’s security structure. This allows for: Improved visibility into group-level relationships and risk ownership. Clearer context during executive reviews and audit reporting. Consolidation of visual and quantitative data in a single exportable report. Acceptance Criteria: Add an optional “Organizations Hierarchy” section to the Executive Summary PDF. Section displays a visual tree or table summarizing organizational relationships. Include relevant metrics (risk score, assets, issue count). Respect the same filtering and scoping rules as the Executive Summary. Ensure formatting aligns with the current report style and branding.

Justin Heffernan 3 months ago

💡 Feature Request

Add Export Option for “Organizations” Hierarchy View

URL: https://app.halosecurity.com/user/security/org/?id=xxxxxxx Description: The Organizations hierarchy view provides a visual representation of relationships between parent and subsidiary organizations. However, there is currently no option to export this hierarchy for reporting or documentation purposes. Requested Enhancement: Add an “Export” option to the Organizations page that allows users to export the full hierarchy view, including all child nodes, in one or more of the following formats: CSV (list format: Organization Name, Parent Organization, Risk Score, Assets, Issues) PDF or PNG (visual export of the hierarchy graph) Use Case / Rationale: Security and compliance teams often need to share organizational structure reports or include them in audit documentation. Having an export option would: Enable easier reporting for customers managing multiple entities. Allow visual documentation of relationships between organizations. Support external collaboration without requiring direct platform access. Acceptance Criteria: “Export” button available on the Organizations hierarchy page. Option to export as CSV and/or image (PDF/PNG). CSV includes all nodes and their parent-child relationships. Export respects applied filters and search parameters.

Justin Heffernan 3 months ago

💡 Feature Request

Integration with Microsoft Dynamics 365

Enable Halo Security to integrate seamlessly with Microsoft Dynamics 365, allowing vulnerability and asset data to flow directly into Dynamics for centralized tracking, reporting, and remediation workflow management. This integration ensures security findings are visible to business and IT teams within their existing CRM/ERP environment, improving collaboration, response time, and compliance tracking.

Charles Lam 6 months ago

💡 Feature Request

Completed

API Access to Retrieve Scanner Source IPs Used in Specific Scans

We would like to programmatically identify the exact IP addresses used by Halo’s scanning engines during each vulnerability scan. While the UI currently shows scanner IPs per scan under the “Scan Details” section, there is no API endpoint available to retrieve this information automatically. Our team uses Tines for workflow automation and has integrated Halo Security’s API to pull scan data. However, without access to the scanner IPs via API, we’re unable to automatically correlate scan activity with logs and firewall data. This feature would help streamline automation, improve security event correlation, and reduce time spent manually checking scan data in the UI.

Dany - AdminA Walker 7 months ago

2

💡 Feature Request

Need More Votes

Enable SMS/Text Alerts for New Vulnerabilities

Implement the ability for users to receive SMS/text message notifications when new vulnerabilities are detected. Users should be able to configure this alert type in their notification settings, specify a phone number, and optionally filter alerts by severity level or specific targets. This feature would enhance real-time awareness and incident response outside of email-based workflows.

Matt Lyons 7 months ago

1

💡 Feature Request