In Review

In Progress

Completed

Main Roadmap

When submiting a ticket through “Open Ticket” there is no option to add screenshots or post more comments :) In here:<a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://app.halosecurity.com/user/support/ticket?id=1049574">https://app.halosecurity.com/user/support/ticket?id=</a>xxxxxx

Screenshots in tickets

Wojciech Iwański

Request to enable automatic delivery of an Executive Summary Report via email. This report would contain only high-level security metrics such as overall risk score, number of scanned assets, vulnerability counts, and risk trends. This option would provide us with a convenient way to share security posture insights with executive teams.

Automated Delivery of Executive Summary Reports via Email

Geoff Augenstein

The current Technology section lists technologies, versions, risk ratings, and CVEs per target, but does not record when a specific technology was first detected. As a result, it can be hard to determine whether a technology is newly introduced or has been present for some time.

Track and Display “First Detected Date” for Identified Technologies

Derek Nasfell

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.

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

Kevin Cisan

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.

Jira Integration at Partner (Parent) Account Level

Luke Warren

It would be great to have a dashboard for ASV scans that displays all domains or IPs or Targets that have passed/Failed the scan, along with their next due date including reminders.

PCI tracking on a per-target basis

Khalid Shaikh

We would like more flexible monthly scan scheduling options. Currently, selecting "monthly" triggers scans every 30 days, which can cause schedule drift and potentially skip a month due to varying month lengths. We would like the ability to schedule scans based on specific calendar patterns, such as:<ul><li>The 1st of the month</li><li>The 2nd Tuesday of each month</li><li>The last Friday of the month </li></ul>This feature would help ensure consistency in scan timing and better alignment with internal reporting and compliance cycles.

Support Custom Monthly Scan Scheduling

Chris Koelbl

The instance details provide limited information on target scan findings: https://app.halosecurity.com/user/security/issue/?targets=all&amp;id=1138111 For example, the 'Link Using Non-HTTPS Connection' issue lists the HTTP link but does not include the actual location. The actual location can be found in the 'Links' section under 'Websites.' https://app.halosecurity.com/user/security/website/link/list?targets=all Clicking the magnifying glass next to a link in the ‘Links’ section opens a modal with additional details, including the 'Actual Location.' For this issue, it would help if a link to the 'Links' section was available, next to the magnifying glass in the 'Instances' section. If you have any questions feel free to reach out!

Add new link to instances section for more details

Todd Gallant

Customers need a way to centrally manage integration credentials (Client IDs and Client Secrets). Today, when a credential such as an Azure Client Secret is rotated, it must be manually updated in every integration where it is used. This becomes difficult when the same Azure application is used across multiple integrations, as there is currently no easy way to identify which integrations share the same Client ID.Proposed Enhancement:Add a centralized credential management section within the Company Settings page of the platform.Location:<a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://app.halosecurity.com/user/account/company/">https://app.halosecurity.com/user/account/company/</a>This new section would allow administrators to securely store and manage Client IDs and Client Secrets used by integrations.When configuring or editing integrations, users would be able to select an existing credential from this centralized list instead of manually entering the Client ID and secret each time.Access Control:<ul><li>This section should only be visible within the Company Settings page.</li><li>Access should be restricted to Admin users only.</li><li>Client Secrets should remain masked/encrypted in the UI.</li></ul>Key Benefits:<ul><li>Simplifies credential rotation (e.g., Azure client secret rotation).</li><li>Eliminates the need to manually update credentials across multiple integrations.</li><li>Reduces configuration errors when secrets are rotated.</li><li>Provides visibility into which credentials are being reused.</li></ul>Additional Suggested Capability:Provide a simple export or table view showing:<ul><li>Integration Name</li><li>Associated Client ID</li></ul>This would allow administrators to quickly identify which integrations rely on a specific Azure application when credentials are rotated.Example Use Case:A customer recently rotated a secret on an Azure application used across 15 integrations. Because the platform does not show Client IDs in a centralized way or allow credential reuse, the team had to manually open and update each integration individually. A centralized credential store would allow the secret to be updated once and automatically applied to all integrations using that credential.

Centralized Client ID / Secret Management for Integrations (Admin Only)

Gerry - AdminA Dalton

URL: <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://app.halosecurity.com/user/security/tags/list?targets=all">https://app.halosecurity.com/user/security/tags/list?targets=all</a> Add the ability to export the list by filtered results.

Add Export Option for Tags

Rece - AdminA Beardsley

We have several Hundred Targets, and often Clients will come to us with their own reports. Also, different teams are responsible for resolving issues on specific targets but not others. Is it possible to tag specific issues on targets so we can say “This is reported By Client X and should be tracked” or “This is also found on Security Scorecard, so fixing this is a double dip”

High Priority

Ability to Tag issues on Targets

An Anonymous User

Integrate with Fortinet to pull in/retrieve records.

Integration

Integration with Fortigate

Dominic Erickson

An integration with Axonius would help up with asset management. This platform allows us to discover, track, and manage all assets across our IT and security environment. Reference: https://www.axonius.com/

Integration with Axonius

Richard Wainwright

For domains parked at a registrar (e.g. GoDaddy), please give us some way to automatically/default tag those targets. That way we can keep an eye on them in case a site does pop up at those domains.

Support auto-tag or default-tag for parked domains

Tom Harold

For environments using Meraki-managed networks, public IPs and routes can change due to DHCP, uplink failover, or SD-WAN policies. Currently, such changes must be manually synced into Halo. With a Meraki API integration, Halo could automatically stay up to date on this.

Integration with Meraki

