BreachLock Breach360 v2.1.0 Release: More Visibility and Control for Autonomous Pentesting

Running autonomous penetration testing for security validation at scale means tracking more than findings. Teams also need to know what was tested, who had access, and what (if anything) changed along the way. With the Breach360 v2.1.0 release, BreachLock introduces a set of improvements designed to make validation easier to monitor, govern, and prove.

The highlights of this release are a centralized audit trail sealed into a signed chain, new preflight checks for web engagements, and expanded deployment visibility, giving teams more control and accountability before, during, and after an engagement.

Why Visibility and Governance Come First

As validation programs grow, the work spreads across more deployments, users, organizations, and AI-assisted workflows. Without a clear view of that activity, teams lose time tracking down what was tested, troubleshooting access problems mid-engagement, and pulling together evidence for audits.

Breach360 v2.1.0 addresses this by bringing deployment context, access controls, and activity records into one place, and by catching common access and connectivity problems before testing begins.

What’s New in Breach360 v2.1.0

1. Deployment Visibility and Control: Deployments are now easier to monitor and control. Teams can see mapped networks and their associated engagements, along with telemetry, logs, and deployment history. A deployment can also be locked so it stops accepting new engagements, and deployment views now share a consistent interface.

2. Account, Organization, and Access Management: Account, team, and organization controls are now clearer and easier to manage.

• Session control: Account settings give users more visibility and control over their active sessions.
• Role-based invitations: Users can invite others with an assigned role, and invited users receive an invitation to join the organization.
• Organization policies: Organization settings provide organization-level controls for defining policies.
• Cross-organization access: Users can be added as members of another organization with a dedicated role, giving internal users who work across multiple organizations controlled access based on that role.

3. Centralized Audit Trail: The new audit trail provides a complete, exportable record of activity within the organization. It records organization and user activity in one place, and events are sealed into a signed chain to help preserve the integrity of what was recorded. Teams can export the audit trail as evidence when required.

4. AI Activity Transparency: A dedicated view now shows how AI models interact with platform data and with other models. Teams can also view AI activity by individual model version.

5. Expanded Domain Discovery: Domain Discovery now provides broader visibility into the external attack surface. Coverage of externally exposed assets and potential entry points has expanded, and discovery of previously unknown or overlooked external assets has improved.

6. Improved Preflight Checks for Web Engagements: Web engagement access issues can now be identified before the engagement begins. Breach360 warns users when authentication fails for an asset and prevents an engagement from proceeding when an in-scope asset is unreachable. Teams can resolve access and connectivity issues upfront instead of discovering them after testing has started.

7. Shared Engagement Presets: Engagement presets can now be shared across the organization, and shared presets can be used to configure engagements through automations. Creating, managing, and using presets is also simpler.

8. Advanced Search Capabilities: Advanced Search is now available across the portal. Users can search and filter across attributes of platform objects such as engagements and deployments, which makes specific objects and information easier to find.

9. Licensing Improvements: The License page has an updated design, with clearer visibility into licensing quotas and the credits available for the current term.

10. Scan Intensity Options: Scan execution is now more predictable across three intensity levels.

• Polite: Slower, more resource-conscious scanning.
• Normal: The default option, balancing scan speed and resource impact.
• Accelerated: Faster scanning, with a higher potential impact on network-enabled services.

Dynamic host timeout behavior now adjusts based on the selected intensity.

Key Benefits for Security Teams

The Breach360 v2.1.0 release delivers several practical benefits.

• Clearer visibility into deployments, engagements, and external assets
• Stronger access controls across teams and organizations
• Exportable, integrity-protected audit evidence
• Fewer engagements disrupted by authentication and connectivity issues
• More consistent, predictable validation workflows

With deployment, access, and activity information in one place, teams spend less time reconstructing what happened and more time acting on results.

Final Thoughts

Breach360 v2.1.0 gives security teams more visibility into their autonomous penetration testing engagements and more control over who can do what on the platform. With a signed audit trail, AI activity visibility, and improved preflight checks, teams can run engagements with more predictability and produce evidence when it’s needed.

This release is another step toward security validation that is continuous, accountable, and easier to manage at scale.

Talk to an offensive security expert today to see if Breach360 is the right fit for your offensive security goals.

Author

BreachLock Labs