Cyber incident response services in Australia. Defence, informed by attack.
WIT Solutions provides cyber incident response services across Australia. We help you contain an attack, find out what happened and recover. Then we harden Microsoft 365, Entra ID, endpoints and networks so the same attack doesn't work twice.
We're practitioner-led and independent. We don't resell products, we're not an MSP, and the person who scopes your work does the work.
- Practitioner-led, no hand-off
- Independent, not an MSP
- Aligned with NIST incident response guidance
- Australia-wide, remote and on-site
- Continuous Monitoring
- 24/7
- Average Response Time
- <15 min
- Threat Detection Rate
- 99.9%
Incident response and defensive security services
Help when something has gone wrong, and the work that stops it happening again.
Incident response
Hands-on help when something has gone wrong: find out what happened, stop it spreading and recover.
Best for: Ransomware, email compromise, account takeover or unexplained activity.
Show what's includedHide what's included
- Triage and scoping: what's affected, and is the attacker still in?
- Investigation of endpoints, Microsoft 365, Entra ID and cloud logs
- Containment and recovery alongside your IT team or MSP
- Clear reports for your board, insurer, lawyers and regulators
Incident response readiness
Preparation that makes decisions faster and calmer when it counts.
Best for: Boards, regulated entities, councils, and anyone without a tested plan.
Show what's includedHide what's included
- An incident response plan and playbooks written for your organisation
- Tabletop exercises for executives and technical teams
- An incident response retainer with terms agreed in advance
Threat hunting
A proactive search for attackers who are already inside your environment.
Best for: After a near miss, before a major change, or as a regular check.
Show what's includedHide what's included
- Hypothesis-driven hunts mapped to MITRE ATT&CK
- Uses data you already have: EDR, Microsoft 365, firewall and DNS logs
- Findings turned into new detection rules
Microsoft 365 & Entra ID security
A hands-on review of your tenant against how attackers actually break in.
Best for: Any Microsoft 365 organisation, especially after an email compromise.
Show what's includedHide what's included
- Conditional Access and phishing-resistant MFA
- Privileged roles, guest access and emergency access accounts
- Mailbox rules, forwarding, OAuth app consent and Defender settings
Detection engineering & SIEM tuning
Make your SIEM alert on what matters, and stop paying to store noise.
Best for: A SIEM with too many alerts, or too few useful ones.
Show what's includedHide what's included
- Microsoft Sentinel, Splunk and Elastic
- Log coverage and custom rules mapped to MITRE ATT&CK
- Rules tested by running the real technique, plus triage runbooks
Security architecture & network segmentation
Design that limits how far an attacker can move after their first foothold.
Best for: Flat networks, new sites, mergers and cloud migrations.
Show what's includedHide what's included
- Network segmentation and firewall rule reviews
- Admin tiering, and separating OT, IoT and guest networks
- Backup design that survives ransomware
System hardening
Secure configuration of Windows, Linux and Active Directory, based on ASD hardening guidance and CIS Benchmarks.
Best for: Essential Eight uplift, audit findings, or fixes after a penetration test.
Show what's includedHide what's included
- Workstation and server baselines through Group Policy or Intune
- Active Directory review: privileged groups, delegation, stale accounts
- Changes staged and tested so business systems keep working
External attack surface monitoring
Regular checks of what you expose to the internet, found the way attackers find it.
Best for: A growing or poorly documented internet footprint.
Show what's includedHide what's included
- Discovery of domains, subdomains and internet-facing services
- Exposed admin portals, remote access and forgotten test systems
- Findings reported on a schedule agreed with you
24/7 Managed SOC
Continuous monitoring of your IT infrastructure, networks, and applications with real-time threat detection.
What to do after a cyber attack: first steps
Act quickly, but don't destroy evidence. These steps protect your investigation, insurance claim and reporting obligations.
Don't wipe or switch off affected machines
Powering off or rebuilding destroys evidence, including what's in memory. Disconnect them instead.
Isolate affected devices from the network
Unplug the cable, turn off Wi-Fi, or use your EDR tool's isolate feature.
Preserve logs
Export firewall, VPN, server and Microsoft 365 audit logs before they roll over.
Reset credentials from a known-clean device
Start with admin accounts, then revoke active sessions so stolen tokens stop working.
Talk on a separate channel
If email may be compromised, coordinate by phone or another channel.
Don't pay or contact the attackers yet
Get advice first. Payments can raise legal issues, including sanctions, and may need reporting to ASD within 72 hours.
Record a timeline
Note what was noticed, when, by whom, and every action taken. Insurers and regulators will ask.
Call your cyber insurer, if you have one
Many policies have an incident hotline and rules about which providers you can use.
Consider your notification obligations
Privacy, critical infrastructure, ransomware payment and APRA rules may apply, some within 12 hours. See reporting obligations below.
Report it to ASD
Use ReportCyber at cyber.gov.au or call ASD's ACSC hotline on 1300 CYBER1 (1300 292 371).
Need hands-on help now?
Email info@witsolutions.com.au with what you're seeing, or use our contact form. If your email may be compromised, send from an account you know is safe.
Our incident response process
Our process is aligned with NIST incident response guidance (NIST SP 800-61). You'll know what's happening at each stage, and why.
Preparation
Plans, contacts, logging and backups ready before you need them. Readiness work and tabletop exercises pay off here.
Detection & analysis
Confirm what happened, how the attacker got in, what's affected, and whether they're still active.
Containment
Stop the spread without destroying evidence. Isolate devices, disable accounts and revoke sessions in the right order.
Eradication
Remove every foothold, such as malware, rogue accounts and mailbox rules. Then close the way in.
Recovery
Restore from clean backups, watch for signs of return, and bring systems back in stages.
Post-incident review
A plain-English report of what happened and what to fix. Lessons feed back into your plan, detections and hardening.
Australian cyber incident and data breach reporting obligations
Depending on your organisation and what happened, you may need to report within days or even hours. These are the main federal schemes.
| Obligation | Who it applies to | Trigger | Deadline | Report to |
|---|---|---|---|---|
| Privacy Act: Notifiable Data Breaches scheme | Who it applies toOrganisations covered by the Privacy Act 1988, including most businesses with annual turnover over $3 million, private health service providers of any size, and Australian Government agencies. | TriggerA data breach likely to result in serious harm to the people whose personal information is involved. | DeadlineIf you suspect a breach, assess it within 30 days. If it's an eligible data breach, notify affected individuals and the OAIC as soon as practicable. | Report toOffice of the Australian Information Commissioner (OAIC) |
| SOCI Act: mandatory cyber incident reporting | Who it applies toResponsible entities for critical infrastructure assets under the Security of Critical Infrastructure Act 2018. | TriggerA cyber security incident affecting the asset. | Deadline12 hours for a critical incident having a significant impact on the asset. 72 hours for an incident having a relevant impact. | Report toAustralian Signals Directorate (ASD) |
| Cyber Security Act 2024: ransomware payment reporting | Who it applies toBusinesses with annual turnover over $3 million, and responsible entities for critical infrastructure assets under the SOCI Act. | TriggerMaking a ransomware or cyber extortion payment, or one being made on your behalf. | DeadlineWithin 72 hours of making the payment. | Report toAustralian Signals Directorate (ASD) |
| APRA CPS 234: information security incidents | Who it applies toAPRA-regulated entities, such as banks, insurers and superannuation trustees. | TriggerAn information security incident that materially affected, or could have materially affected, the entity or its customers. | DeadlineAs soon as possible, and no later than 72 hours after becoming aware. | Report toAustralian Prudential Regulation Authority (APRA) |
General information only. This is not legal advice. Other obligations may apply, such as state privacy laws for councils and state agencies, contracts, and your insurance policy.
We help you gather the facts these decisions depend on, and work alongside your lawyers. To build them into an ongoing program, see our governance, risk and compliance services.
Threat hunting: finding attackers before the alerts do
Most security tools wait for an alert. Threat hunting assumes something has already slipped past them, and goes looking.
Each hunt tests a hypothesis about real attacker behaviour, mapped to the MITRE ATT&CK framework, against your logs and endpoint data.
Our hypotheses come from techniques we use in authorised penetration testing and red teaming. We know what that activity looks like in the logs.
You get a short report: what we looked for, what we found, new detection rules, and any logging gaps.
Waiting for alerts vs threat hunting
| Alert-driven monitoring | Threat hunting |
|---|---|
| Waits for a rule to fire | Starts with a question about attacker behaviour |
| Catches known, noisy patterns | Finds quiet activity that blends in with normal admin work |
| Only as good as the rules you have | Produces new rules, so the next attempt is caught |
Example hunt hypotheses
- A finance mailbox has an inbox rule hiding replies from a supplier.
- A remote access tool that IT didn't install is running on a server.
- A service account is signing in interactively, or from an unusual location.
- Users, not admins, have granted third-party apps access to their mail.
Microsoft 365 security review and Entra ID hardening
Microsoft 365 holds most organisations' email, files and identity, so it's a prime target. We check the controls below, then give you a prioritised list of fixes.
Conditional Access
Who can sign in, from where and on what device. We look for gaps and exclusions, and check emergency access accounts are protected and monitored.
Phishing-resistant MFA
Push and SMS codes can be bypassed by phishing kits that steal session tokens. FIDO2 keys, passkeys and Windows Hello for Business resist this.
Blocking legacy authentication
Older protocols can't do MFA, so they're a side door for password spraying. We confirm they're blocked, without breaking anything that still relies on them.
Privileged access and PIM
Fewer standing admins, separate admin accounts, and just-in-time elevation with Privileged Identity Management where your licensing supports it.
Mailbox rules and external forwarding
Attackers often add rules that hide replies or forward mail out. We review existing rules and block automatic external forwarding.
OAuth app consent
A malicious app can read mail without knowing the password. We restrict user consent, add admin approval and review existing grants.
Microsoft Defender configuration
Safe Links, Safe Attachments, anti-phishing and endpoint settings tuned for you, not left at defaults.
Audit log retention
Unified audit logging switched on and kept long enough to investigate. No logs means no evidence.
Why Microsoft Secure Score alone isn't enough
Secure Score is a useful checklist, but it measures settings against Microsoft's recommendations, not your risk.
Some items give partial points for controls that only cover some users. Others can be marked as handled by a third-party tool without Microsoft checking. And it won't show if an attacker has already left a forwarding rule or malicious app behind.
We review the tenant the way an attacker would, then use Secure Score to track progress.
Rolling out Microsoft 365 Copilot? It can surface any file a user can access, so permissions matter more. See our AI security services.
Defenders who also attack
Defensive work is stronger when it's tested by someone who knows how attackers think.
Detections tested by a real attacker
Our credentials span offensive security and defensive analysis. We can run the technique, see if your controls catch it, and fix the gap.
Independent advice
We don't resell products or licences, and we're not an MSP. So there's no conflict of interest when we review your MSP's work.
No hand-off to junior staff
The person who scopes your work does the technical work, from first call to final report.
Australia-wide, remote and on-site
We work with SMBs of 20 to 500 staff, local councils, healthcare, legal and finance organisations, government suppliers and enterprises.
Credentials held
Offensive, defensive and security management certifications, including OSDA for detection and analysis.
- OSCP
- OSWE
- OSED
- OSEP
- OSCE3
- OSDA
- CRTO
- CRTL
Incident response and defensive security FAQs
What should I do if we've had a cyber attack?
Don't wipe or switch off affected machines. Isolate them, preserve logs and reset passwords from a clean device. Don't pay the attackers before getting advice. Report it to ASD through ReportCyber at cyber.gov.au or 1300 CYBER1 (1300 292 371), then get incident response help.
What is an incident response retainer?
An agreement with an incident response provider, set up before you need it. Scope, rates and terms are agreed in advance, so work isn't held up by contracts in the middle of a crisis.
Do we need an incident response plan?
Yes, if you'd struggle to say who decides what, and who to call, during an attack. A plan sets out roles, contacts and notification steps. Standards such as ISO 27001 and APRA CPS 234 expect one.
What is a tabletop exercise?
A facilitated session where your team works through a realistic scenario, such as ransomware, without touching live systems. It tests your plan, decisions and communication, and shows gaps before a real attack does.
Do we have to report a data breach in Australia?
Often, yes. Under the Notifiable Data Breaches scheme, organisations covered by the Privacy Act must notify affected people and the OAIC about breaches likely to cause serious harm. Other rules cover critical infrastructure, APRA-regulated entities and ransom payments. Get legal advice for your situation.
What is threat hunting?
A proactive search for attackers who have got past your security tools. A hunter tests a hypothesis about attacker behaviour, mapped to MITRE ATT&CK, against your logs. Findings become new detection rules.
How do you secure Microsoft 365?
Start with identity: Conditional Access, phishing-resistant MFA, no legacy authentication and fewer standing admins. Then email: block external auto-forwarding, review mailbox rules and restrict app consent. Then configure Microsoft Defender and keep audit logs.
Do you replace our MSP?
No. We're not an MSP and don't resell products, so we work alongside your MSP or IT team. We can respond to incidents with them, review their work independently, or give them a prioritised list of fixes.
Should we call our cyber insurer first?
Contact your insurer early. Many policies have an incident hotline and conditions about which providers you can use. We can work alongside the insurer's appointed responders where your policy allows.
How much does incident response cost?
It depends on the type of incident, how many systems and users are affected, what logs exist, and whether on-site work is needed. Planned work gets a fixed-price quote after a free scoping call. For a live incident, we explain how it's charged before work starts.
Get help with a cyber incident, or get ready for one
Tell us what's going on. You'll speak with a practitioner, not a salesperson. Planned work gets a fixed-price quote after a free scoping call.






