

FAQ
Deployment is instant — a few minutes to spin up inside a Docker host and trigger with a one-time ephemeral curl command. From there, HybridSenseAI autonomously enumerates at roughly ~40 seconds per IP/Host (internal) or subdomain (external/OSINT). That means:
A standard /24 network segment completes in under 2 hours
A 10K IP/Host/Subdomain environment completes in just over a week
Unlike static scanners, HybridSenseAI doesn’t stop at enumeration. It operates as a fast, continuous, and unlimited protection layer, constantly updating and defending without the need for manual restarts or scheduling.
This ain’t your grandma’s pentesting platform. We started with simple design principles:
No persistent agents
100% coverage
Safe to run in production
1-click user experience
No cheating, scripting, or humans
Those principles are manifested in our differentiation such as:
Chaining kill-chain action, attacks, and findings
Providing environmental context, which leads to true prioritization
Speed to TTV, and ROI gains momentum
No training, no tuning, no configurations…there is zero maintenance
This is Autonomous Threat Detection as a Service
We thoroughly research the safety of any known exploit (e.g. denial of service vs. buffer overflow vs. directory traversal, etc.), and prove it. Any and all exploitations of vulnerabilities are continually and thoroughly tested in our own cyber range against a wide range of operating systems and applications.
If we determine the exploit is 100% safe, HybridSense AI™ will exploit it automatically
If we determine the exploit is 100% safe but may change the environment, the exploit is on by default but can be disabled by the user in the Advanced Config
If we determine the exploit is < 100% safe, a user must deliberately authorize (turn on) the exploit in the Advanced Config–i.e., it’ll be off by default
Additionally, certain exploits that cause changes to the environment such as writing data to a system, are configurable in the advanced options for the customer to disable.
Regardless, HybridSense AI™ will enumerate and validate where possible to accurately determine if a potential exploit is possible. This will show as an “unconfirmed” weakness and consequentially, no proof will have been collected.
No. Unlike VM & BAS tools, HybridSense AI™ does not require an agent or credentials which—when providing reams of vulnerability lists—falsely presume host and privileged access.
HybridSense AI™ operates like an unauthenticated attacker (black box), enumerating and exploiting what it finds to build a true attacker’s perspective of your risk.
If you’d like to see how far an attacker can get when compromising a credential within your domain, you can inject a credential (up to 5) into a HybridSense AI™ operation to be leveraged as an attacker would and see full path and proof of what risk those particular credentials pose to your environment.
Whether injected, discovered, or cracked, HybridSense AI™ has two goals after obtaining a credential:
Manoeuvre Laterally
Enumerate Active Directory for attack paths that lead to more credentials or more privileged access on a host
Enumerate hosts for elevated permissions and then dump stored credentials in memory, the registry, and other common locations
Obtain Sensitive Information
Enumerate all endpoints in a network, looking for file shares, databases, and hosts that it can access
Laterally move and repeat
There are several use-cases where it is useful to understand how far an attacker may get after compromising a credential:
Regular User– Attackers have many common paths to compromise a regular user through phishing, breach data, or poor security hygiene. Whether compromised or deliberate (such as with an Insider Threat), ensuring further compromise is not possible is critical based on the highly demonstrated likelihood of occurrence.
Service Account – Service accounts are a high-value target for attackers because they are often over-privileged and multi-factor authentication is rarely enabled. This is the perfect scenario for an attacker to obtain the keys to your kingdom. Service accounts are often obtained after a vulnerability is exploited on an out-of-date application. Injecting service account credentials can help you understand the risk in one of those services being compromised.
