Penetration testing & red team services in Australia. Think like an attacker.
WIT Solutions provides penetration testing across Australia for organisations that need to know, not guess, whether their security holds up.
We test web applications, networks, Active Directory, cloud and Microsoft 365 the way a real attacker would. Then we explain plainly what we found, what it means and how to fix it.
- Fixed-price quotes
- Independent, with nothing to resell
- Australia-wide, remote or on-site
- Aligned to OWASP and MITRE ATT&CK
What a penetration test actually answers
A penetration test is a controlled, authorised attack on your systems by a skilled tester. It replaces assumptions with evidence by answering three questions.
Can someone get in?
We look for the gaps an attacker would use first: exposed services, weak logins, vulnerable applications and cloud misconfigurations.
How far could they go?
We chain weaknesses together to show whether a single foothold leads to admin access, sensitive data or your finance systems.
What would it mean for the business?
Every finding is explained in business terms: what data, money or operations are at risk, and what to fix first.
What a test can find
A common internal finding, laid out the way it appears in our reports.
From one staff login to full control of the network in four steps
One staff login
What an attacker has after one phishing email
Request a service ticket
Any user can. One account had a 2017 password
Crack it offline
Away from the network, so nothing notices
Log in as that account
It had been added to Domain Admins years ago
Full control
Every password in the domain copied. No alerts fired
Fix first: long random passwords on service accounts (or managed service accounts), remove unneeded group rights, and alert on unusual ticket requests.
Why Australian organisations commission penetration testing
Most tests start with a specific need. These are the most common.
Validating the Essential Eight
The Essential Eight Maturity Model describes controls. Testing shows whether they hold up, such as whether application control can be bypassed.
ISO/IEC 27001:2022
The standard doesn't mandate a penetration test, but auditors look for evidence that technical vulnerabilities are managed and controls work. An independent test provides it.
PCI DSS v4 Requirement 11.4
Requires internal and external penetration testing at least every 12 months and after significant changes. If segmentation reduces your scope, it must be tested too.
APRA CPS 234
Requires regulated entities to test the effectiveness of their information security controls through a systematic testing program, run by skilled, functionally independent specialists.
Cyber insurance
Insurance questionnaires often ask whether you test regularly and fix what you find. A recent report lets you answer with evidence.
Customer and tender due diligence
Enterprise customers, councils and government buyers often ask suppliers for recent independent testing.
Protecting personal information
The Privacy Act requires reasonable steps to protect personal information. Regular, independent testing helps you show what those steps were.
After major changes
A new system, cloud migration, major release or change of IT provider can open new gaps. Test before an attacker finds them.
Need help with the compliance program itself? Our governance, risk and compliance services cover the Essential Eight, ISO/IEC 27001 and more. Our testing gives that work real evidence.
Penetration testing services for every part of your environment
From a single web application to a full red team operation. Each test is scoped to your risk, your systems and your budget.
Web application penetration testing
Hands-on testing of websites, portals and SaaS platforms, logged in and out. We find the logic flaws that automated scanners miss.
Best for: Customer portals, SaaS products, e-commerce and any app holding personal data.
Show what we testHide what we test
- Login, session handling and MFA
- Access control between users, roles and tenants
- Injection, XSS, SSRF and file upload flaws
- Business logic, such as payment and approval abuse
Internal network & Active Directory testing
We start inside your network, as an attacker would after phishing a laptop. Then we show how far that foothold goes.
Best for: Any organisation running Windows and Active Directory, including hybrid Entra ID.
Show what we testHide what we test
- Active Directory attack paths to Domain Admin
- Weak passwords, exposed credentials and Kerberos attacks
- Unpatched servers and legacy protocols
- Segmentation between corporate and sensitive zones
External network & perimeter testing
Testing everything you expose to the internet. We first map what's really out there, including systems you may have forgotten.
Best for: Every organisation. It's the first view an opportunistic attacker gets.
Show what we testHide what we test
- Firewalls, VPNs and remote access gateways
- Exposed services and admin panels
- Known vulnerabilities on edge devices
- Email, DNS and certificate configuration
Cloud, Microsoft 365 & Entra ID testing
Attack testing and configuration review across Azure, AWS and Microsoft 365. In the cloud, identity and configuration are often the weakest points.
Best for: Organisations on Microsoft 365, Azure or AWS, especially after a migration.
Show what we testHide what we test
- Entra ID roles, Conditional Access and MFA gaps
- Over-privileged accounts, service principals and keys
- Storage exposure and logging in Azure and AWS
- Paths from one compromised user to cloud admin
API security testing
Testing the REST and GraphQL APIs behind your web and mobile apps, and those you share with partners.
Best for: SaaS platforms, mobile back ends and partner integrations.
Show what we testHide what we test
- Broken object- and function-level authorisation
- Tokens, API keys and authentication
- Excessive data exposure and mass assignment
- Rate limiting and resource abuse
Mobile app penetration testing
Testing iOS and Android apps, the data they store on the device and the APIs they talk to.
Best for: Finance, health, retail and any app handling personal or payment data.
Show what we testHide what we test
- Insecure storage of data and tokens
- Transport security and certificate pinning
- Login and session handling
- Resistance to reverse engineering and tampering
Red team operations
A covert, goal-based simulation of a real adversary. It tests people, process and technology together, including whether your team notices.
Best for: Mature organisations that already test regularly and want to measure their defences.
Show what we testHide what we test
- Agreed objectives, such as reaching finance systems
- Phishing and social engineering, where in scope
- Stealthy movement designed to avoid detection
- Your detection and response, end to end
Assumed-breach simulation
We skip the phishing step and start as a normal staff member with a standard laptop and account. It answers: if one user is compromised, what happens next?
Best for: Red team realism on a smaller budget and timeframe.
Show what we testHide what we test
- What a standard user can reach and read
- Privilege escalation on endpoints
- Lateral movement towards sensitive data
- Whether endpoint protection and alerts trigger
Purple team exercises
We work side by side with your security team, SOC or MSP. We run real attack techniques mapped to MITRE ATT&CK and check what gets detected.
Best for: Improving detection, or independently checking what your MSP's monitoring catches.
Show what we testHide what we test
- Detection coverage for agreed techniques
- Alert quality and triage
- Logging gaps in EDR, SIEM and cloud
- Detection tuning, retested on the spot
Vulnerability assessment
A broad, tool-assisted sweep for known weaknesses, with results reviewed by a person. Faster than a penetration test, but it doesn't exploit or chain findings.
Best for: Regular hygiene checks between penetration tests, or a first baseline.
Show what we testHide what we test
- Missing patches and end-of-life software
- Insecure and default configurations
- Internal and external hosts at scale
- False positives removed before you see them
Secure code review
Manual review of your source code, guided by how the application really works. It finds flaws that are hard to reach from outside.
Best for: Development teams, high-risk features and pre-release reviews.
Show what we testHide what we test
- Authentication and authorisation logic
- Unsafe input handling and injection points
- Secrets and credentials in code
- Cryptography and dangerous functions
Building with AI? We also test LLM applications, chatbots and Microsoft 365 Copilot rollouts. See our AI security services.
Vulnerability assessment vs penetration test vs red team
These terms are often mixed up. They answer different questions, at different depths and costs.
| Vulnerability assessment | Penetration test | Red team | |
|---|---|---|---|
| Goal | Vulnerability assessment: Find known weaknesses across many systems | Penetration test: Prove which weaknesses can be exploited, and how far they lead | Red team: Test whether you detect and stop a real, goal-driven attack |
| Scope | Vulnerability assessment: Broad: many hosts or applications | Penetration test: Defined systems, agreed in advance | Red team: The whole organisation, within agreed objectives and rules |
| Depth | Vulnerability assessment: Wide but shallow, with no exploitation | Penetration test: Deep, manual exploitation and chaining | Red team: Deep and covert, focused on the objective |
| What it tests | Vulnerability assessment: Patching and configuration | Penetration test: Security controls in the systems in scope | Red team: People, process and technology, including detection and response |
| Who knows it's happening | Vulnerability assessment: Your IT team | Penetration test: Your IT team | Red team: Only a small group of decision-makers |
| Output | Vulnerability assessment: Prioritised list of verified vulnerabilities | Penetration test: Attack narrative, risk-rated findings and fixes | Red team: Attack timeline versus what was detected, plus an improvement plan |
| Best for | Vulnerability assessment: Regular hygiene and a first baseline | Penetration test: Compliance, new systems and annual assurance | Red team: Mature security programs testing their defences |
Not sure which you need? Most organisations start with a penetration test. On the scoping call we'll recommend the right fit, including when a smaller test is enough.
Independent, practitioner-led penetration testing
The person who scopes it does the testing
No hand-off to junior staff. The practitioner on your scoping call does the hands-on work and writes your report.
Independent, with nothing to sell
We don't resell products or licences, and we're not an MSP. So we can test your MSP's work with no conflict of interest.
Manual testing, proven findings
Scanners are a starting point, not the deliverable. Every finding in your report has been confirmed by hand.
Advice tested by a real attacker
Our defensive and compliance advice comes from offensive work. It's validated against real attack techniques, not just paper compliance.
We work with Australian businesses of 20 to 500 staff, local councils, healthcare, legal and finance organisations, government suppliers and enterprises. Based in Perth, we test Australia-wide, remotely and on-site.
Findings lead straight into practical next steps through our defensive security and compliance services.
Our certifications, and what they prove
Most of these are earned by passing practical exams: breaking into real systems against the clock, not answering multiple-choice questions. Here's what each one means for you.
OSCP
OSWE
OSEP
OSED
OSCE3
OSDA
CRTO
CRTL
OSCPOffSec Certified Professional
Proves the ability to compromise a range of networked systems in a timed, hands-on exam. A widely recognised baseline for penetration testers.
OSWEOffSec Web Expert
Advanced web application security. Proves the ability to analyse source code, find complex flaws and write working exploits for them.
OSEPOffSec Experienced Penetration Tester
Attacking hardened environments: bypassing defences, abusing Active Directory and moving through well-defended networks.
OSEDOffSec Exploit Developer
Reverse engineering and writing custom exploits, so testing isn't limited to what public tools can do.
OSCE3OffSec Certified Expert 3
Awarded only to holders of OSWE, OSEP and OSED. It shows expert-level skill across web, network and exploit development.
OSDAOffSec Defense Analyst
A defensive certification in detecting attacks through logs and SIEM data. We know what your defenders see, which makes purple teaming more useful.
CRTOCertified Red Team Operator
Running a realistic, multi-stage attack with command-and-control (C2) tooling against Active Directory environments.
CRTLCertified Red Team Lead
Advanced red team tradecraft: evading endpoint detection (EDR) and operating quietly in mature, well-monitored environments.
Our penetration testing process
Six clear steps, from the first call to a confirmed fix.
Scoping & rules of engagement
A free call to understand your goals, systems and constraints. We agree scope, timing, contacts and rules in writing, then send a fixed-price quote.
Reconnaissance
We map your attack surface as an attacker would: domains, exposed services, technologies and public information. This can surface assets you didn't know were exposed.
Testing & exploitation
Manual, hands-on testing supported by tools. We chain weaknesses to show real impact and stay within agreed limits. If we find something critical, we tell you straight away.
Validation
Every finding is confirmed by hand. No false positives and no raw scanner output: if it's in the report, we've proven it.
Reporting
A clear report for two audiences: a summary for leadership and the board, and full technical detail for the people fixing it.
Debrief & retesting
We walk you through the results and answer questions. Once fixes are in place, retesting of remediated findings is available to confirm they work.
Standards we align to
Our methodology follows recognised public standards, so results are consistent and easy for auditors to rely on.
- OWASP WSTG: Web application testing
- OWASP ASVS: Application security requirements
- OWASP MASVS & MASTG: Mobile app testing
- OWASP API Security Top 10: API risks
- PTES: Engagement structure
- NIST SP 800-115: Technical security testing
- MITRE ATT&CK: Real attacker techniques for red and purple teaming
What's in your penetration test report
One report, written for two audiences: the people who make decisions and the people who fix things. It's written by the tester who did the work.
Executive summary
A plain-English summary for the board, CEO or CFO: overall risk, key issues and what to do first.
Attack narrative
How we got in and how far we went, step by step. It shows how small issues combine into a serious breach.
Findings rated with CVSS and business context
A technical score alone can mislead. A medium-rated issue on your payment system may matter more than a high on a test server.
Reproduction steps
Evidence and step-by-step instructions, so your team or vendor can reproduce and verify each issue.
Prioritised remediation
Practical fixes in order of risk reduction, including quick wins and longer-term changes.
Retest confirmation
When you retest with us, an updated report confirms which findings are closed: clean evidence for auditors, insurers and customers.
How we protect your production systems
Testing should find problems, not cause them. Every engagement runs under written rules of engagement.
Written rules of engagement
Scope, off-limits systems, techniques and limits are agreed and signed off before testing starts.
Agreed testing windows
We test when it suits you. After-hours testing can be arranged for sensitive or busy systems.
Nothing destructive without approval
No denial-of-service, data changes or risky exploits unless you explicitly approve them.
Emergency stop contacts
Named contacts on both sides. If anything looks wrong, testing pauses immediately.
Careful data handling
We access only what's needed to prove impact, avoid copying bulk data, and keep evidence secure.
Test accounts
Dedicated test accounts and test data where possible, so real customers and records aren't touched.
Penetration testing FAQs
How much does a penetration test cost in Australia?
It depends on scope. The main drivers are the number and size of systems (applications, user roles, IP addresses or API endpoints), their complexity, the type of test, on-site work and any after-hours testing. After a free scoping call, we give you a fixed-price quote.
How long does a penetration test take?
A single web application or a small external perimeter often needs a few days of testing. Larger internal networks or multi-application scopes take longer. Red team operations usually run over several weeks. We agree the timeline and report date before testing starts.
How often should we do a penetration test?
At least once a year, and after any significant change: a new system, major release, cloud migration or change of IT provider. PCI DSS sets the same baseline. Customer-facing apps that change often may need testing with each major release.
What's the difference between a vulnerability scan and a penetration test?
A vulnerability scan is automated. It lists known weaknesses, including false positives, but can't show which are exploitable or how they combine. A penetration test is a skilled person trying to break in and proving real impact. It shows whether an attacker could actually succeed.
What is red teaming, and do we need it?
Red teaming is a covert, goal-based simulation of a real attack. It tests whether your people, processes and technology detect and respond. It suits organisations that already test regularly and have security monitoring. If you're not there yet, a penetration test or assumed-breach test is usually better value.
What is an assumed-breach test?
It starts as a compromised staff member, with a standard laptop and user account on your network. Skipping the phishing step saves time and budget. It shows how far an attacker could get from one user, and whether anyone would notice.
Will penetration testing disrupt our systems?
It's designed not to. We work under written rules of engagement and agreed testing windows, with emergency contacts on both sides. Nothing destructive happens without your approval. For fragile systems, we can test after hours or against a non-production copy.
Do you retest after we fix the issues?
Yes, retesting of remediated findings is available. We re-check each fixed issue and update the report to show what's closed. We can include retesting in your quote.
What do we need to prepare for a penetration test?
Not much. Usually a confirmed scope, a technical contact, test accounts for each user role, and any VPN access or IP allow-listing needed. If an MSP or hosting provider manages the systems, let them know. We confirm everything we need during scoping.
Can penetration testing be done remotely?
Yes. External, web application, API, cloud and Microsoft 365 testing is done remotely. Internal network testing can be done remotely through secure access agreed with your IT team, or on-site. We deliver testing anywhere in Australia.
Find out what an attacker would find first
Book a free scoping call. We'll talk through your systems and goals, recommend the right test and send a fixed-price quote.






