How this template works
APIs Selection
The API selection filters in this template specify the criteria for selecting the API to be tested. In this case, the filters include the response code range (gte: 200, lt: 300) and the extraction of the URL from the response to be used in the subsequent request.
Execute request
The execute section defines the type of request to be executed and provides the necessary details for the request. In this template, a single request is executed, and the URL is modified using the extracted URL from the API selection filters. The modified URL is used to access the Actuator endpoint.
Validation
The validation section specifies the expected response code and payload for the executed request. In this template, the expected response code is 200, and the response payload should contain either "applicationConfig" or "activeProfiles". Additionally, the response payload should also contain either "server.port" or "local.server.port". These validations ensure that the Actuator endpoint is properly configured and sensitive environment information is not exposed.
Frequently asked questions
"The text editor in Akto is absolutely remarkable. Its user-friendly YAML format strikes the perfect balance between simplicity and power. With intuitive features like 'API selection filter', 'Execute', Validate' creating test rules becomes incredibly easy. Akto's test editor is a game-changer, enabling seamless creation of highly personalized and effective tests that could meet the needs of any modern day organization. "
Security team,
Rippling
Explore other tests
eSMTP - Config Discovery
Nginx - Git Configuration Exposure
Laravel - Sensitive Information Disclosure
Docker Container - Misconfiguration Exposure
Msmtp - Config Exposure
Parameters.yml - File Discovery
Mongo Express - Unauthenticated Access
Apache Airflow Configuration Exposure
Dockerrun AWS Configuration Exposure
Apache Config file disclosure
Appspec Yml Disclosure
CGI script environment variable
