Escape's public HTTP API is getting better!
It is now possible to progrmmatically fetch your scans and applications from the public api. The documentation has also been improved in order to clearly show the API's base URL, and to present the new routes.
We also added the organization's id on the organization display of the platform. This way, you can now easily retrieve it to start using the API.
Hello everyone ! This week sees the release of a feature that has been heavily asked to us: You can now declare Slack, Discord and email notifications per applications.
If you had previous integrations setup, nothing changes, you will still be notified for every applications your organization has on Escape.
However, when creating a new Discord/Slack/email-based integration, you will be offered to select one or more applications of your organization. Only these applications will trigger the notification to be sent.
We are excited to announce the latest addition to our Escape security platform: the ability to generate a PDF report for auditors and customers:
• Quickly provide the documentation required for vendor assessments, accelerating sales with customers who prioritize security.
• Enables swift compliance with SOC 2 or ISO 27001, generating a PDF report with evidence in seconds.
• Share vulnerability details with auditors or developers for efficient resolution. Each failed test case by Escape results in a finding, including technical details for easy remediation and enhanced web app security.
We understand the importance of security and compliance and are dedicated to providing our customers with the tools they need to ensure they are meeting the necessary standards.
If you have any questions about the Escape security platform or this new feature, please don’t hesitate to contact our team. We are always happy to help and provide additional information.
Hey everyone! We’re excited to announce a new feature to our Escape security platform: static IP and proxy!
This advanced configuration option allows you to run the Escape scanner through the proxy of your choice.
Many of you wanted another way than headers to identify the requests from the Escape scanner. At Escape, we now provide a static IP option. Please get in touch with us if you wish to whitelist our IPs.
See more about Proxy and Static IP in the Advanced Configuration section of our developer documentation.
If you have any questions or feedback, don't hesitate to reach out - we're here to help. Thanks for being part of the Escape Community!
Welcome to the latest update on our Escape Security Platform! We’re excited to announce the latest feature to help keep your API secure and up-to-date. Today, we’re introducing a new testing coverage assessment to help you test your API's entirety.
With this testing coverage feature, you can effortlessly visualize the proportion of your API you want to test and obtain immediate actions on improving your scan configuration to benefit from the full potential of Escape.
With the testing coverage feature, you can be assured that your API security scan is properly configured and functioning as expected.
See our Developer documentation to understand how to improve your coverage :)
We’re excited to bring you this latest feature and hope it helps you improve how you configure and secure your API. Try out the testing coverage feature today and see how it can help you!
Hey there! Today we’re excited to announce a new feature for the Escape security platform: matching scan results with your Git commit hashes.
This new feature makes it easier to identify and fix vulnerable code in your CI/CD pipeline. With this update, you can now easily match the scan results of your Escape scans with the associated Git commit hashes so you can pinpoint the exact code changes that need to be addressed. No more guesswork or manual searching through logs to find the source of the vulnerability – now you can easily identify the changes associated with every build.
This streamlines the process and helps you stay ahead of security threats. We’re committed to helping our customers stay secure; this new feature is just the latest step in that process.
If you use Gitlab, Github or CircleCI, you have nothing more to configure! It's already working from scratch ;) For advanced configuration, check out our new developer documentation!
We hope you enjoy the new update, and please don’t hesitate to reach out if you have any questions or feedback.
Hey everyone! We’re excited to share that we’ve just released a new feature to the Escape Security Platform.
We want to ensure that you always have the most up-to-date information available to protect your data with the highest level of security. By default, Escape always fetches the latest introspection of your application available.
The Introspection Update from CI/CD Hooks allows users with closed introspection to ensure that their security measures stay updated every time a build is released by uploading their schema.graphql or introspection.json at every builds directly from their CI/CD.
See more on our CI/CD documentation.
If you have questions about the Introspection Update from CI/CD Hooks feature, please don’t hesitate to contact our support team. We’re always happy to help.
Hey there! We're proud to announce the availability of the most requested feature on the platform!
It allows you to change the scan configuration on the fly inside your CI/CD, for example, to start fast scans with fresh authentication tokens at every new build of your application. See more on our CI/CD documentation.
We would love to have your feedback on this new feature, feel free to reach us on our Discord Community server!
We just released brand new developer documentation, providing detailed and hierarchized information for you to benefit from the full potential of Escape and make your GraphQL applications more secure.
The developer documentation can be found at the same URL: https://escape.tech/docs
Please let us know if you have any questions or feedback. We're always looking for ways to improve our developer experience.