Australian small-business average reported cybercrime cost per report, 2025–26.
ASD Annual Cyber Threat ReportFictional example. All findings invented for demonstration. No real scan data.
Small Business Edition
Passive cyber exposure report
Example Workshop · example.com
Read this sample as a business owner, then pass the technical brief to your IT provider.
Scorecard
| Area | Status | Illustrative observation |
|---|---|---|
| Email impersonation | DMARC (your email anti-impersonation setting) is set to monitor only. | |
| Mail sender list | A public sender policy is present. | |
| Website encryption | Public records indicate a certificate for the main website. | |
| Public contact | The main contact is a shared business address. | |
| Old sign-in address | Public records mention a legacy sign-in hostname. | |
| Similar domain name | One similar address is worth reviewing for ownership. | |
| Extra sign-in protection | Private account controls aren't visible from public records. |
Why this matters
Reported Australian payment-redirection scam losses, 2025.
National Anti-Scam CentreCybercrime reports in 2025–26, about one every six minutes.
ASD Annual Cyber Threat ReportIllustrative scam scenarios
- Changed invoice details. An email appears to come from a supplier and asks you to pay another account. Verify payment changes by calling your existing contact number.
- Fake staff request. Someone poses as a manager and asks for an urgent purchase. Confirm unusual requests through a separate channel.
- Look-alike sign-in page. A similar web address can be used to impersonate your business. Share the correct address and ask staff to report suspicious links.
Your three priorities
1. Review email impersonation protection
- What we saw
- Illustrative DMARC policy of
p=none. - Why it matters
- It requests monitoring but leaves delivery decisions to receiving providers.
- What to do
- List authorised senders and agree a staged enforcement plan.
- Who
- Your IT provider and whoever manages invoices.
- Effort
- 1–2 hours to scope, then a monitored rollout.
- Done when
- Legitimate mail still arrives and a reviewed enforcement policy is in place.
2. Confirm the old sign-in address
- What we saw
- An illustrative public reference to
login-old.example.com. - Why it matters
- An unowned service can be missed during updates or account reviews.
- What to do
- Check the service inventory and confirm whether to retain or retire the address.
- Who
- Your IT provider.
- Effort
- 30–60 minutes to confirm ownership.
- Done when
- The address has a documented owner and purpose, or has been retired.
3. Set a payment-change rule
- What we saw
- The fictional site publishes a general accounts contact.
- Why it matters
- Someone can target the accounts team with a believable request.
- What to do
- Confirm new bank details by calling a number already on file.
- Who
- The business owner and accounts team.
- Effort
- 30 minutes to agree and share the rule.
- Done when
- Staff can describe the rule and know where to record checks.
What's working well
Published sender policy
Provides a starting point for confirming who may send on the business's behalf.
Certificate on record
Public certificate records show coverage for the main website address.
Shared contact address
Customers have a contact channel without needing a staff member's direct address.
Your next 30 days
- Week 1: Nominate the IT owner and share this briefing. Done when every priority has an owner.
- Week 2: Confirm approved email senders. Done when invoicing, marketing and support senders are on one list.
- Week 3: Review the old sign-in hostname and similar address. Done when the provider has recorded ownership and next steps.
- Week 4: Introduce and rehearse the payment-change rule. Done when staff have tried it on an example request.
Complete the picture: an Active Scan
A separately quoted Active Scan uses a signed authorisation and agreed scope.
| Area | Free passive report | Active Scan (paid, optional) |
|---|---|---|
| Scope | Public records only. No direct testing. | Agreed internet-facing systems. Written permission and rate limits apply. |
| Old hostname | A hostname appeared in public records. | Example result: the agreed hostname was no longer reachable. |
| Mail protection | The public policy indicated monitoring. | Example result: the approved check showed the stated policy needed follow-up. |
| Cost | Free | Quoted separately |
Brief for your IT provider
| Illustrative evidence | Validation and action |
|---|---|
_dmarc.example.com p=none | Verify current policy and sender alignment. Review reports before moving to enforcement. |
login-old.example.com | Check current inventory, ownership and access controls. Retire the address if it is no longer needed. |
example.com certificate record | Confirm the certificate on the production site and track expiry. |
How we did this
A passive review uses public records such as the Domain Name System (DNS, the internet's address directory), certificate records and public listings. Findings describe what was visible at the time.
Internal controls, current software versions and compromise status require separate evidence. The evidence in this sample is invented.
Sources for the national figures and guidance include the ASD Annual Cyber Threat Report 2025–26, the National Anti-Scam Centre's Targeting Scams 2025 report and the ACSC Small Business Cyber Security Handbook.
