Services / Penetration testing

Penetration testing

Penetration testing examines a defined application, network or device the way an attacker would: consultants look for exploitable weaknesses within an agreed scope, pair manual testing with automated tools, and safely exploit what they find.

Each finding is reported with proof-of-concept evidence and remediation guidance the owning team can act on.

Choose a testing area

Focus the scope.

Web Application and Services

Uncover and eliminate critical vulnerabilities in your web applications before attackers do.

Explore assessment

Mobile Application Security

Identify and remediate vulnerabilities in your mobile applications to protect user data and prevent exploitation.

Explore assessment

Desktop Application Security

Identify and remediate vulnerabilities in your desktop applications to prevent exploitation and safeguard sensitive data.

Explore assessment

External Infrastructure

Assess your internet-facing assets to identify vulnerabilities before attackers exploit them.

Explore assessment

Internal Infrastructure

Identify and remediate vulnerabilities within your internal network to prevent data breaches and unauthorised lateral movement.

Explore assessment

Wireless Network Security

Identify and mitigate vulnerabilities in your wireless networks to prevent unauthorised access, data interception, and rogue attacks.

Explore assessment

Restricted Environment Breakout

Assess the resilience of virtual desktops, kiosks, and other locked-down environments against breakout attempts and privilege escalation.

Explore assessment

Hardware and IoT Security

Identify vulnerabilities in IoT devices and embedded systems to prevent exploitation and secure physical and digital assets.

Explore assessment

AI/LLM Penetration Testing

Test the security and resilience of AI models, large language models (LLMs), and AI-driven applications against adversarial attacks and exploitation techniques.

Explore assessment

Who penetration testing is for

A penetration test suits a specific, defined need: an agreed application, environment or change. It can support a release decision, investigate a defined concern, provide evidence ahead of an audit or compliance review, or set a starting point for further work.

If the main question is how an attacker could pursue an objective across systems, and how defenders would respond, adversary simulation fits better.

The red team vs penetration test guide sets out the difference.

Scope the test around a decision

Scoping starts with the decision the test needs to support: which system or change is in scope, what access testing needs, and who will own the findings.

Boundaries and outputs, including any retesting, are agreed at scoping.

The scoping questions for each test list what a consultant will ask, and why each answer matters.

A targeted test can be a complete engagement in its own right; where needs recur, a program provides continuity.

Common questions

How is a penetration test different from a vulnerability scan?

Automated scanning detects standard vulnerabilities. A penetration test adds manual testing to find what scanners miss, such as business logic errors, chained exploits and misconfigurations, and safely exploits each finding to demonstrate its impact.

Which standards does testing follow?

Each assessment follows the framework for its technology, including OWASP ASVS for web and desktop applications, OWASP MASVS for mobile, CIS Benchmarks and NIST 800-53 for external infrastructure, the OWASP IoT Top 10 for devices, and the OWASP Top 10 for LLM Applications and MITRE ATLAS for AI systems.

What do we receive at the end?

A vulnerability report covering severity and impact, proof-of-concept demonstrations, a prioritised remediation roadmap, an executive summary for leadership, and post-assessment consultation to help the team fix what was found.

How often should systems be retested?

Retesting is agreed at scoping. An annual program plans twelve months of testing a quarter at a time, with retesting each quarter.

Who carries out the testing?

SilentGrid's own consultants: 16 testing consultants across Sydney, Melbourne, Brisbane, Adelaide and Hobart, employed full time and background checked, with 26 distinct offensive security certifications across the team, including OSCP, OSWE and OSEE. Testing is never subcontracted.

Tell us which system or change needs testing.