Nick Bernardi

Description: Request to add a native integration between Halo Security and Linear (<a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://linear.app/">https://linear.app/</a>) 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:<ul><li>Create Linear tickets automatically from new Halo issues based on configurable severity or tag filters</li><li>Sync issue status, notes, and remediation updates bi-directionally</li><li>Allow mapping of fields between Halo and Linear (e.g., severity → priority)</li><li>Support linking back to the Halo Security finding from Linear</li><li>Include authentication and workspace configuration options within the Halo Integrations settings</li></ul>Value / Impact:<ul><li>Eliminates manual ticket creation for vulnerability triage</li><li>Reduces missed issues and improves remediation tracking</li><li>Increases Halo’s integration coverage and appeal for teams already using Linear</li></ul>

Integration with Linear Issue Tracking

Nikhil Amin

Integrate with telegram for event/alert triggers. Messages could include critical details like: <ul><li>Target affected</li><li>Issue title and severity</li><li>Scan name or time</li><li>Link back to the Halo Security dashboard</li></ul>

Integration with Telegram

Gökalp Erol

We use Halo to meet our PCI-DSS security requirements, which include storing a quarterly report on our PCI scan status. However, we don’t have a way to schedule the report within Halo, so we have to create a ticket outside of Halo reminding someone to go into Halo and pull the report. Seems this should be part of the PCI compliance process within Halo: send me a quarterly executive summary.

Scheduled executive report

SSO/SCIM authentication/provisioning provides a better security posture for organization to be able to central accounts with vendors when users/employees come and go. Halo, as a cyber security company, should provide support for this.

Need to start supporting SSO/SCIM SAML Authentication

Spiro

Could you please increase the issue report limit from 50 to 100 targets? We typically need to report on 80-100 targets. Thank you.

Increase Issue Report Limit to 100 Targets

Tobey Fu

Enable adjustable columns on the Domains (Seeds) page to allow users to display associated tags, making it easier to correlate domains with discovery automation and asset grouping.Page / Area AffectedDomains (Seeds) page<a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://app.halosecurity.com/user/settings/seeds/domains/">https://app.halosecurity.com/user/settings/seeds/domains/</a>Problem StatementUsers can create automation rules that apply tags to domains and their discovered assets. However, there is currently no way to see which tags are associated with which domains directly on the Domains page. This makes it difficult to:<ul><li>Verify automation behavior</li><li>Quickly understand domain-to-tag relationships</li><li>Manage discovery and scoping at scale</li></ul>Proposed EnhancementAdd adjustable/configurable columns to the Domains page, similar to other list views in the platform, including (at minimum):<ul><li>Tags (multi-value column)</li><li>(Optional, future) Discovery status, asset counts, last discovered date</li></ul>Users should be able to:<ul><li>Enable/disable columns</li><li>Add a Tags column to view which tags are associated with each domain</li></ul>User Value / Impact<ul><li>Faster validation of discovery automation</li><li>Clearer mapping between domains and asset groups</li><li>Reduced manual cross-checking between domains, targets, and tags</li><li>Better scalability for customers with large discovery footprints</li></ul>

Add Adjustable Columns (Including Tags) to Domains Page

URL: <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://app.halosecurity.com/user/security/events/list">https://app.halosecurity.com/user/security/events/list</a> Currently, you have to click into an event to figure out the timestamp of the event or hover over the date to know the time that the alert occured. We need a column available for a timestamp.

Add Timestamp Column within Event Summary

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.

API Access to Retrieve Scanner Source IPs Used in Specific Scans

Dany - AdminA Walker

An integration with PagerDuty would be helpful to feed Halo Security alerts in case of a risk issue being detected.

Integration with PagerDuty

Sean Noriega

While I realize that assets don’t have all of the properties that a target has (once scanned), candidate assets do a have a lot of properties that could be used to filter.Why? We use a large collection of target filters to auto-tag targets for purposes of GRC assignments (who gets the call when a site is vulnerable). We have a lot of business knowledge encoded into these filters.But those filters don’t assist us in finding new assets that should maybe be targets. I have to look at the target filter, then manually search through the discovered asset list for new things that might need to be scanned. Much like there is a “view N targets” button when looking at the Target Filter’s “Matches” section, I wish there was a “view N assets” button to look at what assets match this filter.

Allow target filters/actions to also apply to assets

Please create an operational status page for Halo Security. We are currently working on an ISCP document, and I believe it will be beneficial in the event of system downtime.

Status Page

We would really appreciate if you consider this feature request. The reason i am requesting this feature is because of the client we have onboarded and they have around 70 TLDs and 300 subdomains and they request us to submit scan results every week for every single subdomain. Basically they want a seperate security report for each target. Three points that will actually help an MSSP were:<ol><li> Automation of Report Generation via Workflow, API or filter which ever is best and easy to use.</li><li>There need to be option to create a folder so that these auto generated reports will directly go to that specific folder.</li><li>Once reports have been added to their respective folders there need to be an option to download these reports through a API Call.</li></ol>If these features can be added this will make MSSP live easier and tension free.

Automation for Report Generation

Hi Team, I would like to get the command used to get the result in an instance in the API response too. API: '<a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://api.halosecurity.com/api/v1/issue/instance.json">https://api.halosecurity.com/api/v1/issue/instance.json</a>' In response of this API, I would like to get the command used too. Please refer to the attached screenshot for a better understanding of requirement. <img src="https://fb-usercontent.fra1.cdn.digitaloceanspaces.com/0191a186-2ac2-73f2-893d-02b305cba865.png" data-width="100%" data-align="left">Thank you