A software company adding online payments
The refund button
The challenge. A small software company is adding a customer portal with payments and refunds. The developers are careful and the code is clean. Nobody has asked what happens if a support account is taken over, or if a customer changes an invoice number in a web address.
The insight. Most serious flaws are in the design, not in a line of code. Drawing the system as a diagram and asking four questions of each part (what are we building, what can go wrong, what will we do about it, did we do it well) finds them while a change is an hour’s work.
The decision. The company made a one-hour threat model a step in its normal design review for any change that touches money or personal data.
The action. We ran the first session with the developers and the product owner. We drew the data flows, listed the threats by part, ranked them by likelihood and effect and picked the few that mattered: a role check on every refund, a limit on refund size without a second approval, and a log entry for every change to a payment record. The developers built them, and we reviewed the result.
The result. The three safeguards shipped with the feature. The company now holds a one-page model for the portal and updates it when the portal changes.