Advisory & CISO Services

Penetration Testing Services: Pentests That Prove the Path an Attacker Would Take. Fixed Price, Report in 14 Days, Free Retest.

A pentest should tell you which record one token can reach, which tenant a trial account can read, and how far one phished workstation gets before anything stops it.

We test web applications, APIs, SaaS platforms, mobile apps, networks and cloud environments by hand, senior-led, with tools for breadth. Each scope is a fixed price agreed in writing after one scoping call, the report lands within 14 days of the start, the retest after you fix is free, and the person on the scoping call does the testing. Fixed price, report in 14 days, free retest.

  • Attack paths chained end to end, each with reproduction steps, business consequence and a fix
  • Findings mapped to the PCI DSS, SOC 2, ISO 27001, DORA or NIS2 clause your auditor will cite
  • Written rules of engagement: agreed windows, a named contact on each side, a stop condition
A dark steel door standing ajar at the end of a concrete corridor with light coming through the gap - Atlant Security penetration testing services

One door left ajar is all it takes. The pentest finds it and documents what sits behind it.

See a sample pentest report ↗
Cover of the illustrative penetration test report

SEE THE DELIVERABLE

See what a useful
penetration test report looks like.

Review a combined engagement covering web, REST and GraphQL APIs, gRPC, SaaS tenant isolation, Android and iOS, networks, cloud, identity and CI/CD. Includes technical evidence, remediation and retest criteria.

62 pages. 24 findings. 14 charts, diagrams and matrices.
Illustrative penetration test. The organisation, systems and findings are fictional.

Get the sample report

A free PDF. Enter your email and company name, and we’ll email you a download link.

Use a company email address. Free and disposable email services are not accepted.

We’ll email you a download link and an invitation to discuss your security assessment needs. Privacy policy.

DEFINE YOUR SCOPE

Turn your testing requirements into a clear RFP.

Build one request for your applications, APIs, networks, and cloud. Review the scope, download your document, and send a copy to your inbox and our team.

Only questions relevant to your scope. Estimates and “not sure” are welcome.

200+Security Assessments
14Countries
14Days to Report
FreeRetest After Remediation
Alexander Sverdlov, founder of Atlant Security
Alexander SverdlovFounder, Atlant SecurityCISSP, CEH, CHFI, Mandiant

Scopes and leads every pentest personally, runs the remediation workshop with your engineers and signs the attestation letter your auditor reads.

Connect on LinkedIn

01 / THE DETAIL

What Each Penetration Test Actually Tests

A scanner scopes by host. We scope by the question an attacker would ask of each layer of your estate, and each question is one of six pentests. Pick the scope that matches the question, or combine several into one proposal.

Web application pentest

One application, every role. Access control between users and tenants, session and password-reset flows, injection, business logic in checkout and approvals, file handling, and the path from a self-registered account to the admin console.

Scope and pricing

API pentest

REST, GraphQL and gRPC. Which records a low-privilege token can reach, object and function-level authorisation, token scope and lifetime, rate limits, SSRF through URL parameters, and the shadow versions nobody decommissioned.

Scope and pricing

SaaS platform pentest

Tenant isolation at every layer: IDs, storage paths, search indexes, exports and background jobs. Role escalation inside a tenant, SSO and SAML handling, integration tokens, admin impersonation and support tooling.

Scope and pricing

Mobile app pentest

iOS and Android. What a stolen phone gives away: local storage and keychain use, binary protections, runtime hooking, certificate pinning, session tokens on the device, deep links and WebViews, and the API behind the app.

Scope and pricing

Network pentest

External perimeter and internal network. Exposed services and remote access, lateral movement, Active Directory privileged paths such as Kerberoasting and ADCS misconfiguration, and segmentation between user, server and card-data networks.

Scope and pricing

Cloud pentest

AWS, Azure and GCP. IAM privilege-escalation paths, public storage, instance metadata, secrets in CI/CD pipelines, Kubernetes exposure, security groups, and the hybrid trust from on-premises Active Directory into the tenant.

Scope and pricing

