Fix the Export Folder: robots.txt Is Not Access Control

A company website listed its staff export folder in robots.txt to keep it out of search engines. The folder has no sign-in, and robots.txt is public, so the listing told everyone where to look.

Take the folder out of robots.txt and require a staff sign-in in front of it. The public pages must still load, staff must still download exports, and robots.txt should keep doing its real job for the search pages.

Work through the bench tabs in order. Incident tells you what happened. Target shows the service and lets you use it as an ordinary user would. Fix is where you change the setting that caused the problem; the check table re-runs the platform's own test cases every time you save, and every row marked still works must stay green. Detect asks you to mark the log lines, or write a rule, that catch the misuse without flagging normal traffic. Explain asks a few short questions about why the fix works. When every step passes, Prove releases your flag.

Everything runs in a simulated, in-memory copy of the service built for you alone. The misuse cases are generated by the platform; you never need to write an attack, only the defence.