Penetration testing · Certified ethical hackers

Find the gaps before someone else does.

A penetration test is a controlled, authorised attempt to breach your systems, to find vulnerabilities before attackers do. Our certified team uses the same techniques real threat actors use, then gives you a clear remediation roadmap.

Book a Discovery Call What's included

ISO 27001 certified ISMS Fixed scope and fee before testing OWASP, PTES and CREST-aligned

What you receive at the end

Report & remediation roadmap

Executive summary a board can read in five minutes
Severity, evidence and remediation steps for each finding
A prioritised finding list your IT team can act on
A remediation roadmap with clear ownership

From scope to sign-off

Fixed scope
Tested
Debriefed
Re-tested

Your defences tested by people who think like attackers.

Our penetration testers are certified security professionals who approach every engagement with the mindset of a real adversary, looking for the same attack paths, the same misconfigurations, and the same human-layer weaknesses that actual threat actors target.

They have assessed environments across South Australian government, finance and healthcare, where a missed finding carries real consequences.

Back to Information Security →

Every attack surface tested. Every finding clearly explained.

We scope each engagement to match your environment and risk profile. Whether you need a quick external network test or a full red team exercise, we design the test to answer the questions that matter most for your business.

Network

External network: what's visible and exploitable from the internet
Internal network: what an attacker could reach from inside your environment
Lateral movement: post-exploitation and network traversal testing
Wireless security: network assessment and access point review

Applications & cloud

Web application: OWASP Top 10 and beyond for custom or SaaS applications
Cloud configuration: Microsoft 365 and cloud security review

People & premises

Phishing simulation: testing your people, not just your systems
Physical security: access controls, tailgating and USB drops (on request)

Retest

Retesting: verified remediation, with a Certificate of Completion issued on request

Testing finds the gaps. GRC and compliance work closes them systematically. Pair both for a security programme that's verified, not just documented.

Methodology

Industry-standard methodology. No shortcuts.

Our testing methodology is aligned to recognised industry frameworks, so findings are comparable, reproducible, and defensible in any audit or compliance context.

100% Australian-based. Our penetration testing team operates under Australian law, with full Australian privacy compliance.

01
OWASP Testing GuideThe gold standard for web application security testing. We test against the OWASP Top 10 and the full OWASP Testing Guide for custom applications and APIs.
02
Penetration Testing Execution Standard (PTES)PTES defines the phases of a penetration test: pre-engagement, intelligence gathering, threat modelling, exploitation, post-exploitation and reporting. We follow it for all infrastructure engagements.
03
CREST-aligned practicesOur processes are aligned to CREST standards for professional, ethical and technically rigorous penetration testing, the same framework used by Australian government agencies.

Why Australian businesses run penetration tests.

A penetration test isn't just a compliance exercise. Here's what actually drives businesses to engage.

Client requirements

Enterprise and government clients increasingly require evidence of penetration testing before awarding contracts or renewing agreements. A test report is the answer to that question.

Cyber insurance

Insurers are tightening requirements. Many policies now require annual penetration testing as a condition of coverage or carry premium discounts for businesses that demonstrate tested controls.

Compliance frameworks

ISO 27001, Essential Eight at higher maturity levels, DISP and PCI DSS all have penetration testing requirements. We scope and document tests to satisfy each framework's specific evidence requirements.

After a major change

New cloud migration, system rebuild, acquisition, or significant infrastructure change? Testing after major changes validates that your new environment is secure before attackers find what your team missed.

Five phases, scoped before we start.

These follow the Penetration Testing Execution Standard, the methodology our testing is aligned to, rather than a sequence we invented for a diagram.

01 · Pre-engagement
Scoping
Targets, rules of engagement, testing windows and escalation paths agreed in writing, with a fixed scope and fee before any testing begins.
02 · Intelligence
Gathering
Mapping the attack surface as an attacker would: exposed services, technologies in use, and what your organisation leaks publicly.
03 · Modelling
Threat analysis
Working out which paths a real attacker would actually take against your environment, rather than testing everything equally.
04 · Exploitation
Testing
Proving what is genuinely exploitable and how far it reaches, so findings come with evidence rather than a scanner's opinion.
05 · Report & re-test
Remediation
A prioritised report, a debrief with your team, and a re-test once you have fixed things, so you can show the issues are actually closed.

Plain-language reporting

A report only your security team can understand isn't useful.

Every report we write includes an executive summary a board can read in five minutes, a prioritised finding list your IT team can act on immediately, and a remediation roadmap with clear ownership.

Post-remediation retesting is included on request. When vulnerabilities are resolved and verified, you receive a formal Certificate of Completion, shareable with clients, insurers and auditors.

How to read the report you get at the end

What you receive

Executive summary, board-ready
Technical findings
Severity rating per finding
Evidence and remediation steps
Risk-prioritised roadmap
Debrief session
Retest on request
Certificate of Completion

What people ask before a test.

Something else? Call 1300 080 000 and you'll get a straight answer.

How is a penetration test different from a vulnerability scan?

A vulnerability scan is automated. It runs a tool against your systems and produces a list of known weaknesses. A penetration test is performed by a human analyst who attempts to exploit those weaknesses, chain them together, pivot through your environment, and achieve a defined objective: like accessing sensitive data or compromising a domain controller. Scans tell you what might be vulnerable. Pen tests tell you what actually is, and how bad it could get.

How often should we run a penetration test?

Annual testing is the baseline for most businesses. You should also test after significant infrastructure changes, after a major application release, after an acquisition, or if your compliance framework requires it. ISO 27001, Essential Eight at higher maturity levels, and DISP all have testing requirements. We can align the test scope and frequency to your compliance obligations.

Will a penetration test disrupt our systems?

A professional test is scoped so it doesn't. Before any testing begins we agree written rules of engagement: what is in scope, what is explicitly out of scope, the testing window, and the conditions under which we stop and call you. Destructive techniques such as denial-of-service are excluded unless you specifically authorise them. You get a named contact for the duration of the engagement, so if anything looks unexpected on your side you can reach the tester immediately.

How much does a penetration test cost?

Scope drives the price. The main factors are the number of systems, applications and IP ranges in scope, the depth and type of testing (a focused external network test costs less than a combined web application, network and phishing engagement), and whether findings are retested after remediation. Be wary of a quote that looks unusually cheap, it is often an automated scan presented as a penetration test. We scope the engagement on a discovery call and quote against that agreed scope, so you know what you are paying for before testing starts. Our guide to what a penetration test actually finds walks through the cost drivers in more detail.

What does the deliverable look like?

You receive a written report with an executive summary (plain language, board-ready), a technical findings section (each vulnerability with severity rating, evidence, and remediation steps), and a risk-prioritised remediation roadmap. We walk you through the report in a debrief session, so your technical team understands exactly what needs fixing and in what order. Where post-remediation retesting is included, you also receive a Certificate of Completion, a formal document confirming that identified vulnerabilities have been resolved, suitable for sharing with clients, insurers and auditors.