B-52 and Intruder share the web application pentest
Intruder is an exposure management platform: attack surface monitoring, vulnerability scanning and cloud security, with AI pentesting for web applications. B-52 tests eleven classes as penetration tests. This comparison separates the scanning from the testing, target by target, and carries the date each Intruder page was read: 18 November 2026.
Their published position was last read on 2026-11-18. Every claim below carries the page it came from and the date it was checked.
The divergence
Continuous scanning with one pentest product, and eleven pentest classes
The shared ground is a web application, tested by agents without a person driving the run.
Intruder’s homepage describes always-on exposure management: one platform for AI pentesting, attack surface monitoring, cloud security and vulnerability management. Most of that platform is scanning. It scans external infrastructure, web applications and APIs, cloud accounts, container images and, through an agent, internal devices, on a schedule and whenever something changes, and it is sold in plans by the number of targets. Their own page on automated penetration testing describes the product as a vulnerability scanner. The pentest product is newer and narrower: AI pentesting for web applications, run white-box from a connected code repository, with a report in hours. B-52 is built the other way round. It is a penetration testing platform with eleven coverage classes, and each class is worked as a test: a scope, an exploited finding, and the request and response that prove it. So the two overlap on one class, the web application, and they part on everything either side of it. The coverage table below sets out, class by class, which form each side publishes.
Coverage
Eleven classes, read against what Intruder publishes for each
Their column says whether a class is published as a pentest, as scanning, or not named. B-52 covers all eleven in all three of its delivery models.
| Coverage class | On Intruder, as published | On B-52 |
|---|---|---|
| Web application | Published as an AI pentest, white-box from a connected repository, and separately as continuous scanning, including authenticated scanning behind a login. | Covered, including the authenticated flows and the authorisation decisions behind each role, with a credential supplied per role. |
| This is the shared class. Read 2026-11-18. | ||
| API | Published as scanning: an uploaded schema tested against a set of checks, on a schedule or from a pipeline. | Covered as its own class: an authorisation matrix written first, then routes checked with a second credential. |
| External network | Published as scanning and attack surface monitoring: new assets are scanned when they appear, with a view of each exposed service and port. | Covered, with the perimeter worked out from announced ranges, resolving names and what answers on each address, then proposed back to you as the scope. |
| Internal network | Published as agent-based vulnerability scanning of devices running Windows, Linux or macOS, on two of the four plans. Their page states that it does not cover network devices. | Covered. This is the one class that needs something deployed inside your network, and on-premise and customer-VPC deployments are both available for it. |
| Cloud | Published as agentless scanning across three cloud providers for misconfigurations, insecure permissions, exposed secrets and vulnerabilities, with daily configuration checks. | Covered: the identity and permission layer, proved by making the call. |
| Secure code review | Source analysis is published as a step inside the web application pentest. Code review is not sold as a class of its own. | Covered. A file, a line, the path an attacker takes to reach that line, and the closing change in the repository’s own idiom. |
| Mobile application | Not named on the pages read. | Covered on the platform, in all three delivery models. |
| Thick client | Not named on the pages read. | Covered on the platform. |
| Active Directory | Not named on the pages read. | Covered: privilege paths walked end to end. |
| Social engineering | Not named on the pages read. | Covered, and scoped separately from the other classes. |
| LLM applications | Not named on the pages read. | Covered on the platform. |
| Scheduled vulnerability scanning and attack surface monitoring | Published: the core of the platform, in every plan. | Not offered in B-52. ShadowMap, also from Security Brigade, monitors the external attack surface continuously. |
- On Intruder, as published
- Published as an AI pentest, white-box from a connected repository, and separately as continuous scanning, including authenticated scanning behind a login.
- On B-52
- Covered, including the authenticated flows and the authorisation decisions behind each role, with a credential supplied per role.
This is the shared class. Read 2026-11-18.
- On Intruder, as published
- Published as scanning: an uploaded schema tested against a set of checks, on a schedule or from a pipeline.
- On B-52
- Covered as its own class: an authorisation matrix written first, then routes checked with a second credential.
- On Intruder, as published
- Published as scanning and attack surface monitoring: new assets are scanned when they appear, with a view of each exposed service and port.
- On B-52
- Covered, with the perimeter worked out from announced ranges, resolving names and what answers on each address, then proposed back to you as the scope.
- On Intruder, as published
- Published as agent-based vulnerability scanning of devices running Windows, Linux or macOS, on two of the four plans. Their page states that it does not cover network devices.
- On B-52
- Covered. This is the one class that needs something deployed inside your network, and on-premise and customer-VPC deployments are both available for it.
- On Intruder, as published
- Published as agentless scanning across three cloud providers for misconfigurations, insecure permissions, exposed secrets and vulnerabilities, with daily configuration checks.
- On B-52
- Covered: the identity and permission layer, proved by making the call.
- On Intruder, as published
- Source analysis is published as a step inside the web application pentest. Code review is not sold as a class of its own.
- On B-52
- Covered. A file, a line, the path an attacker takes to reach that line, and the closing change in the repository’s own idiom.
- On Intruder, as published
- Not named on the pages read.
- On B-52
- Covered on the platform, in all three delivery models.
- On Intruder, as published
- Not named on the pages read.
- On B-52
- Covered on the platform.
- On Intruder, as published
- Not named on the pages read.
- On B-52
- Covered: privilege paths walked end to end.
- On Intruder, as published
- Not named on the pages read.
- On B-52
- Covered, and scoped separately from the other classes.
- On Intruder, as published
- Not named on the pages read.
- On B-52
- Covered on the platform.
Scheduled vulnerability scanning and attack surface monitoring
- On Intruder, as published
- Published: the core of the platform, in every plan.
- On B-52
- Not offered in B-52. ShadowMap, also from Security Brigade, monitors the external attack surface continuously.
Whose signature
Three delivery models, one coverage set
The eleven classes are the same in all three, and every report is signable under Security Brigade’s CERT-In empanelment. What changes is who reviews the findings.
| State | What it means | What follows |
|---|---|---|
| Fully autonomous | You sign off the scope and nothing else is asked of you, bar an approval gate if the run reaches one. Observed median turnaround on this model is one to three business days. | Signable under Security Brigade’s CERT-In empanelment, with every finding through an independent automated cross-check. |
| Autonomous, expert verified | A senior Security Brigade auditor verifies every finding before it reaches you. The run underneath is the same run, against the same eleven classes. | Signable under Security Brigade’s CERT-In empanelment, with every finding verified by a senior auditor. |
| Human led Terminal | A Security Brigade team works the engagement with the platform underneath it. Same classes again. | Signable under Security Brigade’s CERT-In empanelment, with the report owned by the auditor who ran it. |
- Report signable under Security Brigade’s CERT-In empanelment
- TerminalNo state follows this one
In their own terms
What Intruder publishes, part by part
Their pages, their names. Each row is sourced in the claims table at the foot of this page, with the page it was read on and the date.
| Part | What it is, as published |
|---|---|
| Attack surface management | Change detection that scans new assets as they appear and keeps a view of each exposed service, technology and port. |
| Vulnerability management | Continuous scanning of infrastructure, applications and cloud environments, with scans for newly public vulnerabilities and findings ranked by the likelihood of exploitation. |
| AI pentesting | Web application pentests on demand, run white-box from a connected repository. The agents analyse the source, test each finding against the running application, and return a report with the line of code behind each finding and a transcript of the steps taken. |
| This is the part that overlaps with B-52. | |
| Application and API scanning | Dynamic scanning of web applications, single-page applications included, with authenticated scanning behind a login, and schema-driven scanning of REST APIs. |
| Cloud security | Agentless scanning across three cloud providers, with daily configuration checks and scans when a change is detected. |
| Internal scanning | An agent installed on each Windows, Linux or macOS device, on the Pro and Enterprise plans. |
| Testing by people | A manual web application penetration testing service delivered by their own team, and a continuous service in which their testers work alongside the scanner. |
| Plans | Free, Cloud, Pro and Enterprise, with a 14-day free trial. Cloud and Pro are priced as a base fee plus a fee for each target; Enterprise is quoted. The AI pentest is priced separately, per test. |
Attack surface management
- What it is, as published
- Change detection that scans new assets as they appear and keeps a view of each exposed service, technology and port.
Vulnerability management
- What it is, as published
- Continuous scanning of infrastructure, applications and cloud environments, with scans for newly public vulnerabilities and findings ranked by the likelihood of exploitation.
AI pentesting
- What it is, as published
- Web application pentests on demand, run white-box from a connected repository. The agents analyse the source, test each finding against the running application, and return a report with the line of code behind each finding and a transcript of the steps taken.
This is the part that overlaps with B-52.
Application and API scanning
- What it is, as published
- Dynamic scanning of web applications, single-page applications included, with authenticated scanning behind a login, and schema-driven scanning of REST APIs.
Cloud security
- What it is, as published
- Agentless scanning across three cloud providers, with daily configuration checks and scans when a change is detected.
Internal scanning
- What it is, as published
- An agent installed on each Windows, Linux or macOS device, on the Pro and Enterprise plans.
Testing by people
- What it is, as published
- A manual web application penetration testing service delivered by their own team, and a continuous service in which their testers work alongside the scanner.
Plans
- What it is, as published
- Free, Cloud, Pro and Enterprise, with a 14-day free trial. Cloud and Pro are priced as a base fee plus a fee for each target; Enterprise is quoted. The AI pentest is priced separately, per test.
Reading their pentest
How the Intruder AI pentest is set up, in their words
Three things on their pages shape what the test is. First, it is white-box. The buyer connects a code repository, supplies context and credentials, and the agents analyse the source before they test the running application; their page presents that as the source of the test’s depth. Second, their guidance is to run it in staging, not production, with validated backups in place, the same precautions they say apply to a human-led test. Third, the report is written for an audit: a summary, the technical detail, and remediation guidance, presented as evidence for the compliance frameworks listed in the claims table. Their page also states that a person in the loop is no longer necessary for a web application pentest. Where a buyer wants one anyway, Intruder publishes a manual service delivered by its own testers.
What each side can show
Six questions a buyer asks at this stage, with both answers
Their column is sourced in the claims table below. Ours is what this site publishes everywhere else.
| The question | Intruder | B-52 |
|---|---|---|
| What arrives with a finding | From the AI pentest: the line of code behind the finding, proof-of-concept code to reproduce it, and a transcript of each step the agent took. | The request as sent and the response as returned, the steps that reproduce it, a CVSS v4.0 vector and a CWE, on every finding, in every class, in all three delivery models. |
| What the test needs from you | A connected code repository, context and credentials. Their guidance is to test in staging. | A credential for each role you want exercised. Nothing is required inside your network for external and application testing, and a deployment only for internal. |
| Whose name the report carries | The AI pentest report is presented as audit evidence, and their page says acceptance depends on the auditor. A manual test by their own team is published as a separate service. | Security Brigade’s, in all three delivery models: every report is signable under its CERT-In empanelment, held since 2008. Security Brigade is ISO 27001 certified. |
| Where the work runs | Their security page describes a SaaS environment. No on-premise or self-hosted deployment is named on the pages read. | On-premise and customer VPC are both available today, with residency in India, the European Union, the United States and Singapore. |
| Firing a test from a pipeline | Scans can be triggered from a pipeline through their API, and findings sent to the issue trackers named in the claims table. | Four continuous-integration systems in production (GitHub Actions, GitLab CI, Jenkins and Azure DevOps), and a result can fail a build against a severity threshold you set. |
| A measured comparison against human testers | Not evaluated in this comparison. | B-52 and Security Brigade’s expert assessment team worked the same targets in parallel, findings pooled with each item counted once. B-52 reached 90–95% of that pooled set. The method is set out below. |
- Intruder
- From the AI pentest: the line of code behind the finding, proof-of-concept code to reproduce it, and a transcript of each step the agent took.
- B-52
- The request as sent and the response as returned, the steps that reproduce it, a CVSS v4.0 vector and a CWE, on every finding, in every class, in all three delivery models.
What the test needs from you
- Intruder
- A connected code repository, context and credentials. Their guidance is to test in staging.
- B-52
- A credential for each role you want exercised. Nothing is required inside your network for external and application testing, and a deployment only for internal.
- Intruder
- The AI pentest report is presented as audit evidence, and their page says acceptance depends on the auditor. A manual test by their own team is published as a separate service.
- B-52
- Security Brigade’s, in all three delivery models: every report is signable under its CERT-In empanelment, held since 2008. Security Brigade is ISO 27001 certified.
- Intruder
- Their security page describes a SaaS environment. No on-premise or self-hosted deployment is named on the pages read.
- B-52
- On-premise and customer VPC are both available today, with residency in India, the European Union, the United States and Singapore.
- Intruder
- Scans can be triggered from a pipeline through their API, and findings sent to the issue trackers named in the claims table.
- B-52
- Four continuous-integration systems in production (GitHub Actions, GitLab CI, Jenkins and Azure DevOps), and a result can fail a build against a severity threshold you set.
A measured comparison against human testers
- Intruder
- Not evaluated in this comparison.
- B-52
- B-52 and Security Brigade’s expert assessment team worked the same targets in parallel, findings pooled with each item counted once. B-52 reached 90–95% of that pooled set. The method is set out below.
How the parallel benchmark was run
What the 90–95% figure counts
Measured against our own assessors As of 2026-09-14
- B-52 and Security Brigade’s expert assessment team worked the same targets at the same time, and neither side saw the other’s output while the work was running.
- Both sets of findings were pooled into one denominator with each item counted once, so a defect both sides reached counts once, not twice.
- B-52 reached 90–95% of that pooled set. Part of what it reached was absent from the team’s own output, which is why the pooled set is larger than either side produced alone.
- Every engagement Security Brigade has run since the firm started in 2006 was worked inside Lemon, and that record is what trained the models the platform runs on.
FAQ
Common questions
Still deciding whether this is the right test? Ask us directly.
Request a scoping callWhat is Intruder?
Is Intruder a penetration test or a vulnerability scanner?
How much does an Intruder pentest cost?
What does B-52 cover that Intruder does not publish?
Can a B-52 report be filed where an empanelled auditor is required?
How current is this comparison?
Every claim, sourced
What was read, and when
Competitive claims go out of date, and this page has a date on every one of them so you can tell how far. Where a row has aged past what you would rely on, check it against their own site. That is where each of these was read.
| What Intruder publishes | Verified |
|---|---|
| Homepage positioning: "Always-on exposure management" and "A single platform for AI pentesting, attack surface monitoring, cloud security and vulnerability management. Built for stretched security, IT and compliance teams." The page states "Join 3,000+ companies securing their attack surface with Intruder". | 2026-11-18 |
| Read at https://www.intruder.io/ | |
| Their page on automated penetration testing opens: "Intruder is an automated vulnerability scanner that finds cyber security weaknesses in your digital infrastructure, to avoid costly data breaches." It adds: "Intruder is an example of a vulnerability scanner, offering year-round protection from opportunistic attackers." | 2026-11-18 |
| Read at https://www.intruder.io/automated-penetration-testing | |
| AI pentesting is published for web applications: "AI pentesting agents deliver the depth of a pentest on your web applications, on demand." "Intruder takes a white-box approach, working from your source code for deeper coverage." "Connect your code repository via GitHub or GitLab, provide any context and credentials and launch a scan in minutes." | 2026-11-18 |
| Read at https://www.intruder.io/platform/ai-pentesting | |
| How the AI pentest works, and what the report carries: "Connect your GitHub or GitLab repo and the agents run AI SAST across your source code, then test each finding against the app to prove what’s exploitable." "You get a summary, the detailed findings with the exact line of code behind each one, and a full transcript of every step the agent took, so you and your auditor can see exactly what was tested and what was found." "You get proof-of-concept code with it, so your team can reproduce the issue rather than take our word for it." | 2026-11-18 |
| Read at https://www.intruder.io/use-cases/ai-sast | |
| On people in the test: "A human in the loop isn’t necessary for web app pentesting anymore." "Intruder’s agents are built and trained by CREST-certified pentesters and validate every finding against the application before it’s reported." | 2026-11-18 |
| Read at https://www.intruder.io/platform/ai-pentesting | |
| On where to run it: "AI pentesting is as safe to run as a human-led pentest. Neither is completely risk-free, so the same precautions apply: test in staging rather than production, keep validated backups, and make sure your disaster recovery works." | 2026-11-18 |
| Read at https://www.intruder.io/platform/ai-pentesting | |
| AI pentest pricing: "Intruder’s AI web app pentesting starts from $3,500 per test for existing customers and $4,000 as a standalone purchase. Pricing is based on the size and complexity of your application." | 2026-11-18 |
| Read at https://www.intruder.io/platform/ai-pentesting | |
| The pentest pricing page lists a "Same day pentest" at $3,500 per test, marked "Platform subscribers pay", and a "4 pentest pack" at $12,000, with "Pentests must be used within 1 year of purchase." It lists "Unlimited retesting", "Integrate GitHub, GitLab, Azure DevOps or Bitbucket Cloud repos" and a compliance promise: "If your auditor rejects the report, we refund the test in full". | 2026-11-18 |
| Read at https://www.intruder.io/pentest-pricing | |
| Platform plans are named Free, Cloud, Pro and Enterprise, with a 14-day free trial. "Our pricing for Cloud and Pro consists of a base fee plus a small fee-per-target." "Pricing for Enterprise is quoted separately, as it depends on your specific requirements and the size/complexity of your systems." The Cloud and Pro amounts are calculated on the page from the number of targets; the page as read carried no fixed figure for them. | 2026-11-18 |
| Read at https://www.intruder.io/pricing | |
| Web application scanning: "Continuous dynamic application security testing (DAST) for web apps, single-page apps and underlying infrastructure, including authenticated scanning behind login pages." The same passage states the scanner "integrates with CI/CD pipelines through GitHub, GitLab, Jira and Azure DevOps". | 2026-11-18 |
| Read at https://www.intruder.io/ | |
| Attack surface and vulnerability management: "Real-time change detection automatically scans new assets for vulnerabilities, delivering a complete view of every exposed service, technology and port." "Emerging threat scans run within hours of new critical vulnerabilities going public, issues are prioritized by real-world exploit likelihood". | 2026-11-18 |
| Read at https://www.intruder.io/ | |
| Cloud: "Agentless scanning across AWS, Azure and Google Cloud that catches misconfigurations, insecure permissions, exposed secrets and critical vulnerabilities before attackers do. Daily configuration checks and automatic scans on detected changes keep exposure windows short." | 2026-11-18 |
| Read at https://www.intruder.io/ | |
| Internal scanning: "Agent-based internal vulnerability scanning, with audit-ready reports for compliance." It covers "Any device running Windows, Linux, or macOS." Asked whether it scans network devices such as routers and switches, the page answers: "No. Intruder’s internal scanner is agent-based, meaning it runs directly on each device rather than scanning across the network." "Internal scanning is available on Pro and Enterprise plans." | 2026-11-18 |
| Read at https://www.intruder.io/use-cases/internal-vulnerability-scanning | |
| API scanning: "Automated vulnerability scanning for your REST APIs. Upload your API schema and test it against 100 checks, from SQL injection to cross-site scripting." "Intruder’s API lets you trigger scans from your CI/CD pipeline, so you can catch vulnerabilities during development rather than after release." | 2026-11-18 |
| Read at https://www.intruder.io/use-cases/api-security | |
| Compliance use: "Automated reports are generated after every scan and include a high-level summary plus the technical detail auditors need for SOC 2, ISO 27001, HIPAA, PCI DSS, and more." Asked whether it replaces an annual pentest, the page answers: "It depends on your auditor, but many accept AI pentesting as evidence of regular penetration testing." "Vulnerability scan and pentest reports can be sent directly to Drata and Vanta." | 2026-11-18 |
| Read at https://www.intruder.io/use-cases/compliance | |
| Integrations: "Intruder integrates with Jira, GitHub, GitLab, Azure DevOps, and ServiceNow for issue tracking, Slack and Microsoft Teams for alerts, Drata and Vanta for compliance, and Microsoft Sentinel for SIEM." | 2026-11-18 |
| Read at https://www.intruder.io/use-cases/compliance | |
| Testing by people is also published: a "Manual web application penetration testing service", "Conducted by our CREST-certified penetration testing team", and a "Continuous web application penetration testing service" in which "Our penetration testers prioritize high-impact issues". | 2026-11-18 |
| Read at https://www.intruder.io/penetration-testing/web-application-penetration-testing-service | |
| Their own attestation and hosting model: "Intruder Systems Ltd successfully completed the AICPA Service Organization Control (SOC) 2 Type 2 audit." The same page describes "logical data separation between clients’ datasets within the SaaS environment". | 2026-11-18 |
| Read at https://www.intruder.io/security | |
| Mobile applications, thick-client applications, Active Directory, social engineering and LLM applications are not named as test targets on the homepage, the AI pentesting page, the pricing page or the pentest pricing page. No on-premise or self-hosted deployment of the platform is named on those pages. | 2026-11-18 |
| Read at https://www.intruder.io/platform/ai-pentesting | |
Homepage positioning: "Always-on exposure management" and "A single platform for AI pentesting, attack surface monitoring, cloud security and vulnerability management. Built for stretched security, IT and compliance teams." The page states "Join 3,000+ companies securing their attack surface with Intruder".
- Verified
- 2026-11-18
Read at https://www.intruder.io/
Their page on automated penetration testing opens: "Intruder is an automated vulnerability scanner that finds cyber security weaknesses in your digital infrastructure, to avoid costly data breaches." It adds: "Intruder is an example of a vulnerability scanner, offering year-round protection from opportunistic attackers."
- Verified
- 2026-11-18
Read at https://www.intruder.io/automated-penetration-testing
AI pentesting is published for web applications: "AI pentesting agents deliver the depth of a pentest on your web applications, on demand." "Intruder takes a white-box approach, working from your source code for deeper coverage." "Connect your code repository via GitHub or GitLab, provide any context and credentials and launch a scan in minutes."
- Verified
- 2026-11-18
Read at https://www.intruder.io/platform/ai-pentesting
How the AI pentest works, and what the report carries: "Connect your GitHub or GitLab repo and the agents run AI SAST across your source code, then test each finding against the app to prove what’s exploitable." "You get a summary, the detailed findings with the exact line of code behind each one, and a full transcript of every step the agent took, so you and your auditor can see exactly what was tested and what was found." "You get proof-of-concept code with it, so your team can reproduce the issue rather than take our word for it."
- Verified
- 2026-11-18
Read at https://www.intruder.io/use-cases/ai-sast
On people in the test: "A human in the loop isn’t necessary for web app pentesting anymore." "Intruder’s agents are built and trained by CREST-certified pentesters and validate every finding against the application before it’s reported."
- Verified
- 2026-11-18
Read at https://www.intruder.io/platform/ai-pentesting
On where to run it: "AI pentesting is as safe to run as a human-led pentest. Neither is completely risk-free, so the same precautions apply: test in staging rather than production, keep validated backups, and make sure your disaster recovery works."
- Verified
- 2026-11-18
Read at https://www.intruder.io/platform/ai-pentesting
AI pentest pricing: "Intruder’s AI web app pentesting starts from $3,500 per test for existing customers and $4,000 as a standalone purchase. Pricing is based on the size and complexity of your application."
- Verified
- 2026-11-18
Read at https://www.intruder.io/platform/ai-pentesting
The pentest pricing page lists a "Same day pentest" at $3,500 per test, marked "Platform subscribers pay", and a "4 pentest pack" at $12,000, with "Pentests must be used within 1 year of purchase." It lists "Unlimited retesting", "Integrate GitHub, GitLab, Azure DevOps or Bitbucket Cloud repos" and a compliance promise: "If your auditor rejects the report, we refund the test in full".
- Verified
- 2026-11-18
Read at https://www.intruder.io/pentest-pricing
Platform plans are named Free, Cloud, Pro and Enterprise, with a 14-day free trial. "Our pricing for Cloud and Pro consists of a base fee plus a small fee-per-target." "Pricing for Enterprise is quoted separately, as it depends on your specific requirements and the size/complexity of your systems." The Cloud and Pro amounts are calculated on the page from the number of targets; the page as read carried no fixed figure for them.
- Verified
- 2026-11-18
Read at https://www.intruder.io/pricing
Web application scanning: "Continuous dynamic application security testing (DAST) for web apps, single-page apps and underlying infrastructure, including authenticated scanning behind login pages." The same passage states the scanner "integrates with CI/CD pipelines through GitHub, GitLab, Jira and Azure DevOps".
- Verified
- 2026-11-18
Read at https://www.intruder.io/
Attack surface and vulnerability management: "Real-time change detection automatically scans new assets for vulnerabilities, delivering a complete view of every exposed service, technology and port." "Emerging threat scans run within hours of new critical vulnerabilities going public, issues are prioritized by real-world exploit likelihood".
- Verified
- 2026-11-18
Read at https://www.intruder.io/
Cloud: "Agentless scanning across AWS, Azure and Google Cloud that catches misconfigurations, insecure permissions, exposed secrets and critical vulnerabilities before attackers do. Daily configuration checks and automatic scans on detected changes keep exposure windows short."
- Verified
- 2026-11-18
Read at https://www.intruder.io/
Internal scanning: "Agent-based internal vulnerability scanning, with audit-ready reports for compliance." It covers "Any device running Windows, Linux, or macOS." Asked whether it scans network devices such as routers and switches, the page answers: "No. Intruder’s internal scanner is agent-based, meaning it runs directly on each device rather than scanning across the network." "Internal scanning is available on Pro and Enterprise plans."
- Verified
- 2026-11-18
Read at https://www.intruder.io/use-cases/internal-vulnerability-scanning
API scanning: "Automated vulnerability scanning for your REST APIs. Upload your API schema and test it against 100 checks, from SQL injection to cross-site scripting." "Intruder’s API lets you trigger scans from your CI/CD pipeline, so you can catch vulnerabilities during development rather than after release."
- Verified
- 2026-11-18
Read at https://www.intruder.io/use-cases/api-security
Compliance use: "Automated reports are generated after every scan and include a high-level summary plus the technical detail auditors need for SOC 2, ISO 27001, HIPAA, PCI DSS, and more." Asked whether it replaces an annual pentest, the page answers: "It depends on your auditor, but many accept AI pentesting as evidence of regular penetration testing." "Vulnerability scan and pentest reports can be sent directly to Drata and Vanta."
- Verified
- 2026-11-18
Read at https://www.intruder.io/use-cases/compliance
Integrations: "Intruder integrates with Jira, GitHub, GitLab, Azure DevOps, and ServiceNow for issue tracking, Slack and Microsoft Teams for alerts, Drata and Vanta for compliance, and Microsoft Sentinel for SIEM."
- Verified
- 2026-11-18
Read at https://www.intruder.io/use-cases/compliance
Testing by people is also published: a "Manual web application penetration testing service", "Conducted by our CREST-certified penetration testing team", and a "Continuous web application penetration testing service" in which "Our penetration testers prioritize high-impact issues".
- Verified
- 2026-11-18
Read at https://www.intruder.io/penetration-testing/web-application-penetration-testing-service
Their own attestation and hosting model: "Intruder Systems Ltd successfully completed the AICPA Service Organization Control (SOC) 2 Type 2 audit." The same page describes "logical data separation between clients’ datasets within the SaaS environment".
- Verified
- 2026-11-18
Read at https://www.intruder.io/security
Mobile applications, thick-client applications, Active Directory, social engineering and LLM applications are not named as test targets on the homepage, the AI pentesting page, the pricing page or the pentest pricing page. No on-premise or self-hosted deployment of the platform is named on those pages.
- Verified
- 2026-11-18
Read at https://www.intruder.io/platform/ai-pentesting
Other comparisons
Scope the test the requirement asks for
B-52 publishes configurable pricing for web, API, mobile and cloud assessments. Other testing classes and delivery models are quoted individually.