The delay is usually the expensive part
Most small-business incidents do not begin with a specialist attacker in a darkened room. They begin with an ordinary inbox: a supplier invoice, a login prompt, a code from an authenticator app, a “quick remote session”, or a message that looks like the owner. Someone acts, then realises it feels off.
What happens next is a people problem as much as a technical one. If the expected response is “how could you be so careless?”, people wait, hope and try to fix it quietly. Meanwhile a payment can still leave, a mailbox rule can still forward mail, or a customer can still be asked to pay a fake invoice.
The Australian Cyber Security Centre’s current small-business handbook treats staff awareness as a control, not a slogan. It asks businesses to train people to spot scams and phishing, to verify payment requests through a trusted channel, and to make reporting of suspicious activity part of ordinary work. That only works if reporting is safe.
Decide who “report it” means this week
In a five-person business, “report it” should not mean “fill in a government form before you tell anyone”. Internal reporting comes first. Official reporting comes when money, accounts, customers or ongoing access may be involved.
Write three names on a card that is not stored only in the mailbox:
- Who staff tell first. Usually the owner, or one named deputy when the owner is on a job.
- Who can pause payments. The person who actually pays invoices or payroll.
- Who can lock an account. The person who can change an email password, end sessions or call the IT helper.
Include casuals, weekend staff and any family member who answers the shop phone or pays a supplier. If they can click, they need the same sentence: tell the named person straight away.
Say this before anything happens
Owners should say it out loud, once, in a normal meeting — not after a scare. Adapt the names; keep the meaning.
Owner to the team: “If a message, payment, login or code feels wrong, tell me or [deputy] immediately. You will not be in trouble for speaking up, even if it turns out to be nothing. The costly mistake is the one we hear about a day later.”
Staff, when they need the sentence: “This may be nothing, but I want you to know now. I [clicked / paid / shared a code / gave screen access] at about [time], on [account or device].”
That is enough to start. A perfect timeline can wait.
How to receive a report without freezing the person
The first thirty seconds teach the team whether the promise was real. Use this order:
- Thank them. “Good. You did the right thing telling me.” Do not ask why they fell for it.
- Stop further harm. If money may be moving, call the bank using the number on the card or in the official app — not a number in the suspicious message. If a login or mailbox may be involved, lock that account from a device you still trust. If someone has remote access to a screen, end the session and disconnect.
- Ask four facts, then stop interviewing. What did they do? Which account or device? Did money leave? Can they still see the message?
- Warn the next person if needed. If customers or suppliers may receive a fake invoice from you, tell them through a channel you already trust.
- Keep the evidence. Do not delete the email or chat in anger. A screenshot or the original message is enough for later.
Lessons belong in a calmer conversation after the risk is contained. If the first response is blame, the next incident will go unreported.
What to capture in sixty seconds
Staff do not need a forensic pack. ACSC may later ask larger organisations for logs or technical samples; a cafe or trade business usually needs a short note the owner can read while calling the bank.
- Time and date, even if approximate.
- What happened in one line: clicked a link, opened an attachment, paid an invoice, shared a code, approved a sign-in, or allowed remote access.
- Which mailbox, payment system, phone or computer.
- Whether money, bank details or customer information may be involved.
- Whether anyone else was copied, or whether a customer might act on a message from the business.
- Whether the original message is still visible.
If they cannot answer a point, write “unknown” and keep going. Incomplete information reported now is more useful than a complete story tomorrow.
A ten-minute rehearsal, not a trap
ACSC asks small businesses to make an incident plan and to test it in a simple way, including how staff report, who they contact, and how the business will communicate if systems are down. It also says a copy of the plan should be available offline. That can be a paper card in the till drawer.
Once a quarter, use ten minutes at the end of an ordinary meeting:
- Pick one likely scenario for this business: a changed-bank-details invoice, a fake owner message asking for a code, or a “support” call asking for screen access.
- One person plays the reporter and uses the staff sentence above.
- The owner or deputy plays the receive script: thank, pause payments if needed, lock the relevant account, ask the four facts.
- The team names the first three real contacts: bank number, email recovery path, and who warns customers.
- Thank the reporter again, in front of everyone. That is the point of the drill.
Do not run a surprise phishing test on the same day, and do not publish a “who failed” list. A gotcha exercise can train people to hide mistakes. If you later use a simulated phishing email, tell the team in advance that it is training, score the process (did they report it?) rather than the person, and never attach the result to pay or humiliation.
When to take it outside the business
Internal reporting is not the end. ACSC’s current advice is to report a potential incident as soon as possible, even if it may be a false alarm or it happened some time ago. Early contact can bring advice and helps warn other Australians. Some sectors have extra mandatory reporting rules; most microbusinesses should not guess those from memory.
Use official channels in this order of urgency:
- Money or cards. Your bank or payment provider first, using its official app, website or the number on the card.
- Advice during an incident. Australian Cyber Security Hotline, 1300 CYBER1 (1300 292 371), 24 hours a day. ACSC can give advice; it does not recover lost money or provide hands-on repair of your device.
- Cybercrime and incidents. Start at cyber.gov.au/submit-a-report. To report a cybercrime to police, use the ReportCyber path linked from that page. The separate “report a cyber security incident” form is aimed at large organisations, government and critical infrastructure — not the default for a small shop.
- A scam pattern affecting customers or payments. The National Anti-Scam Centre’s Scamwatch service is the consumer-facing reporting path listed by COSBOA’s Cyber Wardens guidance.
- Calm, practical support for a very small team. IDCARE’s federally funded Small Business Cyber Resilience Service is free for eligible Australian businesses with 19 or fewer full-time equivalent employees, excluding the owner, that are actively trading with a valid ABN. Check current eligibility at idcare.org/smallbusiness or call 1800 595 170 during the published business hours.
Privacy notification is a separate question. If customer or staff personal information may have been exposed, check current OAIC guidance rather than assuming the Privacy Act does or does not apply because of turnover alone.
Sources and further reading
- Cyber.gov.au — Small business hub
- Cyber.gov.au — Educate staff on good cyber security practices
- Cyber.gov.au — People, training and incident readiness
- Cyber.gov.au — Implement and test cyber security incident response plans
- Cyber.gov.au — How we help during a cyber security incident
- Cyber.gov.au — Submit a report
- IDCARE — Small Business Cyber Resilience Service
- business.gov.au — Cyber security
Frequently asked questions
Do we report every odd email to the ACSC?
No. Tell the named person in the business first. Use official reporting when there is suspected fraud, customer exposure, locked or misused accounts, or access you cannot explain. When you are unsure and the impact may be real, ACSC’s public position is that it is better to report early than to wait for certainty.
What if the owner is the person who clicked?
The same habit applies. Tell the deputy or bookkeeper, pause payments, and lock the affected account. A no-blame rule that excludes the owner will not survive the first real incident.
Should we punish a second mistake?
Repeated reckless handling of money or customer data is a management issue, and it should be handled as one — after the incident is contained. The first conversation still needs to collect facts and stop further harm. If people believe the second report is the dangerous one, they will delay that report too.
Keep going
If you want a short, practical session for the people who actually pay invoices and reset passwords, see our cyber safety training. For questions about courses or on-site sessions, use Contact Us.