Penetration Testing Services
Manual penetration testing of applications, APIs, networks and cloud, with three-level review (L1 → L2 → L3) of every finding. Delivered from Mumbai, London, New York and Singapore.
What a penetration test is
A penetration test is an authorised attack on your own systems. Testers work to an agreed scope, find the weaknesses an adversary would use, exploit them to show the impact and report how to fix each one. Buyers commission it before a release, for a customer or auditor, and on the annual cycle that PCI DSS, ISO 27001 and SOC 2 programmes run to.
Seven assessments, one engagement process
Each has its own methodology and its own page. Most engagements combine two or three of them.
Web Application Penetration Testing
Business logic, authentication, authorisation and session handling across every user role, against the OWASP Top 10 and ASVS.
Before a release, a customer security review or a certification audit.
Scope and methodology →API Security Testing
REST, GraphQL and WebSocket endpoints tested for broken object and function level authorisation, against the OWASP API Top 10.
When partners, mobile apps or third parties consume your APIs.
Scope and methodology →Mobile Application Security Testing
iOS and Android binaries, local storage, transport security and the back-end APIs the app calls.
Before an app store release or a major version.
Scope and methodology →Network Penetration Testing
External perimeter and internal network: exposed services, segmentation, Active Directory and lateral movement paths.
Annually, after infrastructure change, and for PCI DSS segmentation evidence.
Scope and methodology →Cloud Security Assessment
AWS, Azure and GCP configuration, identity permissions and the exposure those permissions create.
After a migration, a new account structure or a change in who administers the estate.
Scope and methodology →Red Team Assessment
An objective-led adversary simulation across people, process and technology, mapped to MITRE ATT&CK.
When the question is whether your detection and response would catch a real intrusion.
Scope and methodology →Secure Code Review
Source code read for injection, authorisation and cryptographic flaws that black-box testing reaches slowly.
For high-value applications, and alongside a penetration test of the same system.
Scope and methodology →Which test fits your situation
The scoping call settles this in detail. These are five common starting points.
A customer, auditor or investor has asked for a penetration test report
Web application or API testing of the product they buy, with an executive report written to be shared.
You handle card data
External and internal network testing with segmentation checks, plus the applications in the cardholder data flow.
You have moved to the cloud since the last test
A cloud security assessment of configuration and identity permissions before the next application test.
You want to know whether your team would detect an intrusion
A red team assessment with an agreed objective, measured against your detection and response.
One application carries most of your risk
A secure code review alongside the penetration test, so that findings are traced to the line that causes them.
Three in-house platforms behind every test
Quality that depends on which tester you were assigned is luck. We built the platforms that make it structural.
L1 · L2 · L3
Lemon
Our audit management platform. It structures each engagement, tracks coverage and carries every finding through three levels of review.
About LemonAutonomous testing
B-52
Our agentic penetration testing platform. It adds autonomous testing to an engagement, with exploit evidence for what it confirms.
About B-52External attack surface
ShadowMap
Our attack surface platform. It maps the domains, services and exposures an attacker sees first, which informs the scope of external and red team testing.
About ShadowMapReports written for the audit they go into
A penetration test is usually evidence for something. Tell us which framework the report serves and it is scoped and written for that reader.
PCI DSS v4.0.1
Requirement 11.4
ISO 27001
Annex A 8.8 and 8.29
SOC 2
Trust Services Criteria
HIPAA
Security Rule evaluation
GDPR
Article 32
MAS TRM
Singapore financial institutions
NIST CSF
Version 2.0
IEC 62443
Industrial control systems
Buying in India? The same work is commissioned as VAPT, with reporting for RBI, SEBI and CERT-In. See VAPT services in India, RBI and SEBI CSCRF.
Penetration testing by country
Penetration testing services, answered
Something else? Read the case studies or ask the team.
Request a scoping callWhat are penetration testing services?
What is the difference between a vulnerability assessment and a penetration test?
How often should penetration testing be carried out?
What do you deliver at the end of a penetration test?
Who carries out the testing?
Which countries do you work in?
Scope your penetration test
Tell us what is in scope and who will read the report. We reply within one business day.