Digital Roxy runs manual penetration tests against web apps, APIs, networks, mobile apps, and cloud environments for US companies that need real findings, not checkbox scans. Every engagement is led by OSCP-certified offensive security engineers and delivered with CVSS-scored findings, exploitation proof, remediation guidance, and a free retest once your team ships the fix.
A penetration testing service simulates real-world attackers against your systems under a signed scope. The goal is to find exploitable vulnerabilities before a criminal, ransomware operator, or nation-state actor finds them. The output is not a list of scanner alerts. It is a report of confirmed findings that have been manually verified, exploited in a safe environment, scored for business impact, and paired with specific remediation steps your engineers can act on.
Digital Roxy runs penetration tests as offensive engagements, not compliance theater. Every finding in our reports has been reproduced by a human tester. Every remediation recommendation has been written by someone who has fixed the same bug in production code. Every retest is included in the engagement fee, so your team gets a clean attestation once the fix ships.
Automated scanners catch configuration mistakes and known CVEs. They miss business logic flaws, chained exploits, privilege escalation paths, and the kind of subtle authorization bugs that get companies into breach notification territory. A real pentest assumes the attacker has time, skill, and motivation.
This page is the top-level guide to our penetration testing service. If you know which testing type you need, jump to the testing types grid below. If you need a budget range, see the pricing tiers. If you have a scoping call booked, you can also download a sample report on request.
These three services get sold interchangeably and they should not be. Each answers a different security question, carries a different scope, and produces a different report. Buying the wrong one costs money and leaves gaps.
Every Digital Roxy penetration test follows the Penetration Testing Execution Standard, with OWASP Top 10 coverage for web targets and NIST SP 800-115 structure for reporting. Seven phases, documented handoffs at each gate, no shortcuts.
We define targets, exclusions, rules of engagement, test windows, and emergency contacts in a signed scope document. Production environments get explicit sign-off. Third-party hosted assets (AWS, Azure, Cloudflare) get provider notification when required. Nothing starts until the scope is locked.
Passive reconnaissance against the target attack surface. DNS enumeration, subdomain discovery, certificate transparency logs, employee profiling from public sources, exposed credentials on breach dumps, leaked source code on public Git platforms. This phase finds what you did not know was exposed.
We map the target to a concrete threat model. Who attacks this asset and why. What data would they want. What is the realistic attack path from external to crown jewels. This is not a generic STRIDE exercise. It is a tailored model that drives what gets tested hardest.
Automated scanning gets used here, and only here, to build coverage breadth. Burp Suite Pro, Nuclei, Nessus, and custom tooling identify candidate issues. Every automated finding then flows into the next phase for manual verification. Raw scanner output never makes it into the final report.
This is where pentest stops looking like a scan and starts looking like an attack. Manual testers chain findings into real exploit paths. An exposed .git directory plus a default admin credential plus a privilege escalation CVE becomes a full takeover scenario, documented with request and response captures, screenshots, and proof-of-concept code.
Once an exploit works, we ask the follow-up question attackers ask: what does this foothold unlock. Lateral movement testing, privilege escalation, persistence simulation, and data access assessment. We stop at the pre-agreed boundary every time. No data exfiltration. No destructive actions. Proof of access is enough.
Every engagement ends with an executive summary for leadership, a technical report with CVSS-scored findings and full reproduction steps for engineers, a compliance attestation letter for auditors, and a free retest after your team ships the fix. Clean retest means a clean attestation.
Every report is accompanied by a live debrief with your engineering team. We walk through the exploit chains, explain why each finding matters in your architecture, and answer questions. Your developers leave the call knowing how to prevent the same class of bug from shipping again.
Every testing type has its own methodology, toolset, and report format. A web app pentest is not a network pentest. Mobile app testing is not API testing. Choose by asset, not by vendor marketing.
OWASP Top 10 plus business logic, authentication, authorization, and session management. SPAs, multi-tenant SaaS, e-commerce, and CMS targets. Manual exploitation of XSS, SQLi, IDOR, SSRF, and deserialization.
See Web PentestExternal and internal network testing. Perimeter services, firewall rules, segmentation gaps, Active Directory weaknesses, Kerberos attacks, lateral movement, and privilege escalation to Domain Admin.
See Network PentestiOS and Android testing to OWASP MASVS. Insecure storage, certificate pinning bypass, deep link hijacking, IPC flaws, reverse engineering resistance, and the mobile API behind the app.
See Mobile PentestREST, GraphQL, and gRPC testing to OWASP API Top 10. Broken object-level authorization (BOLA), mass assignment, JWT weaknesses, rate limiting failures, and excessive data exposure.
See API PentestIAM policy review, S3 and blob exposure, metadata service abuse (IMDSv1/v2), Lambda permission escalation, Kubernetes cluster testing, and misconfigured security groups across multi-cloud environments.
See Cloud PentestContinuous pentest program on a subscription. Always-on scanning plus quarterly deep-tests plus unlimited retests plus a dedicated Slack channel. For companies that ship weekly and need security to keep up.
See PTaaSEvery engagement ships with a compliance attestation letter tailored to the framework your auditor wants. One pentest, the right documentation for whichever standard is on the line.
Requirement 11.4 mandates annual external and internal penetration testing for any environment storing, processing, or transmitting cardholder data. Our reports include segmentation testing validation, which PCI explicitly requires for merchants claiming reduced scope.
The SOC 2 Trust Services Criteria CC7.1 (detection and monitoring) and CC4.1 (risk assessment) both reference external security testing. A current penetration test report is the cleanest evidence artifact auditors accept for these controls.
The HIPAA Security Rule requires covered entities to conduct a regular risk analysis of ePHI systems. Penetration testing is the recognized method for validating technical safeguards under 45 CFR 164.308(a)(1)(ii)(A). Reports are BAA-ready.
ISO 27001 Annex A.12.6 on technical vulnerability management and the ISO 27002 guidance on intrusion testing both align with an annual penetration test. Reports are structured to map findings directly to Annex A control references for your ISMS evidence package.
GDPR Article 32 requires a process for regularly testing the effectiveness of technical measures. A pentest is the direct evidence artifact for this obligation. Reports include data-flow findings relevant to Article 32(1)(d) for EU and UK-regulated data.
The NIST Cybersecurity Framework Protect and Detect functions both call for regular testing. Reports are tagged against NIST CSF 2.0 subcategories (PR.DS-01, PR.IP-07, DE.CM-08) so your governance team can slot findings directly into the framework.
These are the classes of findings our engagements surface every month. Not scanner warnings. Confirmed vulnerabilities with proof-of-exploit and remediation steps.
An unauthenticated endpoint accepts serialized objects without type validation. Crafted payload triggers deserialization against a gadget chain, giving shell access to the application server. Found in a Fortune 500 internal portal, patched within 72 hours of disclosure.
Sequential user IDs in an API response, no object-level authorization check. Iterating IDs exposes name, email, phone, and purchase history of every customer. A single exploit chain that would trigger breach notification under state laws in all 50 states.
Image proxy accepts arbitrary URLs and fetches them server-side. Request to http://169.254.169.254/latest/meta-data/iam/security-credentials returns long-lived AWS access keys. Full cloud account compromise from a single uploaded image URL.
JWT validation accepts both RS256 and HS256 algorithms without enforcing the expected algorithm. Attacker signs a new token using the public key as an HMAC secret, granting arbitrary user impersonation including admin role.
/.git/ directory accessible from the production web root. Full source code extraction including database credentials, S3 access keys, and a historical commit containing a private signing key that was "removed" in a later commit. Git history is forever.
Service account with SPN set and a weak password yields a TGS ticket that gets cracked offline in under two hours. Service account runs with local admin rights on the file server, providing lateral movement into the finance department share.
Every Digital Roxy pentest engagement ships with the full documentation package your leadership, engineering, and audit teams each need.
Two pages, non-technical. Risk posture, critical findings, business impact, and remediation timeline. Written for the board and C-suite, not engineers.
Full findings with CVSS 3.1 scores, exploit reproduction steps, request and response captures, screenshots, and architectural recommendations. The report engineers actually use.
Signed letter tailored to PCI DSS, SOC 2, HIPAA, ISO 27001, or the specific framework driving the engagement. The artifact your auditor needs.
After your team ships fixes, we retest every finding and produce a clean retest report showing status: Fixed, Partially Fixed, or Open. Retest is included in the original engagement fee.
60-minute working session with your engineering team. We walk through exploit chains, answer questions, and discuss remediation approaches specific to your stack.
Prioritized fix plan with effort estimates and code-level guidance. Designed as a working document your team can execute against, not a security team wishlist.
Penetration testing pricing depends on scope: target count, environment complexity, and required compliance framework. These tiers set the baseline. Every engagement gets a fixed-price quote after a free 15-minute scoping call.
Single asset pentest. Right for startups, one web app, or a focused network segment that needs annual testing.
Multi-asset engagement. Web + API + network or web + mobile + cloud. Right for SOC 2 and PCI DSS annual requirements.
Always-on pentest program. Right for SaaS companies shipping weekly that need continuous coverage.
Enterprise engagements (red team, adversary simulation, supply chain pentest, regulated-industry work) scope at $40,000 and up. All quotes are fixed-price after a 15-minute scoping call. No hourly billing. No scope creep fees.
Every tester on your engagement holds Offensive Security Certified Professional (OSCP) or equivalent practical certifications. We do not staff pentests with junior scanners.
Automated tools build coverage breadth. Humans find the bugs that matter. Our engagements are 70% manual, 30% tool-assisted. The ratio is inverted at most firms.
Every engagement includes a free retest after your team ships fixes. Clean retest means clean attestation for your audit. No separate fee, no renegotiated scope.
Reports include code snippets, configuration examples, and architectural recommendations written by engineers who have fixed the same bug in production. Not vendor-speak.
We quote fixed prices after a 15-minute scoping call. No hourly billing. No scope creep invoices. If the engagement expands, the pricing conversation happens before any new work starts.
Vulnerabilities and architectural details from your environment stay confidential. Signed NDA before kickoff, evidence destruction after attestation, no case studies without written approval.
Timeline for a typical Full-Stack Pentest engagement. Scoped Pentests compress to one week. PTaaS runs continuously.
15-minute scoping call to define targets, exclusions, test windows, and rules of engagement. Signed scope document and mutual NDA in place before any work starts. Test accounts provisioned by your team.
Passive OSINT against the target attack surface. Automated vulnerability analysis with Burp Suite Pro, Nuclei, and Nessus. End of week: candidate finding list handed to the exploitation phase.
Two testers running manual exploitation against confirmed candidates. Critical findings disclosed in real-time through a shared Slack channel so your team can start remediating before the report ships. Full post-exploitation walk through.
Technical report, executive summary, and compliance attestation drafted and peer-reviewed. 60-minute live debrief with your engineering team to walk through findings and remediation approaches.
Your team ships fixes. We stay available in Slack for clarifying questions. No additional fees for remediation support during the engagement window.
We retest every finding and update status: Fixed, Partially Fixed, or Open. Clean retest gets a clean attestation letter you can hand to your auditor. Retest is included in the engagement fee.
Every state has a different regulatory mix, industry profile, and threat landscape. Pick your state for local context on what a pentest looks like in your jurisdiction.
The full cyber security program: monitoring, incident response, and security architecture. Pentest is the offensive leg.
Related Reactive ServiceAlready breached? The reactive service that cleans, hardens, and documents a compromised WordPress environment within hours.
Continuous OptionContinuous pentest program for teams that ship weekly. Always-on coverage, quarterly deep-tests, unlimited retests.
Book a 15-minute scoping call. Tell us what you need tested and which compliance framework is driving it. You get a fixed-price quote within one business day.