Apps in Your Users' Hands, Tested Like an Attacker Would.
Once your app is installed, attackers can take it apart. We test iOS, Android and desktop apps and the APIs behind them for the weaknesses that matter.
- iOS
- Android
- Desktop
- Backing APIs
How we test
- Manual testing, 20% automated
- 80%Manual testing, 20% automated
- Typical engagement, end to end
- 3 to 6 wkTypical engagement, end to end
- Platforms: iOS, Android, desktop
- 3Platforms: iOS, Android, desktop
- Included after you fix
- RetestIncluded after you fix
Overview
The Client Can't Be Trusted
Mobile and desktop apps run on devices you don't control. Secrets stored in the app, weak local storage or tamperable update paths can all be abused.
We test the app itself and the APIs it calls, so you see the full picture from the device to your backend.
What we test
From the Device to the Backend
Local Data Storage
Sensitive data, tokens and secrets stored on the device.
App Hardening
Reverse engineering, tampering and runtime protections.
Licensing Controls
Bypasses for licensing and feature restrictions.
Update Paths
Whether updates can be intercepted or replaced.
Network Traffic
Transport security and certificate handling.
Backing APIs
The APIs the app relies on, tested for authorization flaws.
Testing approaches
Black, Gray or White Box Testing
How much we know going in shapes what the test can find. We help you pick the right approach during scoping.
Black-Box Testing
No prior knowledge of the target, simulating an outside attacker.
- External attacker perspective
- Zero knowledge going in
- Real world attack scenarios
Gray-Box Testing
Partial knowledge, such as user accounts or documentation, simulating an insider or a compromised account.
- Authenticated testing as each role
- Insider and compromised account scenarios
- Best balance of depth and realism
White-Box Testing
Full knowledge, including source code and architecture, for the most thorough analysis.
- Source code and configuration access
- Architecture review
- Deepest coverage
For desktop and mobile apps we usually recommend gray-box: app builds plus test accounts, so we cover both the app and its APIs.
How we test
Our Methodology
Every engagement follows the same disciplined path, typically three to six weeks end to end.
- 1Week 1
Scope & Recon
Agree scope and map the attack surface.
- Rules of engagement
- Passive and active recon
- 2Weeks 2 to 4
Scan & Identify
Find live services and weaknesses.
- Misconfigurations
- Vulnerability identification
- 3Weeks 2 to 4
Exploit
Prove real impact, safely.
- Privilege escalation
- Lateral movement
- 4Weeks 5 to 6
Report & Retest
Clear findings, then verify your fixes.
- CVSS scored findings
- Retest included
Why Com-Sec
A Team That Does the Heavy Lifting
Expert Led
Mostly manual testing by experienced testers, finding what automated scanners miss.
Audit Ready Reports
Reports written for SOC 2, ISO 27001, HIPAA and customer reviews, with an attestation letter.
Retesting Included
We verify your fixes and update the report so it closes cleanly.
FAQ
Frequently Asked Questions
Ready to Test Your Defenses?
Book a scoping call for your app. You'll get a fixed price quote within 48 hours.
Book a Call