Small Business Website Risk Assessment – Brochure Site + Contact Form
The Australian Government recently introduced the Digital Duty of Care bill.
You can download it here:
The post below was written by AI – not my own work, but I have read it and made edits where I saw fit.
Get in touch with your online service provider as soon as you can to audit and remediate anything in the list below.
This is important – don’t put it off. I know it’s another burden on your already stressed out psyche, but I want you to realise this is very real, and you need to protect yourself.
View the very informative video by Tax Invest Accounting on this topic here:
https://www.facebook.com/reel/959361110582754
Small Business Website Risk Assessment
Brochure Site + Contact Form
Risk Register
Scope: Small business brochure website with a single contact form that emails the site owner.
Platform: HTML (assumed – a single page).
Jurisdiction: Australian users only.
Excluded: payments, user accounts, user-generated content (UGC), newsletter/marketing.
Status: v0.1 — draft for review.
Review cadence: quarterly, and after any change (new plugin, new form, new staff, new host).
Scoring
- Likelihood (L) 1 = rare … 5 = almost certain
- Impact (I) 1 = negligible … 5 = severe (legal, financial, reputation, or loss of the business)
- Score = L × I — prioritise from the top
| Score | Band | Action |
|---|---|---|
| 15–25 | Critical | Fix now |
| 8–12 | High | Fix this quarter |
| 4–6 | Medium | Plan / monitor |
| 1–3 | Low | Accept / review annually |
Treatment: Mitigate · Accept · Transfer (insurance) · Avoid
Register
| # | Asset | Threat | Vulnerability | Existing controls | L | I | Score | Band | Treatment | Owner | Status |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Website / CMS | Compromise via outdated WordPress core/theme/plugins (supply chain) | Auto-updates off, unused plugins present, no WAF | Unknown — verify | 3 | 4 | 12 | High | Mitigate | Site owner | Open |
| 2 | Admin access (wp-admin) | Account takeover | No MFA, weak/reused password, generic “admin” username | Unknown — verify | 3 | 4 | 12 | High | Mitigate | Site owner | Open |
| 3 | Backups | Ransomware / accidental deletion / host loss, no tested restore | Backups not offsite or never test-restored | Unknown — verify | 3 | 5 | 15 | Critical | Mitigate | Site owner | Open |
| 4 | Domain / DNS | Domain or DNS hijack (site + email lost) | Registrar account not MFA’d / not locked, unclear expiry owner | Unknown — verify | 2 | 5 | 10 | High | Mitigate | Site owner | Open |
| 5 | Email domain | Spoofing / phishing sent “as” the business | No SPF/DKIM/DMARC records | Unknown — verify | 3 | 3 | 9 | High | Mitigate | Site owner | Open |
| 6 | Contact form | Spam, bot abuse, mail-relay / header injection | No CAPTCHA/honeypot, weak server-side validation | Unknown — verify | 4 | 2 | 8 | High | Mitigate | Site owner | Open |
| 7 | Owner inbox | Contact messages (name/email/message = personal info) leaked if inbox compromised | Email account lacks MFA; old enquiries retained forever | Unknown — verify | 2 | 3 | 6 | Medium | Mitigate | Site owner | Open |
| 8 | Legal / privacy | No privacy or collection notice on the form | Form collects personal info with no notice | Unknown — verify | 3 | 2 | 6 | Medium | Mitigate | Site owner | Open |
| 9 | Accessibility | DDA non-compliance (WCAG 2.1/2.2 AA) | No alt text, poor contrast, keyboard traps, no audit | Unknown — verify | 3 | 3 | 9 | High | Mitigate | Site owner | Open |
| 10 | Content / IP | Unlicensed images, fonts, or music | No licence register; assets sourced without records | Unknown — verify | 3 | 2 | 6 | Medium | Mitigate | Site owner | Open |
| 11 | Hosting | Outage / TLS certificate expiry / mixed content | No uptime monitoring, manual cert renewal | Unknown — verify | 3 | 3 | 9 | High | Mitigate | Site owner | Open |
| 12 | Third parties | Analytics / fonts / CDN leak visitor data overseas (APP 8 cross-border) | Third-party scripts loaded without review or disclosure | Unknown — verify | 3 | 2 | 6 | Medium | Mitigate | Site owner | Open |
| 13 | People | Phishing of the owner via the contact form (fake customer, malicious link/invoice) | No process to verify requests out-of-band | Unknown — verify | 3 | 3 | 9 | High | Mitigate | Site owner | Open |
| 14 | Maintenance | Bus factor — no one owns/updates the site | Credentials held by one person, undocumented, no calendar | Unknown — verify | 3 | 4 | 12 | High | Mitigate | Site owner | Open |
Priority order (highest first)
- #3 Backups (15) — onsite + offsite, test a restore, document recovery steps.
- #1 Patching (12) — enable auto-updates, remove unused plugins/themes, add a WAF.
- #2 Admin access (12) — MFA on wp-admin, strong unique passwords, least privilege, change default
adminuser. - #14 Bus factor (12) — named owner, documented credentials (password manager), quarterly review calendar.
- #4 Domain/DNS (10) — registrar MFA + transfer lock, expiry alerts.
- #5, #9, #11, #13 (9) — DMARC, WCAG pass, uptime/TLS monitoring, phishing awareness.
Remediation Checklist
Actions mapped to risk IDs above. Tick items as they are completed.
Quick wins (do this week)
- [ ] #3 Backups — Confirm the host takes backups. Add an offsite backup (plugin or host feature). Store one copy outside the host account. Restore to a test environment and verify. (3-2-1: 3 copies, 2 media, 1 offsite.)
- [ ] #2 Admin access — Enable MFA on every WordPress admin account. Use a password manager; unique passwords. Remove the default
adminusername. Give each user the minimum role needed. - [ ] #1 Patching — Turn on auto-updates for WordPress core and security releases. Delete unused plugins and themes (don’t just deactivate). Enable a WAF (host-provided or Cloudflare free tier).
- [ ] #5 Email spoofing — Publish SPF, DKIM, and DMARC DNS records. Start DMARC at
p=none, review reports, then move toquarantine. - [ ] #4 Domain/DNS — Enable registrar transfer lock and MFA. Set a domain-expiry alert (calendar). Confirm the registrant email is one you control.
- [ ] #14 Bus factor — Record all logins in a shared password manager. Name a backup owner. Add a recurring quarterly review.
Short term (this quarter)
- [ ] #6 Contact form — Add CAPTCHA (e.g. hCaptcha/Turnstile) and/or a honeypot. Rate-limit submissions. Ensure the form is server-side validated and cannot be used as a mail relay or for header injection.
- [ ] #7 Inbox / retention — Enable MFA on the email account. Set a retention rule: delete or archive enquiries older than 12 months.
- [ ] #8 Privacy notice — Add a short collection notice to the form and a privacy policy page (see
assumptions.mdfor content). - [ ] #9 Accessibility — Run an automated check (axe, Lighthouse) then manual keyboard + contrast checks. Fix alt text, headings, focus order, contrast to WCAG 2.1 AA.
- [ ] #11 Hosting — Add uptime and TLS-expiry monitoring (host tool or free monitor). Enable auto-TLS renewal.
- [ ] #13 Phishing — Never act on contact-form requests for payment or credential changes without verifying out-of-band (phone a known number).
- [ ] #10 Content/IP — Create a simple licence register: asset, source URL, licence, date. Replace anything unlicensed.
- [ ] #12 Third parties — Inventory scripts/tags (analytics, fonts, CDN). Self-host fonts where possible. Disclose overseas data flows in the privacy policy.
Ongoing / quarterly
- [ ] Re-score the register every quarter.
- [ ] Re-test one backup restore per quarter.
- [ ] Review DMARC reports; review user accounts and access.
- [ ] Re-check after any change: new plugin, new form, new staff, new host, new data type.
Glossary
Plain-English definitions for the terms used in this risk assessment. Grouped loosely, alphabetical within each section.
Risk assessment terms
- Asset — Anything of value worth protecting: the website, admin logins, the domain, the owner inbox, reputation, customer trust.
- Risk — The chance of something bad happening multiplied by how bad it would be. Here, scored as L × I.
- Likelihood (L) — Probability the threat succeeds, 1 (rare) to 5 (almost certain).
- Impact (I) — How much damage if it does, 1 (negligible) to 5 (severe).
- Risk register — The living table of risks, scores, owners, and status.
- Treatment — What you do about a risk: Mitigate (reduce it), Accept (live with it), Transfer (insurance), Avoid (stop the activity).
- Threat — Who or what could cause harm (hackers, malware, staff error, fire).
- Vulnerability — The weakness that lets a threat succeed (no MFA, outdated plugin).
- Control — A safeguard that reduces likelihood or impact (a firewall, a backup).
Authentication & access
- MFA (Multi-Factor Authentication) — Logging in with more than a password, e.g. password + one-time code. Stops most account takeovers even if the password leaks.
- 2FA (Two-Factor Authentication) — Same idea, exactly two factors. MFA is the general term.
- Password manager — A tool that stores unique, strong passwords behind one master password. Avoids reuse.
- Least privilege — Give each person only the access they actually need.
- Admin account — A login with full control of the site (e.g. WordPress administrator). Highest-value target.
- Credential stuffing — Attackers try leaked username/password pairs on your site, hoping you reused them.
- Bus factor — The number of people who must be hit by a bus before the project stalls. Here, “1” means all knowledge sits with one person.
Web & hosting
- CMS (Content Management System) — Software for building/editing a site without coding. WordPress is one.
- WordPress — The most common CMS. Runs on a core plus themes (appearance) and plugins (features).
- Plugin — Add-on code for WordPress. A top attack path when outdated or abandoned.
- Theme — The visual template of a WordPress site. Also needs patching.
- wp-admin — WordPress’s admin dashboard URL; the login attackers target.
- WAF (Web Application Firewall) — Filters malicious web traffic before it reaches the site (e.g. Cloudflare, host WAF).
- CDN (Content Delivery Network) — A global network that serves your site’s files faster; also can filter attacks.
- DNS (Domain Name System) — The internet’s address book, turning your domain into a server address. Hijack it and attackers control your site.
- Registrar — The company where the domain is registered.
- Registrar lock / transfer lock — A setting that blocks unauthorised domain transfers.
- TLS / certificate / HTTPS — Encryption for traffic between visitors and your site. Expired cert = “not secure” warnings.
- Mixed content — A secure page loading insecure (HTTP) resources; browsers flag it.
- Uptime monitoring — An external service that alerts you when the site goes down.
- Supply chain attack — Compromise via third-party code (a plugin, a library, a font CDN) rather than your own code.
Email security
- SPF (Sender Policy Framework) — DNS record listing which servers may send email for your domain.
- DKIM (DomainKeys Identified Mail) — A cryptographic signature proving an email really came from your domain.
- DMARC — A policy that tells receiving servers what to do with mail failing SPF/DKIM, and sends you reports.
p=none= monitor only. - Spoofing — Sending email that pretends to be from your domain.
- Phishing — A fake message tricking someone into clicking a link, paying, or handing over credentials.
- Mail relay — Using your server/form to send mail you didn’t intend. An abused contact form can become one.
- Header injection — Injecting extra email headers via form fields (e.g. to add hidden recipients).
Backups & resilience
- 3-2-1 backup — 3 copies, on 2 different media, with 1 offsite. Protects against ransomware, deletion, and host loss.
- Test restore — Actually restoring a backup to prove it works. An untested backup isn’t a backup.
- Ransomware — Malware that encrypts your files and demands payment.
- Incident response — Your plan for what to do when something goes wrong.
Contact form & abuse
- CAPTCHA — A challenge (image, checkbox, invisible score) that blocks bots. e.g. reCAPTCHA, hCaptcha, Cloudflare Turnstile.
- Honeypot — A hidden form field bots fill in but humans don’t; a silent spam filter.
- Rate limiting — Capping how often someone can submit, to stop floods.
- Server-side validation — Checking form input on the server, not just the browser, so it can’t be bypassed.
- Personal information / PII — Data that identifies a person: name, email, phone, message content. Your contact form collects this.
Legal & standards (Australia)
- Privacy Act 1988 — Australia’s main privacy law.
- APP (Australian Privacy Principle) — The 13 rules under the Privacy Act for handling personal information.
- Small business exemption — Businesses with turnover ≤ AUD $3M are generally exempt from the Privacy Act (with exceptions).
- APP 8 / cross-border disclosure — Rules on sending personal information overseas.
- NDB scheme (Notifiable Data Breaches) — Requires reporting eligible data breaches. Follows the Privacy Act, so likely out of scope if exempt.
- Collection notice — A short statement telling people why you’re collecting their info.
- Spam Act 2003 — Rules for commercial email: consent + unsubscribe.
- DDA (Disability Discrimination Act 1992) — Requires equal access, including websites.
- WCAG (Web Content Accessibility Guidelines) — The accessibility standard; 2.1/2.2 AA is the usual target.
- ACL (Australian Consumer Law) — Requires claims and pricing to be truthful.
- Copyright Act 1968 — Governs use of images, fonts, music.
- ACMA — The communications/media regulator.
- ACSC / ASD — Australian Cyber Security Centre / Australian Signals Directorate; publish security guidance.
- Essential Eight — Eight prioritised cyber mitigations from the ASD.
- ReportCyber — ACSC’s portal for reporting cybercrime.
Site types (for later sections)
- UGC (User-Generated Content) — Content posted by users, e.g. blog comments. Creates moderation and legal liability.
- PCI DSS — Payment Card Industry Data Security Standard, triggered if you handle card data.
- DSAR (Data Subject Access Request) — A person asking for a copy of their data (GDPR terminology; AU equivalent is an APP access request).