Two variants sit alongside the six: the bank pentest, built around payment workflows, core-banking integrations and privileged access for banks and credit unions, and DORA TLPT, the threat-led, regulator-validated exercise for financial entities designated under Article 26, which runs alongside the annual pentest.

Each scope produces its own question for the test, and its own section in the report.

02 / THE DETAIL

The Attack Paths That Repeat Across the Estates We Test

One per scope, these are the findings that recur across the environments we assess. Most sit in who can reach what, on fully patched systems, which is why a scan of the same estate comes back clean.

Role checks enforced only in the browser

The admin menu is hidden from ordinary users and the endpoint behind it answers any session. One request with a copied URL turns a self-registered account into an operator.

Object IDs the API trusts

Swap your own invoice ID for the next integer and the API returns another customer’s record. Broken object level authorisation, API1 in the OWASP API Security Top 10, recurs across the APIs we test.

A tenant filter missing on one code path

The main query is scoped to the tenant. The export job, the search index or the webhook payload is scoped to nothing. A free-trial account reads another customer’s data through the gap.

Session tokens held in plain text on the phone

A long-lived token in app storage or a backup, with no binding to the device. Whoever holds the phone, or the backup, holds the account until the token expires months later.

A service account with its go-live password

Kerberoastable (MITRE ATT&CK T1558.003), cracked offline, and local admin on the servers that matter. One phished workstation to Domain Admin with every host fully patched.

A CI/CD key with far more than it needs

A deployment credential in a repository or a pipeline variable, attached to a role that reads every bucket and can assume the production role. One leak reaches the database.

The finding boards remember: four steps from one phished laptop to the cloud tenant, with no exploit against an unpatched system.

03 / THE DETAIL

What the Report Has to Prove, and to Whom

A pentest report has two readers. Your engineer wants the exact request, the exact host and a fix that survives the next release. Your auditor, examiner or enterprise customer wants to see that an independent party tested the scope, that you understood the risk and closed it.

Ours carries both. The method follows NIST SP 800-115, every finding is mapped to the clause it bears on, the executive summary states what a board needs in two minutes, and the retest and attestation letter close the loop for the audit file. The same report supports SOC 2, ISO 27001, PCI DSS, HIPAA, DORA and NIS2 programmes, and NIST SP 800-53 control CA-8.

Financial entities designated under DORA have a separate, heavier regime, DORA TLPT, which we also deliver. Card environments add PCI DSS Requirement 11.4.5 segmentation testing to the network scope.

What each regime expects, and what in the deliverable answers it.
Two security consultants and a client at a boardroom table with a printed penetration test report open between them

04 / THE DETAIL

Rules of Engagement for Live Production Systems

Before anything is touched, both sides sign rules a risk committee and a release manager can read.

  • What is never done. Denial-of-service techniques, destructive payloads and real transactions stay out of every engagement. Test records we create are removed before the report is issued.
  • Windows you set. Testing hours, blackout dates and release freezes are written into the rules. Anything touching a production database or an identity provider runs in a window you approve.
  • A named contact and a stop condition. One escalation contact on each side, reachable throughout, and a written condition under which testing halts immediately.
  • Evidence handling. Any personal or customer data encountered is redacted at capture, held encrypted for the engagement only, and destroyed on a documented date.
  • Platform boundary respected. Cloud scopes follow the AWS customer penetration testing policy, the Azure penetration testing rules of engagement and the Google Cloud acceptable use policy. Hosted vendor platforms are tested at the integration surface.

05 / THE DETAIL

How the Engagement Runs

Five steps. The price is fixed at the first one, and the report lands inside fourteen days of the third.

1

Scoping call

Which scopes, roles and environments, and which auditor or customer will read the report. A proposal within 24 hours with a fixed price and timeline in writing.

2

Rules of engagement

Test windows, escalation contacts on both sides, test accounts and data, the cloud-provider rules that apply, and a written stop condition.

3

Manual testing

Reconnaissance first: subdomains, technologies, roles and trust relationships. Then senior-led exploitation, chaining weaknesses end to end against the agreed scope. Tools for breadth, people for authorisation and logic.

4

Report and workshop

Findings register with reproduction steps and severity, executive summary with regulatory mapping, and a live remediation workshop with your engineers.

