AI agents investigate every alert, add context, and prepare cases for response, on a full-stack SecOps platform that captures and correlates all your security data.
Cloud-based SIEM platform providing visibility across all your data sources
Every alert investigated, with a verdict and the evidence behind it
Manage your external footprint, publicly available data, and Dark Web leaks
Log management and threat detection across any of your log sources
Get ultimate assurance that your environment is free from threat actors
Fully featured distrubuted NDR for on-premises and public cloud environments
A SecOps platform purpose-built for industrial and OT environments
Integrated endpoint agent providing deep visibility, response and forensics
Deploy honeypots and honeytokens and stay ahead of threat actors
24x7 security operations from our Australian SOC. AI investigates every alert, and experienced analysts validate findings and contain threats around the clock.
Eyes-on-glass SOC and continuous threat hunting
24x7 managed detection and response across endpoint, network, cloud, identity, and log sources
AI investigations and 24x7 MDR on the Microsoft Sentinel you already own
Quickly recover from cyber attacks and breaches
Security Score, risk register, CISO program and reporting from live data
Fake sites, apps and accounts, leaked code and dark web exposure, taken down for you
AI agents map, watch and test your attack surface around the clock
ThreatDefence is the only SecOps as a Service company providing broad coverage across your entire technology stack with evidence-based security.
We provide security teams with full-stack SecOps infrastructure – you get deep visibility from day one, gain control over your security data, and get access to a comprehensive set of ready-to-use tools, detections, workflows, playbooks and scenarios.
24x7 SOC, Continuous Monitoring, Threat Containment and Incident Response
Expert hunters and AI agents find attacker activity your alerts missed
Leverage our Cyber Range to train defenders based on real-world scenarios and simulations
OT and industrial cyber security services for critical infrastructure
Monitoring, evidence and a 24×7 SOC in one platform
Compliance monitoring, evidence and board reporting
Privacy Act reform impacts, obligations, and practical security considerations
Monitoring and compliance support for critical infrastructure environments
A practical guide to securing critical infrastructure with continuous monitoring
A practical buyer’s guide for schools evaluating SIEM and SOC services
A practical guide to selecting the right SIEM and SOC service for local government
Articles on security operations, AI and compliance
Events, awards and company news
Read what our customers say about us
Solution briefs and datasheets
How we keep your data secure
Technical support and knowledge base
Guides, case studies, and advisories in one place
How AI agents investigate alerts and run security operations
Free ebook: a practical guide to adopting an AI SOC platform
A practical guide to incident response and digital forensics
Where SOAR playbooks fit and where AI agents take over
Free ebook: modern security operations with Microsoft Sentinel
How the framework is structured and what changes from the Essential Eight
How an attack unfolds stage by stage and how to detect each one
November 18, 2026
November 16, 2026
November 13, 2026
We provide end-to-end SecOps solutions for Managed Security Service Providers (MSSPs), Managed Service Providers (MSPs), and Value-Added Resellers (VARs).
Find out how you can become a ThreatDefence partner.
Protect your entire technology stack and build your SecOps on your own pace
White-labeled AI SOC for every client tenant, co-managed with our SOC team
Launch your SOC business without any upfront investment
Embed security operations, threat intelligence and exposure data in your product
Sovereign SOC for Australian MSPs and MSSPs, with onshore analysts and client data
Set the rules for closing alerts automatically, with evidence checks and review
How MSPs deliver branded security monitoring with a SOC partner
ThreatDefence was an official partner of the Cyber Resilience Summit NSW, 29 October 2026 at Hilton Sydney.
Our team was back at BSides Canberra, and our cyber quiz was a hit again.
Two days in Perth with our partner Ever Nimble, on security operations and cyber resilience.
Sponsors of the AUSCERT Cyber Security Conference on the Gold Coast.
Sponsors of the Gartner Security & Risk Management Summit in March.
Sponsors of the Cyber Security for Critical Assets Summit in Perth, February 2026.
Expert conversations with speakers and attendees at CyberCon Melbourne 2025.
Agentic penetration testing continuously tests your external attack surface, proves exploitable weaknesses, and verifies that fixes work. ThreatDefence delivers it as a managed penetration testing service, with AI agents carrying out authorized tests and a 24x7 SOC validating significant findings, investigating signs of earlier exploitation, and tracking remediation.
Attackers now run AI agents against exposed systems. ARTEX, an autonomous penetration testing framework, has been used in real intrusions since August 2026. The FBI issued a FLASH advisory on the framework in November 2026, and Microsoft documented cases where attackers progressed from initial targeting to privileged cloud access in under three hours.
Agentic tools change how attackers find and exploit weaknesses:
An agent can examine an application, identify authentication paths, and begin testing within minutes of first contact.
A single controller can target hundreds of organizations in one campaign, including smaller systems that might previously have attracted little attention.
Agents can repeat tests, adjust their approach, and pursue alternative paths for hours with limited operator involvement.
The same ability to explore systems and adapt testing can be used defensively, within authorized scope and controlled operating limits.
Read the ARTEX advisory >
A traditional penetration test assesses the systems included in its scope at a particular point in time. The environment may change immediately afterward: an application is released, an external service is added, a vulnerability becomes known, or an existing configuration is modified.
An annual assessment remains useful, but it cannot establish whether every change introduced afterward is secure. Continuous penetration testing addresses that gap by testing newly exposed systems, responding to relevant changes, and revisiting existing assets.
Vulnerability scanning identifies potential weaknesses, while agentic testing investigates whether those weaknesses can actually be used. The agent adapts its next action to what it learns from the target, rather than following only a fixed sequence of checks.
Continuous testing complements periodic independent assessments. Each provides a different form of security evidence.
ThreatDefence provides agentic penetration testing as a standing subscription through its AI SOC platform. Your organization authorizes the scope and test policy during onboarding, while ThreatDefence operates the agents, validates significant findings, and tracks each confirmed weakness through remediation and retesting.
The managed service includes:
Agreed domains, addresses, exclusions, and testing rules remain in force across subsequent tests. Your team can update the policy as the environment changes.
Tests are triggered by changes, while a rolling schedule revisits systems that have not changed. There is no separate engagement to book for each test.
The testing agent demonstrates weaknesses on the target before reporting them, with evidence that engineers can use to investigate and fix the problem.
Offensive testing runs alongside security monitoring in the same AI SOC platform. For monitored environments, confirmed weaknesses can be checked against existing security telemetry.
Findings remain open while your team works on remediation. The agent repeats the relevant test when a fix is reported.
The service maintains a growing account of discovered assets, tests performed, confirmed weaknesses, analyst reviews, and verified fixes.
The service reduces the need for your team to organize individual testing engagements and manually follow up on every finding. Your system owners remain responsible for implementing changes, while ThreatDefence manages testing and verification.
Read about penetration testing as a service >
ThreatDefence connects attack surface discovery, agentic testing, SOC investigation, and remediation verification in one managed process. Each confirmed weakness moves through the same sequence, from identifying the affected asset to checking the deployed fix.
Connecting testing with SOC investigation adds an important distinction. A confirmed vulnerability establishes that a weakness can be exploited, while the associated log investigation looks for evidence that exploitation may already have occurred.
The result is a single record connecting the technical finding, security investigation, remediation, and retest.
The testing agent can follow a sequence of weaknesses to determine what an attacker could reach within the authorized scope. An exposed configuration file, an open registration function, and a missing access control may appear relatively minor when examined separately but become significant when combined.
Consider a customer portal where a test account can register successfully and access another account’s invoices. The important finding is the demonstrated failure of account separation, supported by the requests and responses that establish how access was obtained.
Testing agent
Authorized test inside the agreed scope.
14 requests, rate capped.
/api/v1/accounts/{id}/invoices critical
/api/v1/accounts/{id}/invoices
/api/v1/register weak control
/api/v1/register
/assets/config.json read
/assets/config.json
200 OK returned to test account 7731. Expected 403.
Finding PT-0218, critical. One account can read another account’s invoices.
Minimal proof kept. No customer data stored.
The attack path records what the agent discovered, which branches it explored, and the steps that led to the confirmed weakness.
It also shows where the agent stopped because a path was unsuccessful or a testing limit was reached. A stopped path should not be interpreted as proof that everything beyond it is secure.
This gives your engineering team a reproducible explanation of the weakness rather than an isolated vulnerability label.
Read Inside an Agentic Penetration Test >
Every confirmed finding includes evidence of the weakness on the affected system. The record identifies what was tested, why the result matters, and what your team needs to correct.
Read access to another account proven with a test account.
Proof reviewed, severity confirmed, your team notified.
Hunter agent searched 90 days of web logs for the same request pattern. No earlier use found.
Access check added to the invoices route.
The same request is refused with 403.
Each finding contains:
The request that succeeded and the response demonstrating the weakness, limited to the minimum evidence needed, with no customer data stored.
The exact hostname, service, or application where the weakness was confirmed.
The testing sequence and observations that explain how the agent identified and reproduced the problem.
A rating informed by demonstrated exploitability and what the weakness exposes.
Practical remediation steps for the system owner, linked to the test that will be repeated after the correction.
Timestamped records of analyst validation, telemetry searches, remediation, and subsequent retesting.
The distinction between a potential weakness and a proven finding matters. A scanner may identify a suspicious version, configuration, or response. The testing agent goes further by demonstrating the weakness on the actual target before it becomes a confirmed finding.
Engineers can examine the evidence and understand what needs to change without having to reconstruct the original investigation.
Watch the agents test an exposed system, prove a weakness and close it in a live demo.
Continuous penetration testing responds to changes in your attack surface, relevant threat intelligence, and remediation status. A rolling testing schedule covers existing systems between those events.
portal.acmecorp.com recorded by the ASM agent.
An exploited flaw affects an exposed VPN product.
Your team marks PT-0218 as fixed.
A leaked account matches the HR portal.
Testing can begin following several events:
The ASM agent identifies a hostname, service, or certificate that was not previously recorded, or detects a change to an existing asset.
A published advisory or known exploited vulnerability affects a product exposed by your organization.
A leaked account or cloned sign-in page identifies an exposed system that may need further assessment, subject to the applicable testing approvals.
Your team marks a confirmed finding as remediated, triggering the relevant verification test.
Your team or a SOC analyst requests testing of an authorized system, including ahead of a planned release.
The Planner agent determines what should be tested next. Newly discovered exposures and relevant security changes can be brought forward instead of waiting for the next scheduled rotation.
Testing priority follows the exposed system and the available information. For example, an internet-facing application with active authentication functions may warrant attention before an unused hostname.
The testing history records which event initiated each run and what the agent found.
The testing agent assesses your external attack surface from the perspective of a system reachable over the internet. Testing depth depends on the asset, its observed behavior, and the authorized scope.
The service covers:
Testing authentication, session handling, access controls, input handling, and exposed API documentation.
Checking whether customer portals and APIs prevent one account from viewing or changing another account’s information.
Examining self-registration, account recovery, single sign-on configuration, and multi-factor authentication weaknesses.
Assessing internet-reachable remote access systems, databases, and management interfaces.
Checking public storage, exposed keys, and services deployed with insecure default settings.
Testing exposed products affected by newly published advisories and vulnerabilities with confirmed exploitation.
Testing adapts to the target. A customer portal requires different checks from a remote access gateway, and an API authorization issue requires different evidence from an exposed management interface.
For account separation testing, the question is whether an authorized identity can reach information or functions belonging to another account. Such checks may require test accounts supplied by your team, with the necessary approval.
The service focuses on externally reachable systems. Internal network testing, social engineering, and physical access assessment remain outside its scope.
Read about web application penetration testing >
ThreatDefence operates the testing agent under a test policy approved by the system owner before testing begins. The policy identifies authorized targets, permitted methods, excluded activities, and any conditions requiring human approval.
These restrictions are enforced outside the AI model, so instructions encountered on a tested system cannot extend the agent’s authority.
The controls include:
The organization confirms ownership or testing authority for the domains and addresses included in the assessment.
Triggered, scheduled, and requested tests operate under the same approved rules. Exclusions and testing windows can be changed as necessary.
An asset discovered outside the authorized scope remains untested until the responsible owner approves its inclusion.
The agent uses the least intrusive method needed to prove a weakness. Denial of service, data modification, and data removal are excluded.
Testing rates are capped, with time windows and exclusions configurable for individual systems.
Each agent runs in a sandbox with network access restricted to authorized targets.
Higher-impact activities, including tests involving leaked credentials or accounts supplied by your organization, require approval from an analyst or your team.
Every request and result is logged for subsequent review.
Production testing requires more than a general assurance that an AI agent will behave safely. The actual controls governing network access, test intensity, target selection, and approvals must remain effective regardless of what the agent encounters.
For example, a page might contain instructions designed to redirect an AI agent toward another hostname. The sandbox network policy prevents the agent from reaching that destination if it falls outside the approved scope.
The same rules apply when tests run automatically in response to a new exposure.
ThreatDefence’s SOC manages the testing service, reviews significant findings, and follows remediation through verification. Your team authorizes the scope, supplies necessary system context, and implements the fixes.
This division matters for organizations without a dedicated offensive security team. The service handles ongoing test execution, evidence review, and tracking, while remediation remains with the people responsible for the affected systems.
Each confirmed problem has a record containing its owner, supporting evidence, history, and current status.
For monitored environments, the SOC can also investigate whether available logs indicate earlier exploitation. A successful penetration test does not, by itself, establish that an actual compromise occurred.
ThreatDefence maintains an ongoing record of testing and remediation in the platform. Security teams can review current findings and historical activity without waiting for a periodic assessment report.
The record includes:
Discovered domains, hosts, services, and certificates, together with changes recorded over time.
Individual tests, the events that triggered them, and their results, providing visibility into the scope assessed.
Confirmed weaknesses, associated fixes, and the results of verification tests.
Findings, fixes, and retest histories that can be exported for auditors or independent penetration testers.
Customer records remain in their own region, on a platform hosted in Australia and the United States.
ThreatDefence holds ISO 27001 and PCI DSS certification and a SOC 2 report.
Testing history should distinguish assets that have been tested from assets awaiting assessment. A discovered asset and a completed penetration test provide different levels of assurance.
The accumulated evidence helps your team understand how coverage and findings have changed, while giving independent reviewers a starting point for their own assessments.
Continuous agentic testing complements independent human-led penetration testing. The managed service provides ongoing external validation, while an independent assessment can address specialist testing requirements and provide a separate opinion.
An independent tester may examine complex business workflows, make judgments requiring deeper organizational context, or evaluate systems inaccessible from the internet.
Agentic testing provides repeatable validation between those engagements. Its records can also help the independent tester understand previously identified weaknesses and verify what has changed.
Where a customer, contract, or standard requires an independent penetration testing report, the independent assessment remains necessary.
Read about continuous penetration testing >
Agentic penetration testing provides the validation step within continuous threat exposure management, or CTEM. The broader program discovers exposures, establishes which weaknesses can be used, and coordinates remediation.
Within the ThreatDefence platform, the related capabilities are:
The ASM and Brand agents identify external exposures that may require testing.
The testing agent demonstrates which weaknesses are exploitable within the approved scope.
Confirmed findings affect the Security Score and enter the risk register until remediation is completed and verified.
The wider risk management process handles prioritization, ownership, and organizational reporting. Penetration testing contributes the technical evidence showing what an attacker could actually exploit.
Read the CTEM guide >
MSPs and MSSPs can provide agentic penetration testing and attack surface monitoring to their customers under their own brand, using the ThreatDefence platform and SOC.
The service supports:
Each customer has its own authorized domains, exclusions, test windows, and testing limits.
Testing can begin using authorized customer domains before security log integrations are connected.
Partner analysts and ThreatDefence’s SOC work with findings through the same cases.
Partners can incorporate ongoing testing into their managed security services while retaining the customer relationship. Each customer remains responsible for approving testing and implementing changes to its systems.
The model allows providers to offer continuous external penetration testing without having to operate the testing agents and associated SOC processes independently.
Getting started with ThreatDefence’s managed penetration testing service begins with confirming which systems may be tested and how testing is permitted to operate. External discovery and testing require only the authorized domains initially, so security log connections can be added afterward.
Onboarding follows these steps:
The first test can begin once the scope and testing policy are confirmed and authorized. SOC telemetry adds the ability to investigate earlier exploitation, but it is not required to begin external testing.
Read about external penetration testing >
See how ThreatDefence automates security monitoring, compliance and cyber risk management in one platform.
CountryAustraliaUnited StatesNew ZealandUnited KingdomCanadaSingaporeOtherI'm an MSP, MSSP, or reseller
Δ
Agentic penetration testing, also called agentic pentesting or AI penetration testing, uses AI agents to plan and execute authorized security tests. Unlike a fixed scanner, the agent can examine a target’s responses and adapt its next testing step. ThreatDefence uses this approach to continuously assess external systems, confirm exploitable weaknesses, and preserve the evidence. SOC analysts review significant findings, while execution remains within the agreed testing policy.
ThreatDefence’s managed penetration testing service covers authorized internet-facing web applications, APIs, exposed services, identity functions, and cloud resources. The testing agent performs testing and records confirmed weaknesses, while SOC analysts validate significant findings and investigate available telemetry for earlier exploitation. The service also tracks remediation and retests reported fixes. Internal network penetration testing, social engineering, physical testing, and independent assurance reports remain outside the service.
The ASM agent maintains the external asset inventory, and the Brand agent identifies relevant external exposures, including credential and impersonation findings. The Planner agent determines testing priorities, while the testing agent explores authorized systems, develops test sequences, and proves weaknesses. For environments connected to security monitoring, the Defender and Hunter agents examine available telemetry for signs that a confirmed weakness may already have been exploited.
Yes, within an approved policy designed to limit testing impact. ThreatDefence restricts agents to authorized targets, caps request rates, supports testing windows, and excludes destructive activities such as denial of service or modifying and removing data. Isolated sandboxes enforce network boundaries independently of the AI model. Higher-impact activities require human approval. As with other production security testing, the system owner should review scope and operational constraints before authorizing execution.
ThreatDefence’s SOC manages the testing service and reviews significant findings, while your organization authorizes the scope and remains responsible for its systems. The agents operate under controls that define permitted targets and methods, and activities requiring additional authorization wait for human approval. Every test request and result is recorded. Your team handles remediation, and ThreatDefence repeats the relevant tests to verify that reported fixes are effective.
Attack surface management identifies the systems your organization exposes to the internet, including assets absent from existing inventories. Agentic penetration testing uses that information to assess whether weaknesses on authorized systems can be exploited. The ASM agent supplies the changing asset inventory, and the testing agent performs the validation. Newly discovered assets outside the approved scope still require authorization before testing, even when discovery has already identified them.
A new or changed system can be queued for testing as soon as the ASM agent records it, ahead of the normal rolling schedule. Priority depends on the exposure and available context, rather than discovery order alone. An active internet-facing application may take precedence over an unused hostname. The service also responds to new vulnerability advisories, reported fixes, and specific testing requests, while remaining subject to approved time windows and testing limits.