A personal playbook
Light iton paperfirst.
Backburn Cyber is a personal security playbook and an expert showcase. It describes an AI-assisted, read-only review, and each finding gets a second, separate review pass. That record gives you evidence you can show your board, insurer and regulator.
This is not a penetration test. Not currently taking clients.
Anatomy of
a review
Read only, from the first look to the page you keep. Nothing here is an offer of work.
Old accounts, weak sign ins, untested backups, stale keys, unpatched servers, code nobody has reviewed
- 01
Map the fuel
Accounts, sign in, backups, keys and patching. The review lists the fuel before it judges any of it. Nothing on the systems is changed.
- 02
Read it twice
An AI-assisted pass drafts the findings. Each finding then gets a second, separate review pass. This is not a penetration test.
- 03
Leave a record
What remains is written in plain English, with a severity on Backburn's own scale. The record gives you evidence you can show your board, insurer and regulator.
What the
notes cover
Five parts of the same notebook. They describe a way of working. They do not sell it.
- 01
Reading the estate
Accounts, sign in, devices and backups. Where the estate is Microsoft 365 or a similar set of services, it is assessed against the ASD Essential Eight Maturity Model. An assessment against the model is not a claim of compliance, certification or ASD endorsement.
- 02
Outside the eight
Email authentication and vendor checks are written up on their own. They sit outside the Essential Eight, and they are not folded into that assessment.
- 03
Two readings
The review is AI-assisted and read only. Each finding gets a second, separate review pass before it is written into the register. This is not a penetration test.
- 04
Controls, described
Our recommendations come from running these controls ourselves: sign in rules, email authentication, release gates, and backups that have been restored for real. The playbook describes them. It does not offer to carry them out.
- 05
If it breaks
An incident plan, a tabletop, and a small kit for the day they are needed, written so a board can follow the thread.
The holes,
on one page
A security register puts open holes on one page: what each one is, what could go wrong, what is exposed and how severe it is. The rows below are a fictional retail firm, a shop and its back office. They are not a record of any real review. A real register, kept current as holes are closed, is the sort of page you can show a board, an insurer or a regulator.
- Moderate
- High
- Extreme
- Catastrophic
- Fixed or passed
- Regrowth means fixed or passed
| Ref | Security hole | Risk | Exposure | Severity | Likelihood | Status |
|---|---|---|---|---|---|---|
| BB-001 | Two admin accounts sign in with a password only | One phished password hands over the whole Microsoft 365 tenant. | Staff mailboxes and the shared files. | Catastrophic | Likely | Open, due in 3 days |
| BB-002 | Backups have never been restored | After ransomware the backups may fail when they are needed. | The shop systems. Up to 30 days of records. | Extreme | Possible | Drill booked |
| BB-003 | Anyone can send email as the company domain | Fake invoices and changed payment details sent in the company name. | Customers and payment instructions. | Extreme | Likely | Open, due in 7 days |
| BB-004 | Four former staff accounts still active | Old credentials reused to get in without anyone noticing. | The shared drive and the order list. | High | Possible | Open, due in 14 days |
| BB-005 | Shop admin has no sign in limit | Passwords for the back office can be guessed at machine speed. | The product catalogue and stored orders. | High | Possible | Fix in testing |
| BB-006 | Service keys kept in a shared spreadsheet | One leaked file opens the paid services behind the business. | The card machine provider, the parcel tracker, and the email tool. | High | Possible | Open, due in 14 days |
| BB-007 | Three of 22 laptops are not encrypted | A lost laptop becomes a notifiable data breach. | Staff files saved on the device. | Moderate | Unlikely | 2 of 3 done |
| BB-008 | No written incident plan | A slow, improvised response on the worst day of the year. | The shop and its supplier deadlines. | Moderate | Possible | Open, due in 30 days |
These entries are fictional. The severity scale is Backburn's own, not an official rating. Moderate, high, extreme and catastrophic are labels for findings on that scale. Regrowth green is reserved for a control that is fixed or has passed, and it is not used on the rows above.
From a boundary
to a record
A walkthrough of the method only. It names no firm and no sector, and it uses no figures.
- Boundary
Set the boundary
Agree what will be read: identity, mail, devices, backups, and the vendors a firm depends on. The work is read only. It does not change those systems, and it is not a penetration test.
- Reading
First reading
An AI-assisted pass walks that boundary and drafts each finding in plain English: the hole, what could go wrong, and what is exposed.
- Again
Second pass
Each drafted finding gets a second, separate review pass. A claim that does not hold is left out. What remains is rated on Backburn's own scale, which is not an official rating.
- Record
The record
The register is what you keep. Our recommendations come from running these controls ourselves. The record gives you evidence you can show your board, insurer and regulator.
Most security writing comes from people who have not had to keep a business running while they tightened the controls.
The author writes these notes from running production systems: sign in, backups, an incident plan, and the page a board reads. Our recommendations come from running these controls ourselves, and they are written in plain English. Not currently taking clients.
A letter, when
there is one.
Field notes will be short and occasional. There is nothing to buy, and no engagement to book.