MENU
Refer to the exhibit.
Refer to the exhibit. A security analyst notices that a web application running on NGINX is generating an unusual number of log messages. The application is operational and reachable. What is the cause of this activity?
The provided log file contains multiple HTTP GET requests attempting to access various directories and files on the web server such as:
/balance
/security
/finance
/secret
/opt
/fuzzer/admin
These requests appear to be sequential, systematically targeting commonly used file and directory paths. The response codes are mostly 404 (Not Found) and a few 301s, indicating that the requester is trying different permutations of paths to discover hidden or vulnerable endpoints. This behavior is consistent with directory fuzzing, a reconnaissance technique used by attackers (or automated tools) to map out web directory structures by sending a high volume of crafted requests to guess hidden or unlinked directories and files.
This is distinct from DDoS (which would manifest as volume-based access issues), SQL injection (which targets specific parameters within requests), or botnet infection (which generally involves command-and-control communication or massive traffic floods).