§1 Report sheetWL-2274 / Sample report

number changed to read another customer's invoices
Client | Freight payments platform |
Test type | Web and API |
Scope | Customer portal and public API, eight days. |
Findings | 1 Critical, 4 High, 8 Low |
Result | Customer data read |
Written for the client's board. The client is fictional and the name is withheld.
We tested the customer portal and the public API by hand for eight days, using two test accounts we were given.
Two test accounts and a proxy were enough. Invoice records were checked for a session, but never for an owner.
Ownership checks moved into one shared layer. The retest used new IDs and read nothing.
§3 TimelineWL-2274 / Sample report
Sample timeline, taken from the test log. Every action has a time.
When | Step | By |
Day 0 | Scope, test windows and stop contact signed | Lead |
Day 1 | Two test accounts set up, API calls mapped | Tester |
Day 2 | Invoice ID changed in a call, second account's invoice returned | Tester |
Day 2 | Named contact phoned with the proof and a fix | Tester |
Day 3 | Same flaw checked across the remaining record types | Tester |
Day 8 | Testing closed, findings written up | Tester |
After the test | ||
Day 8 | Report read through with the client on a call | Lead |
Day 21 | Ownership checks moved into one shared layer | Client IT |
Day 38 | Retest with new IDs: nothing read | Tester |
§4 FindingsWL-2274 / Sample report
Severity | Finding | Closed |
Critical | Invoice records returned without an owner check | Day 38 |
High | Payment records open to the same change | Day 38 |
High | No limit on repeated record requests | Day 38 |
High | Record IDs issued in sequence | Day 38 |
The other 9 stay in the client's copy.

§5 Client noteWL-2274 / Sample report
It was one number in one call. Seeing it done on our own test account ended every argument about priority.
Every record checked for an owner, in one layer
A limit on repeated record requests
Ownership tests added to each release
§6 More reportsEnd of WL-2274