5

Retest and attestation

One free retest after you fix, then an attestation letter signed by a named qualified individual, addressed to your auditor, your customer or your board.

06 / PRICING

Penetration Testing Pricing

Each scope is a fixed price. Larger or combined scopes are priced in one proposal with volume pricing; you approve the total before anything starts.

ScopeWhat is coveredTestingPrice
External network perimeterInternet-facing IP ranges, DNS, mail, remote access5-7 days
APIUp to 50 endpoints, REST, GraphQL or gRPC5-7 days
Web application1 application, all roles7-10 days
Internal network and Active DirectoryInternal ranges plus privileged-path analysis7-10 days
Cloud infrastructureOne AWS, Azure or GCP environment7-10 days
SaaS multi-tenant platformMulti-tenant platform, all roles and tenant boundaries10-14 days
Mobile app, single platformiOS or Android, one applicationAgreed at scoping
Mobile app plus its APIiOS or Android plus the API behind it10-14 days
Mobile app, both platformsiOS and AndroidAgreed at scoping
Mobile app, both platforms plus APIiOS and Android plus the API behind themAgreed at scoping

Every scope includes the findings register, the executive summary with regulatory mapping, the remediation workshop, one free retest and the attestation letter. The full list across all services is on the pricing page, and a standalone Active Directory assessment is priced on the AD security assessment page.

For small projects and ad-hoc work outside our pre-agreed packages or retainers, our standard hourly rate is $460.

07 / THE DETAIL

Penetration Test or Vulnerability Scan

Two controls that get bought as if they were one. Auditors know the difference, and the report has to show you do too.

A scan finds known weaknesses by version. A pentest proves what an attacker can reach by chaining them, and documents the path.

Need the scan as well? The vulnerability assessment covers the NIST RA-5 scanning control and pairs with any scope above.

08 / THE DETAIL

Who Commissions a Penetration Test

SaaS and software companies answering an enterprise security questionnaire or a customer asking for a recent pentest
Organisations preparing for SOC 2, ISO 27001, PCI DSS or HIPAA whose auditor expects an independent test and a retest
Fintechs, payment companies and EU financial entities meeting PCI DSS 11.4 or DORA Article 25 testing obligations
Healthcare and life-sciences providers evidencing the HIPAA Security Rule evaluation for applications and networks
Government contractors assembling NIST SP 800-171 assessment evidence ahead of a CMMC Level 2 assessment
Acquirers and private equity firms who need a target’s real exposure before the deal closes

Across 200+ security assessments in 14 countries since 2013, the estates have ranged over fintech, healthcare, SaaS, government contractors, private equity portfolios, law firms, manufacturing with OT, and ecommerce.

09 / THE DETAIL

Find Out What One Token, One Key or One Workstation Can Reach

One scoping call. Bring your last pentest report, your auditor’s request, or nothing at all. You will leave with a scope written as questions, a fixed price in writing, and a date for the report.

Scope My Pentest

10 / THE DETAIL

Book the Scoping Call

Choose a time for your scoping call.

Or visit our contact page ↗

11 / FAQ

Penetration Testing FAQ

