Terra fits when
You want AI red teaming of LLM apps and agents, protection as WAF or firewall rules, or a single-tenant or air-gapped deployment.
ShieldProbe and Terra Security
Terra Security and ShieldProbe: compare the review, the protection and the retest.
Both pair AI testing with human review, and both can protect a proven exploit while the code fix is prepared. Terra does it with WAF and firewall rules. ShieldProbe Defend, sold separately, does it inside your Node.js application, starting in log-only mode.
How Terra and ShieldProbe compare
Terra Security offers agentic pentesting with human pentesters on the loop, and Prevention rules for confirmed exploits. Here is how each step compares.
Scroll the table sideways to compare both options. You can also focus it and use the arrow keys.
| Compared on | Terra Security | ShieldProbe |
|---|---|---|
| What it tests | Web and internal application testing, including authentication flows, business logic and APIs, plus external and internal network testing and AI red teaming of LLM applications, copilots, MCP servers and agents. | Web apps, APIs (REST, GraphQL, SOAP), networks and servers, internal or external. Black-box for every target; grey-box with your test accounts for web apps and APIs. |
| Findings and review | Pentesters validate exploitability before a finding is confirmed, and a human pentester makes the call at critical decision points. Every agent action and human decision is logged. | AI authors each finding and a named consultant approves it before you can see it. Every finding carries the request, response and impact, so your team can reproduce it. |
| Fixes and retests | Findings carry remediation guidance, and teams can open an automated pull request; with source code connected, Terra scopes a remediation plan to the affected files. A retest re-runs the original attack and records pass or fail. Tickets go to Jira, Linear or ServiceNow. | Retests of confirmed findings for 12 months under your engagement terms. Fix drafts the code change in VS Code or Visual Studio (beta) for your developers to review. |
| Application protection | Prevention, announced 3 August 2026, checks whether your existing controls already stop a confirmed exploit. If not, it generates a WAF or firewall rule, tests it against the exploit, and your security team applies it. | Defend, sold separately, adds protection rules for supported findings inside your Node.js app. It starts in log-only mode and blocks only once you turn enforcement on. Ownership flaws such as IDOR are logged, never blocked: they need the code fix. |
| How it runs | Agentic testing with a human on the loop, as multi-tenant SaaS, a single-tenant instance in your own AWS, Azure or GCP account, or on-premises and air-gapped. Terra says continuous monitoring surfaces new findings within hours of a code change. | A scoped pentest run from our own attack infrastructure. External targets need nothing installed; internal targets are reached through a small connector that needs no admin rights. The report arrives in 48 hours for agreed scope once access is ready. |
Plan a side-by-side test
Use the same targets and test accounts you gave the other tool. We agree scope and access with you before testing starts.
Which fits your team
ShieldProbe fits when
You want protection inside your Node.js application rather than at the WAF, code fixes drafted in your developers’ IDE, and retests for 12 months under your engagement terms.
What happens after the report
Each module takes a finding one step further.
Assess
A pentest of your web apps, APIs, networks and servers. A named consultant approves every finding, and each one comes with evidence your team can reproduce.
Explore AssessDefend
Protection for supported findings inside your Node.js app, sold separately. It starts in log-only mode and blocks only when you turn enforcement on. Ownership flaws are logged, never blocked.
Explore DefendFix
A code change drafted from the actual attack, in VS Code or Visual Studio (beta). Your developers review it and raise the pull request.
Explore FixContinuous
Developer preview. Selected tests run on the repository events you enable, so each change is tested as it ships.
Explore ContinuousCommon questions
Does Terra already block proven exploits?
Yes. Terra Prevention generates a WAF or firewall rule for a confirmed exploit, tests it against that exploit, and your security team applies it. ShieldProbe Defend works inside your Node.js application instead, sold separately and starting in log-only mode. Neither replaces the code fix.
Do both have people reviewing findings?
Yes. Terra describes pentesters validating exploitability before a finding is confirmed, with a human on the loop at critical decision points. In ShieldProbe Assess, a named consultant approves each finding before you can see it, and the platform will not release a finding without that approval.
Can we run ShieldProbe alongside Terra?
Yes. Both test web applications, APIs and internal and external networks, so you can run them on the same scope and compare findings, protection and retests. Terra’s AI red teaming of LLM apps has no ShieldProbe equivalent.
Do we install anything?
Not for external targets. Internal targets are reached through our connector or another access path agreed during scoping. Defend, if you add it, runs as an SDK in your Node.js application.
Sources
Details about other products and standards come from the public sources below, reviewed on 20 October 2026 unless dated. If anything has changed, tell us and we will correct it.
- Terra Platform: targets, human-on-the-loop review and continuous testing (reviewed 27 October 2026)
- Terra: web application and API testing (reviewed 27 October 2026)
- Terra: Prevention launch, WAF and firewall rules for confirmed exploits (3 August 2026) (reviewed 27 October 2026)
- Terra: remediation workflow, pull requests and retests (5 July 2026) (reviewed 27 October 2026)
- Terra: deployment and control options (reviewed 27 October 2026)