How this template works
APIs Selection
The template includes API selection filters that specify the desired response code range (between 200 and 299) and extract the URL from the response to be used in the execution step. These filters ensure that only successful responses are considered and the URL is extracted for further processing.
Execute request
In the execution step, a single request is made to modify the URL by appending "/apache.conf" to it. This modified URL is used to access the Apache configuration file. This step allows the template to perform the necessary action of accessing the configuration file.
Validation
The validation step ensures that the response received from the modified URL meets certain criteria. It checks if the response code is equal to 200, indicating a successful request. Additionally, it validates the response payload by checking if it contains either the "<Directory" and "</Directory" tags or the "<VirtualHost" and "</VirtualHost" tags. This validation confirms that the Apache configuration file has been successfully accessed and contains the expected content.
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
Appspec Yml Disclosure
CGI script environment variable
circleci config.yml exposure
