Agentless Security Testing at Scale and Modern DAST in CI/CD¶
Escape DAST (Dynamic Application Security Testing) is a feature that automatically tests APIs and Web Applications (including SPAs) for security weaknesses. By using Escape Inventory’s detailed output (including automatically generated API Schemas from code or frontend assets), the Escape DAST engine works with the knowledge it needs to run meaningful business logic security tests. It can run at scale directly on all exposed APIs and Web Apps discovered by the inventory or as a configurable Modern DAST right in the CI/CD pipeline during the development phase.
This Code-to-Cloud integration means teams can test both production and development environments, internal and external assets, without manual traffic capture. By using advanced reinforcement learning to simulate real-world usage, Escape uncovers hidden vulnerabilities that other scanners miss. As a result, security teams find complex business logic issues early and often, reducing risk and improving application integrity.
By combining structured input (API Schemas) with intelligent test generation, Escape DAST provides a clear, practical way to discover and address critical vulnerabilities before they can be exploited.
Key Features¶
Agentless and Traffic-less Security Testing¶
Escape DAST uses the API Schemas from the Inventory to understand how each endpoint should behave. This allows it to send well-formed requests and explore the application logically. Escape DAST does not rely on agents installed in the environment or captured network traffic. It tests the application as an outside user would, making setup easier and results more reliable.
Modern DAST to Find Complex Business Logic Vulnerabilities in CI/CD¶
Escape DAST can find issues that involve how the application handles its data and processes, not just standard injection attacks. It can detect problems like flawed tenant isolation, where one user might gain access to another user’s data. All of this can be done directly from the development stage, in CI/CD.
Custom Security Rules¶
Default security tests are extensive and cover many vulnerabilities. However, for customers with specific use cases, Escape allows the creation of custom rules. These enable teams to build their own governance and apply it at scale, using a simple yet powerful language thanks to Escape's inference engine.
Sensitive Data Detection¶
During testing, Escape DAST identifies places where sensitive information might leak. This includes personal data (PII), secrets, or tokens that should remain private. The system uses both static and dynamic analysis to reduce false positives and highlight genuine risks.
Contextualized Results (Including Code Owners)¶
Escape DAST links every detected vulnerability back to the information gathered by Escape Inventory. Each finding includes details like:
- Code owners
- Environment (production, staging, etc.)
- Exposure status
- Technology in use
This extra context makes it much easier to prioritize issues requiring urgent attention.
Prioritization and Remediation¶
By knowing who owns the code and where the vulnerable component sits in the application stack, teams can quickly assign fixes to the right people. This reduces the time between detection and remediation.
Internal Assets¶
Escape supports the deployment of a Private Location to detect, fingerprint, and test internal application assets behind firewalls or VPNs using a reverse tunnel.
How it works¶
Escape DAST’s approach is grounded in advanced machine learning and reinforcement learning. It converts the API definitions into a neutral model called a MetaGraph. Using this model, it guides test cases to explore the application’s logic in realistic ways. This approach improves test coverage and uncovers issues that static or traffic-based tools might miss.
For more details, check out this article on our Business Logic Security Testing algorithm: Escape Proprietary Algorithm
Index¶
- Start a new Scan
- Understanding Results
- Analyze Logs
- Schedule Scans
DAST in CI/CD¶
- DAST in GitHub Action
- DAST in GitLab CI
- DAST in Bitbucket
- DAST in CircleCI
- DAST in Jenkins
- DAST in Azure DevOps
- DAST in Travis CI
- Override configuration
- Update introspection
- Identify commits
- Command Line
Authentication¶
- AWS Cognito Preset
- Basic Preset
- cURL Preset
- cURL Sequence Preset
- Digest Preset
- GraphQL Preset
- Headers Preset
- HTTP Preset
- OAuth Client Preset
- OAuth User Preset
- Playwright Preset
- Advanced Workflows
- Authentication Reference
Custom Rules¶
- Alerting
- Detectors
- Transformations
- Mutators
- Seeders
- Custom Rules Reference
Expert Usage¶
- Rate Limiting
- Blocklist & Hotstart
- API Custom Payloads
- API Access Control
- Scan Internal Applications
- API DAST Reference
- Data Types Reference
- SPA DAST Parameters
- GraphQL Persisted Queries
- Retrieve a GraphQL Schema
Supported Security Tests¶
- LLM Security Testing
- Access Control 9
- Configuration 16
- Information Disclosure 32
- Injection 31
- Protocol 24
- Request Forgery 7
- Resource Limitation 18
- Schema 18