Burp Suite DAST vs Reconmap

Burp Suite DAST is an automated dynamic scanner for web vulnerabilities, built on the scanning engine used in Burp Suite Professional. Its Chromium-based crawler can handle JavaScript single-page applications, dynamic forms, GraphQL endpoints, and asynchronous loads, while crawling and auditing can run in parallel. Session-aware scans maintain authenticated state using username-password pairs or recorded login sequences. The scanner covers APIs described by Postman Collections, OpenAPI, SOAP, and GraphQL, with native support for several authentication methods. Teams can schedule portfolio scans from a dashboard or run them in CI pipelines, including on pull requests and merges. Deployment options include managed cloud and self-hosted software for Windows and Linux, plus Helm deployment for Kubernetes; self-hosted deployments can operate in air-gapped environments. Access controls include role-based permissions, site groups, audit trails, SAML single sign-on, and group-locked scan policies. Findings include captured requests and confirming responses. Pricing depends on the portfolio and requires contacting PortSwigger; a guided proof-of-concept trial follows a tailored demo and discovery call.

Reconmap is a free, open-source collaboration platform for planning, conducting, and documenting penetration test projects across assets and clients. It supports multiple top-level organisations and includes project templates, task management, and client management. Vulnerability tracking and a templates database help organize findings, while users can automate security commands and schedule them with cron expressions. Reports can be generated in Word, Markdown, and Typst formats, with custom whitelabel reporting. Integrations can send vulnerabilities to Jira or Azure DevOps and deliver event-driven HTTP notifications through webhooks. Security features include SSO, OpenID and SAML user federation, two-factor authentication, email verification, and an audit log. A REST API with token authentication supports connections to external tools and scripts. Deployment options include Docker Compose, Kubernetes, manual installation, and hosted SaaS maintained by the project’s lead developers through Netfoe. The documentation positions Docker Compose for small teams and Kubernetes for production deployments and large teams; it also cautions that Compose is not designed for high availability or horizontal scaling out of the box.