How this template works
APIs Selection
The template uses API selection filters to specify the criteria for selecting APIs to test. In this case, it filters APIs based on the response code, ensuring that only APIs with a response code between 200 and 299 are selected. It also extracts the URL from the response and assigns it to the variable "urlVar".
Execute request
The template uses the "execute" section to define the type of request to be executed. In this case, it is a single request. It modifies the URL by appending "/appspec.yml" and "/appspec.yaml" to the extracted URL variable "urlVar". This allows the template to test for the presence of the appspec.yml file in the application deployment.
Validation
The template uses the "validate" section to define the validation criteria for the response. It checks that the response code is equal to 200 and that the response payload contains specific keywords such as "version:", "os:", and "files:". This ensures that the appspec.yml file is accessible and contains the expected deployment information.
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
CGI script environment variable
circleci config.yml exposure
