Fix the Page Build: Credential in an HTML Comment

A developer left a note with the reporting service credential inside an HTML comment on the marketing site. The browser hides comments from the rendered page, but every visitor receives the full markup.

Move the credential to the server's secret store, strip comments at build time, and rotate the credential so the leaked one stops working. The pages must still render, and the office must still sign in to reporting.

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.