Skip to content
TheTrainingChannelTM

The Living Case Study · October 19, 2026

Four Kinds of Problems

How to tell poor presentation, information disclosure, a configuration risk, and an exploitable weakness apart.

Poor presentation

Poor presentation means the page was written for the wrong reader. A student meets notes that were meant for the person updating the site. The lesson is harder to use. The correction is to rewrite the page for the student and keep the builder notes in a work file that the public site does not serve.

Information disclosure

Information disclosure means a public page reveals something about how the site is put together. It might name the kind of setting a feature is waiting on, or answer whether a service is ready. The secret value can still be absent. The map is still worth closing, because a stranger did not need it.

Configuration risk

A configuration risk means a protection is missing, weak, or inconsistent. Familiar examples are a sign-in form that accepts unlimited guesses, browser protections that were never turned on, and two passes stamped so similarly that one could stand in for the other.

A configuration risk is a job to fix and then test. Calling it a breach takes a separate fact: evidence that someone used it.

An exploitable weakness, and a breach

An exploitable weakness is a path that works. A person can use it to enter, to take data, or to knock the service over. A breach is that path together with evidence of use, or evidence that data already left.

One event can sit in more than one bin. Builder notes on a public page are poor presentation and information disclosure. If those notes had included a working password, the event would also be exposure of a secret. The October 19, 2026 review did not find a working password on a public page.