Keep your school website safe by controlling who can make changes, acting on security updates and testing that you can get the site back. In the age of AI, add one more habit: verify unusual requests through a channel you already trust, even if the message sounds like someone you know.
1. Know who has the keys
List the school’s domain registrar, hosting account, website editor and form tools. Record the school owner and supplier contact for each. The person who updates the news page does not need the power to move the domain.
Use named accounts instead of a shared admin login. Turn on multi-factor authentication (MFA), which asks for a second proof of identity at sign-in. Remove access when staff or suppliers leave. Our guide to giving an agency account access can help you delegate without handing over ownership.
2. Verify unusual requests before acting
An email that sounds like your principal is not proof it came from them. AI can help make fake messages sound natural, so spelling mistakes are not a reliable warning sign. Treat an urgent request to reset an account, change where enquiries go or share an MFA code as a reason to pause.
Call the person on a number you already have, or start a fresh chat through your school’s usual staff channel. Do not use the phone number or link in the request. Never share a sign-in code or approve a prompt you did not start. If you already acted, tell IT straight away using your school’s reporting process.
3. Follow one enquiry from start to finish
Use a test enquiry with made-up details. Ask who can read it and where copies land: in the form tool, a shared inbox or an enrolment system. An open-day form is a place to ask for contact details, not a place to collect health information. If you need sensitive information later, use the school’s approved process.
Ask your privacy or records lead which copies must be kept, for how long and who approves disposal. Do not delete records needed for a legal duty, a retention rule or a hold. Keep student information in an approved private system, not on an unlinked public page.
4. Know who handles urgent updates
ASD’s Australian Cyber Security Centre recommends securing website logins, keeping the content system and plugins up to date, and backing up the site. Ask who patches each tool you use and who gets alerts. A managed host may cover the hosting platform, but check the terms before assuming it also covers your plugins, forms or domain.
Ask your provider to confirm that your CMS, plugins, themes and server software are supported and receiving security updates, and agree who handles urgent patches. Ask when you’ll get confirmation that the work is done, and check key pages and forms afterwards.
If you use Webflow, see our guide to its hosting and security features. Whatever you use, check that the site and form load over HTTPS without browser warnings.
5. Test a restore before you need one
Ask what a backup includes. A copy of the site might not include form entries or account settings. Have IT or your supplier restore a copy away from the live site, then check that key pages load and a test form still works. Write down how long it took and who could do it again.
“We have backups” and “we know how to restore the site” are two different answers.
6. Make a one-page response plan
- Name the person who calls IT or the host if the site changes unexpectedly or goes down.
- Agree who checks whether family data may be affected and who handles any notice.
- Keep a copy of these contacts somewhere you can reach without the website.
Start this week
- Confirm account owners. Name the school owner and supplier contact for the domain, hosting, website editor and form tools.
- Enable MFA. Start with the accounts that can change the website, domain or enquiry destinations.
- Check where enquiries go. Send a test with made-up details and confirm who can read it and where copies are stored.
- Request evidence of a successful restore. Ask IT or your supplier to show that a backup has been restored and checked away from the live site.
Run through these checks with marketing, admissions and IT before the next open day. If no one owns a step, fix that first. Talk to IGNITE if you need help mapping the public website, its forms and the handover to your IT team.