Horizon3 and Torq Publish Brief on Integrated Attack Path Remediation and Verification
A new joint solution brief details how Horizon3’s NodeZero exploitability findings connect with Torq’s SOC workflows to orchestrate fixes and verify closed paths.

Key points
- Horizon3 and Torq published a joint solution brief describing their integrated workflow for security remediation.
- The integration uses NodeZero to identify proven attack paths and Torq to orchestrate automated fixes across IT tools.
- Teams can automatically retest environments after remediation to verify that specific exploit paths are fully closed.
Horizon3 and Torq have published a joint solution brief describing an integrated workflow that connects autonomous penetration testing with automated security operations. According to the document from Horizon3.ai, the partnership allows security teams to move beyond simple vulnerability lists. Instead, the solution focuses on evidence of exploitable attack paths, orchestration of fixes, and automatic verification that those paths are closed.
The core of this integration relies on Horizon3’s NodeZero platform, which performs autonomous pentesting from an assumed-breach position. NodeZero safely tests live environments by chaining together vulnerabilities, misconfigurations, and credential weaknesses. It maps reachable attack paths across network, cloud, identity, and Active Directory systems. This provides security teams with concrete proof of which weaknesses are actually exploitable in their specific infrastructure.
Context and Background
Torq brings these NodeZero findings directly into SOC workflows to enable coordinated action. The platform enriches the data with asset ownership details and attack-path impact scores. This context allows teams to prioritize remediation efforts on the specific weaknesses that NodeZero has demonstrated are reachable. According to the brief, this connection bridges the gap between discovering a theoretical flaw and acting on a proven risk.
The integration also links remediation actions with scoped verification pentesting. Torq can orchestrate responses across identity, endpoint, cloud, collaboration, and ITSM tools. After these automated actions are taken, the system launches a targeted retest. This retest confirms whether the specific attack path has been successfully closed. If the path remains exploitable, the finding returns for another remediation pass, supporting a continuous cycle of hacking, fixing, and verifying.
Who Is Affected
Security teams that rely on traditional vulnerability scanners often struggle with noise and false positives. This solution targets organizations that need to validate exploitability before spending resources on fixes. By focusing only on proven attack paths, teams can direct remediation more efficiently across identity, endpoint, and cloud environments. The brief illustrates how NodeZero findings flow into Torq Hyperautomation, Socrates AI SOC Analyst, and Case Management modules.
The workflow is designed for continuous security operations rather than one-time assessments. Verified findings are resolved in Case Management, while unresolved issues loop back for further action. This approach helps contain exposed credentials by triggering rotation and session revocation followed by verification. The joint brief emphasizes that this method supports a continuous hack, fix, verify cycle.
What should you do?
Security leaders should evaluate whether their current workflows distinguish between theoretical vulnerabilities and proven exploit paths. Teams using Horizon3 or Torq should review the joint solution brief to understand the integration capabilities. Organizations should check if their SOC tools can orchestrate remediation across identity and cloud platforms automatically. Finally, verify that your current process includes a verification step to confirm fixes actually close the attack path.
What to do and how to stay safe
- Review your current vulnerability management process to see if it validates exploitability before prioritizing fixes.
- Check if your SOC platform can orchestrate remediation actions across identity, endpoint, and cloud tools automatically.
- Ensure your workflow includes a verification step that retests environments after remediation to confirm paths are closed.
Step-by-step guide: Social Engineering Warning Signs and How to Respond
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.


