A prototype that works when you try it has passed one test, which is that it works for you, once, when nothing goes wrong. Before real customers use it you need to know how it behaves for strangers, in numbers and on a bad day. The twelve checks below need no technical knowledge, only the prototype, a second device and a friend, and each one says what a pass looks like. They cannot prove that a product is secure, which takes a proper review, but they do catch the faults we find most often.
Before You Start
Create two test accounts with different email addresses and add a few invented records to each, so that there is something to protect. Keep a note of every result as you go, because the pattern across the checks will tell you more than any single one.
Sign-In and Access
- Open a signed-in page without signing in. Copy the address of a page from inside your account, sign out and paste it into a private browser window. A pass is being sent to the login screen.
- Look at someone else's record. Signed in as the first account, open a record and change the number or code in the address to one that belongs to the second account. A pass is a refusal, and a fail is seeing the other account's data.
- Visit the admin area as an ordinary user. If the product has an admin screen, open its address while signed in to a normal account. A pass is being turned away.
Data and Backups
- Find out where the data lives. Ask the tool, or whoever built the prototype, to name the database and the company that hosts it. A pass is a clear answer and an account you can sign in to yourself.
- Ask for yesterday's copy. Delete one test record and ask for it to be restored from a backup. A pass is getting the record back, and being told that backups exist does not count until one has been restored.
When Things Go Wrong
- Submit twice. Press the pay or save button twice in quick succession. A pass is one order and one charge.
- Decline a card. Use your payment provider's test card for a declined payment. A pass is a clear message to the customer and no order left half made.
- Drop the connection. Turn off the wifi halfway through saving a form, then turn it back on. A pass is either a saved record or a clear warning, and a fail is the work disappearing without a word.
More Than One User
- Edit the same thing at once. With a friend, open the same record on two devices, change different fields and save. A pass is both changes being kept, or a warning to the second person.
- Bring a crowd. Ask ten people to sign up and use the prototype in the same five minutes. A pass is nobody noticing anything unusual.
Ownership
- Check whose name is on the accounts. List the code, the hosting, the domain and the payment account, and write beside each one who owns the login. A pass is your company on all four.
- Ask where the secret keys are kept. Ask the tool to list every password and key the product uses and where each one is stored. A pass is none of them written into the code or visible in the browser.
Reading the Results
| What you found | What it means | What to do |
|---|---|---|
| Every check passed | The most common faults are absent | Launch to a small group, and have it reviewed before you grow |
| Fails only under Ownership | The product may be sound, but parts of it belong to somebody else | Move the accounts and keys into your name before launch |
| Fails under When Things Go Wrong or More Than One User | It will work until it gets busy | Fix these before taking payments or promoting it |
| Any fail under Sign-In and Access or Data and Backups | Customer data would be at risk from the first day | Keep real customer data out of it until this is fixed |
Test with invented data only
Run every check using test accounts and made-up records. If one of them fails, you will be glad that the data it exposed belonged to nobody.
Common Questions
You can, and for a single fault it often works. The risk is that each fix is made without a view of the whole product, so one repair can quietly undo another. After any fix, run all twelve checks again, including the ones that passed before.
No. These checks catch the faults we see most often, and a prototype that passes all of them is in better shape than most. A full review reads the code and the configuration, tests the product the way an attacker would and covers a great deal that cannot be seen from the outside.
Rarely. The screens and the flow that people already understand usually stay, and the work goes into what sits underneath them.
BY BANKS reviews prototypes, keeps what works and rebuilds what would break, so that the product is one you can put in front of real customers. That is our prototype to production service, and the deeper testing belongs to our cyber security work. If your prototype failed any of these checks, get in touch and tell us which ones.
Ready to Build Something?
If this resonated, let's talk about how we can apply these ideas to your business.
Start a Conversation