How to test an email gateway against phishing attachments
Email gateways can stop obvious spam while still delivering a deceptive attachment to a busy inbox. Testing your email gateway against phishing with attachment-based payloads shows whether inspection, sandboxing, link rewriting, impersonation rules and quarantine work as intended without exposing real staff or customers.
For Australian teams, the exercise should reflect real environments. Organisations in Sydney, Melbourne and Brisbane commonly combine hybrid work with Microsoft 365 or Google Workspace, while .com.au, .gov.au and healthcare domains carry different trust requirements. Plausible lures can reference Australia Post, tax obligations, energy bills or toll notices.
The safest approach uses written authorisation, synthetic recipients, harmless marker files and team-controlled links. It measures gateway decisions and user handling without creating live malware, capturing credentials or sending damaging attachments. Results should guide detection tuning, awareness training and incident-response playbooks.
Define scope and safety controls
Obtain written authorisation before sending anything. Define allowed tenants, recipients, attachment types, sending domains, test windows and stop conditions. Exclude live customers, shared mailboxes and executive accounts unless specifically approved. Assign a coordinator and security observer so gateway, endpoint and SIEM events can be correlated.
Document test-data handling. Keep synthetic information minimal, follow the Australian Privacy Principles under the Privacy Act 1988 and apply existing access, retention and legal-hold rules. OAIC guidance is particularly relevant to healthcare providers and financial institutions, while government agencies should follow approved security processes.
Build safe attachment test cases
Build a small set of harmless samples: an Office document containing only a canary token, a PDF with benign metadata and an approved test link, an HTML attachment, a password-protected archive containing text, and an archive with a double extension. The canary provides evidence of processing when a file is rewritten or inspected in the test environment, without introducing executable code or live malware.
Vary display names and subjects to test impersonation, but keep every sender and destination under your control. Use Australian English, A$ amounts, day-month dates and familiar themes such as parcel redelivery, invoices or utility bills. Local realism can reveal rules that depend too heavily on overseas sender patterns.
Map delivery routes and supporting controls
Test each delivery route separately: external-to-external, external-to-internal, internal-to-internal, mobile app, webmail, relay and API paths. For Microsoft 365 and Google Workspace, document whether Safe Links, attachment handling, quarantine and alert policies act before or after your gateway. Forwarding rules can otherwise hide the primary result.
Treat authentication separately. A valid SPF record, aligned DKIM and a passing DMARC result confirm origin controls; they do not make an attachment safe. Record authentication, policy alignment and the final gateway action so legitimate-looking mail is not mistaken for secure mail.
Mail testing complements checks around the user’s connection. If staff join branch Wi-Fi or home networks, a wireless network audit can identify unmanaged access points or unsafe local DNS settings that weaken the environment around a mail client.
Run the test and record outcomes
Begin with one sample, confirm the route, then expand in small batches. Schedule runs around Sydney, Melbourne and Perth business hours. Record each mailbox’s tenant, client and network, because a message blocked at the gateway may still reach users through forwarding.
Before sending, confirm:
- Written approval identifies tenants, recipients, attachment classes, sending domains, dates and stop conditions.
- Synthetic senders use display names and domains controlled by your organisation.
- Marker attachments contain no executable code, macros, scripts or live malware.
- Tracking destinations lead only to an approved page and never collect passwords.
- Gateway, endpoint and SIEM logging remains active throughout the test window.
After each run, record:
- The gateway verdict, timestamp, matched policy, action and message-release status.
- Whether sandboxing or content disarm and reconstruction processed the attachment.
- Elapsed time from submission to block, quarantine, alert and analyst review.
- User report, click and attachment-open data, with no credentials captured.
- Exceptions, including false positives, bypasses and endpoint-only prevention.
Tune controls and validate resilience
Treat a blocked message as a successful control only when quarantine, alerting and safe release also work. A generic attachment block is weaker than sandbox-based detection if staff can inspect the message and release it correctly. Measure processing time, alert quality, false positives and the proportion reaching junk folders.
Prioritise remediation using the ASD Essential Eight and the risk profile of the sector. Common improvements include stricter attachment policies for finance, government, healthcare and e-commerce teams, attachment detonation, look-alike domain checks, and alerts routed to a 24/7 managed detection process. Retest each change with the same samples.
Keep scenarios appropriate for the Australian market without creating legal or reputational harm. Delivery messages can mention Australia Post, bills can use A$ and local dates, and government or health themes should point only to controlled domains. Avoid real logos and personal data unless the brand owner has approved their use.
Start with a controlled gateway assessment
Infoziant Security helps Australian organisations design safe, repeatable exercises around their mail flow and risk profile. The assessment can combine vulnerability testing, cloud and mobile reviews, SIEM monitoring and threat intelligence, then translate the findings into practical gateway, endpoint and awareness improvements.
Request a trial-based email gateway assessment or ask for a free VAPT report. The agreed scope will define safe payloads, success criteria and reporting, showing what was blocked, what reached inboxes and which controls need adjustment before the next authorised exercise.