What is a penetration test?
A manual, senior-led attempt to reach the data or privilege an attacker would want, inside a scope agreed in writing. We start from a question, such as which records one API token can reach, and answer it by chaining weaknesses together until the agreed boundary stops us. The output is a register of proven attack paths, each with reproduction steps, business consequence and a fix, mapped to the clause your auditor will cite.
How is a penetration test different from a vulnerability scan?
A vulnerability scan matches software versions and configurations against a database of known weaknesses and reports each host on its own. A penetration test takes a credential, a token or a foothold and follows it across systems, testing authorisation and business logic a scanner has no way to evaluate. Regulators treat them as two controls: NIST SP 800-53 lists scanning under RA-5 and penetration testing under CA-8, and PCI DSS v4.0 Requirement 11.4 asks for both.
Which penetration test do we need?
Start from the question. A customer-facing application with several roles is a web application pentest; a product whose value sits in its endpoints is an API pentest; a multi-tenant product sold to enterprises is a SaaS pentest; an iOS or Android app is a mobile app pentest; an estate with Active Directory is a network pentest; an AWS, Azure or GCP account is a cloud pentest. Banks get the bank pentest, and EU financial entities designated for threat-led testing get TLPT under DORA Article 26. Two or three scopes go into one proposal with volume pricing.
How much does a penetration test cost?
Every scope is a fixed price agreed in writing: from $4,000 for an external perimeter or an API of up to 50 endpoints, from $5,000 for a web application, an internal network with Active Directory or a single-platform mobile app, from $6,000 for a cloud environment, a SaaS platform or a mobile app with its API, from $8,000 for both mobile platforms and from $12,000 for both with the API. Every price includes the report, the remediation workshop, one free retest and the attestation letter. Combined scopes are priced in one proposal with volume pricing, and you approve the total before anything starts.
How long does a penetration test take?
Testing runs five to fourteen days by scope: five to seven for an external perimeter or an API, seven to ten for a web application, an internal network or a cloud environment, ten to fourteen for a SaaS platform or a mobile app with its API. The report is delivered within fourteen days of the start, and the scoping call produces a proposal within 24 hours.
Do you test production systems, and can the test cause downtime?
Production is tested under written rules of engagement: denial-of-service techniques and destructive payloads stay out of every engagement, anything that touches a production database or an identity provider runs in a window you approve, test records we create are removed before the report is issued, and a named contact on each side can halt testing under a written stop condition. Cloud scopes follow the AWS customer penetration testing policy, the Azure penetration testing rules of engagement and the Google Cloud acceptable use policy, and hosted vendor platforms are tested at the integration surface.
How often should we run a penetration test?
PCI DSS v4.0 Requirement 11.4 sets the clearest cadence: internal and external penetration testing at least once every 12 months and after significant changes. SOC 2 auditors expect a report from inside the audit period, ISO/IEC 27001:2022 control A 8.8 expects technical vulnerabilities to be managed continuously, and DORA Article 25 expects testing that includes penetration testing. In practice: one pentest per scope per year, a fresh test after a major release or migration, and continuous scanning between tests.
What do we receive at the end, and is retesting included?
A findings register with reproduction steps, severity, business consequence and a specific fix for each finding, an executive summary that maps each finding to the regulatory clause it bears on, and a live remediation workshop with your engineers. After you fix, one round of retesting is included at no charge, followed by an attestation letter signed by a named qualified individual for your auditor, customer or board.
Who does the testing?
Alexander Sverdlov, Founder and Principal Security Consultant, CISSP, CEH, CHFI and Mandiant certified, formerly of the Microsoft Security Consulting team, who secured nuclear energy infrastructure at the Emirates Nuclear Energy Corporation and has served as a UN cybersecurity panelist, with 200+ security assessments across 14 countries since 2013. The person on your scoping call tests your systems, runs the workshop and signs the attestation.
Will the report satisfy our SOC 2, ISO 27001, HIPAA or CMMC assessor?
SOC 2 auditors expect penetration test reports as evidence under CC7.1 and CC4.1 and leave the method to you. ISO/IEC 27001:2022 Annex A 8.8 and A 8.29 are covered by the findings register and by testing applications before acceptance. Under the HIPAA Security Rule, technical testing is accepted evidence for the 45 CFR 164.308(a)(8) evaluation and the 164.308(a)(1)(ii)(A) risk analysis. For NIST SP 800-171 control 3.12.1, a pentest is accepted assessment evidence for CMMC Level 2 practice CA.L2-3.12.1. GDPR Article 32(1)(d) asks for regular testing of the effectiveness of security measures, which the annual report and retest letter document.

12 / THE DETAIL

Related Services

Vulnerability assessment - Active Directory security assessment - Cloud security consulting - AWS security assessment - IT security audit - Bank pentest - DORA TLPT - SaaS virtual CISO - Pricing

Between annual pentests, Pentestas runs continuous AI penetration testing against the same scopes.

Comparing providers? See the best pentest companies ranked by scope or Our ranking of 40 penetration testing companies covers boutiques, research-led firms, PTaaS and autonomous platforms, with each one's pricing model.