Six checks for business email security
Review business email sign-in, domain authentication, updates, request verification, sensitive-file handling and recovery with IT and staff.

Business email security depends on account controls, configuration and how staff handle requests. A secure sign-in doesn’t stop a colleague from sending information to the wrong recipient, and an authentic-looking message can still be fraudulent.
Use these six checks with IT to find out what’s set up and what staff should do. The Cyber Centre’s email guidance covers both technical settings and workplace practices.
1. Verify sign-in and recovery
Use unique passwords where passwords are required, and deploy supported MFA. Prefer phishing-resistant methods where the service and devices support them. Confirm enforcement for ordinary and administrator accounts.
Test recovery when the normal phone or email isn’t available. Protect recovery material and remove obsolete methods. MFA blocks some attacks, but an account can still be compromised in other ways.
2. Check sending-domain authentication
Have IT review SPF, DKIM and DMARC alongside every service that legitimately sends mail for your domain. Test intended senders before enforcing a restrictive policy.
The Cyber Centre’s technical email guidance explains these controls. They help with domain impersonation. They can’t tell you whether the request in a message is genuine, or whether a similarly named domain belongs to the sender you expect.
Assign someone to review sending changes and available reports. Don’t leave an old marketing or application sender undocumented.
3. Verify updates and attachment protection
Check that supported email clients, browsers and operating systems receive updates and that endpoint protection is functioning. Updates can be switched on and still fail, so check that the last one installed.
Handle attachments and software the way IT has set up. Don’t disable a warning or upload a confidential attachment to a public scanning service. Ask IT to examine an unexpected file.
4. Confirm consequential requests separately
For payment changes, credentials or sensitive records, verify the request through a trusted contact route. Use a phone number or workflow you already have. Don’t use contact details supplied in the message being checked.
A known account can be compromised. Familiar wording and a continuing email thread aren’t enough for a high-impact change. Record who confirmed the change and how.
5. Choose a protected route for sensitive material
Identify the information and recipient before selecting email, a sharing link from your business file service or another secure transfer method. Check who the link or folder lets in, and whether the recipient can use the route.
Transport encryption doesn’t necessarily protect every stored copy or provide end-to-end encryption. Confirm the selected service’s protection and limits. Recheck addresses and link access before sending.
6. Practise reporting and account response
Give staff a known channel for suspicious messages and unexpected account activity. Ask them to report what happened, including any entered password, approved prompt or opened attachment.
For suspected compromise, have IT review sessions, recovery methods, forwarding rules, delegated access and connected applications as applicable. Changing the password alone may leave another access route.
Test the reporting process with a harmless sample. Record who investigates and escalates, including outside ordinary hours. Alerts still need a person to act on them.


