We’ve just added a delete endpoint for applications in our public API, making it easier to manage your resources programmatically.
https://public.escape.tech/v1/#tag/applications/DELETE/application/{id}We’re excited to introduce Frontend SPAs (Single Page Applications) as part of your Application Inventory. This enhancement allows you to track and manage your SPAs with the same level of detail and efficiency you expect from our platform.
If you have access to the DAST feature, this functionality is already available to you. For users without DAST access, reach out to your account manager to enable this feature.
How to access your Frontend SPAs inventory:
By providing better visibility into your frontend applications, we aim to enhance your ability to manage, secure, and monitor all your modern applications effectively!
A quick heads up: We’ve made significant optimizations to our platform, resulting in faster page load times across the board. Your workflows will now be more seamless, with less time spent waiting and more time focused on what matters most.
Automated API Schema Generation is now possible from C#!
Building APIs in C#? No need to worry about maintaining your API specifications anymore. You can effortlessly generate API specifications directly from your C# code.
Escape scans your codebase, analyzes your API's code, and generates precise specifications, saving you time and effort while ensuring accuracy.
To learn more about how automated API specification generation works, visit our documentation: Code to Cloud: API Schema Generation.
We look forward to seeing how this helps streamline your API development and security workflows. As always, your feedback is welcome!
We’re excited to announce our new integration with Wiz, bringing together Escape’s deep application-layer insights with Wiz’s unparalleled cloud security capabilities. This partnership empowers security teams with:
💡 If you're a joint Wiz and Escape customer, you can find step-by-step instructions on how to set up Wiz integration in the Escape's official documentation. Feel free to set it up now 😉
We’ve drastically enhanced our support for Postman Collections!
Our DAST scanner now parses collections more effectively, even when they’re poorly implemented—a common issue we’ve addressed head-on. Postman Collections, by design, provide examples of API requests, and with this improvement, we ensure better accuracy and coverage for your scans, no matter the quality of the collection.
We’re excited to announce that our DAST scanner now supports OpenAPI specifications with cURL traffic examples, including those built using extensions like Redocly. This enhancement leverages real-world examples to boost scan quality and simplify your security testing process.
OpenAPI specifications can include cURL traffic examples to demonstrate specific API requests and responses. With this update, our DAST scanner can now parse OpenAPI specs with embedded cURL examples and use them to initiate scans.
We’ve also added support for Redocly, a tool that simplifies creating OpenAPI specs enriched with cURL examples, ensuring seamless integration into your workflows.
Use tools like Redocly to build your OpenAPI specification, embedding cURL examples to document API behavior and parameters.
Upload the Spec to the DAST Scanner:
Go to Security Scan and click New Application
3.Run the Scan:
The scanner will parse the OpenAPI spec, leverage the cURL examples for precise API interactions, and begin testing for vulnerabilities!
We’re excited to introduce another great capability for our DAST scanner: support for Burp Suite exports as REST API schemas. This enhancement streamlines your workflow by allowing you to leverage Burp Suite traffic captures to define your API schema, ensuring more comprehensive and efficient vulnerability scans.
Burp Suite is a widely-used tool for security testing, and its exports provide detailed records of HTTP traffic captured during web application testing. With this update, our DAST scanner can now ingest Burp Suite exports to interpret and scan REST APIs.
Use Burp Suite to intercept and record API traffic during your testing session. Export the captured data in the supported format.
Upload to DAST Scanner Configure your scan in a few easy steps:
Go to Security Scan and click New Application.
3.Initiate the Scan
The scanner parses the Burp Suite export, identifying endpoints, HTTP methods, and other critical details. Start the scan to analyze your API for vulnerabilities.
We hope this new feature helps streamline your security testing workflow. And of course, we wish you not too many criticals found 😉
We're excited to announce a new capability for our DAST scanner: support for HAR files as REST API schemas. This enhancement offers you greater flexibility when scanning your APIs for vulnerabilities, especially since generating a HAR file can be faster and easier than creating or maintaining a Swagger/OpenAPI specification.
HTTP Archive (HAR) files are JSON-formatted files that capture network activity, including requests and responses, between a client and a server during a browsing session. With this update, our DAST scanner can now ingest HAR files to interpret and scan REST APIs, simplifying the scanning process and expanding its capabilities.
HAR files capture actual API interactions, including dynamically generated requests and responses during runtime. This is particularly useful in scenarios such as:
Upload the HAR file to the DAST scanner via the API schema configuration interface:
Go to Security scan and click on New Application
Start scanning smarter, not harder 😉