Offensive Security

Penetration Testing

PSC penetration testing combines threat modelling, manual exploration, controlled exploitation, and evidence-based reporting across applications, APIs, infrastructure, mobile, and client software. It is designed to show which weaknesses form credible attack paths, not to deliver an unverified scanner export.

The engagement is for teams that own a defined system or environment and need practical assurance before release, after major change, or as part of an established security program. The outcome is a prioritized set of reproducible findings, an attack-path narrative, and clear remediation and retest decisions.

Subject-matter owner: Mike Chen · Lead Penetration TesterReviewer: Viral Maniar · Managing Director and Principal Consultant
Risk focus

Problems this engagement addresses

The scope follows credible attack and failure paths rather than a generic control checklist.

  • Authentication, session, and authorization failures that expose another user's or tenant's data.
  • Injection, unsafe file handling, server-side request forgery, and insecure output processing.
  • Internet-facing or internal infrastructure weaknesses that enable foothold, privilege escalation, or lateral movement.
  • Business-logic abuse that scanners cannot understand or validate.
  • Security controls that exist on paper but fail under realistic attack sequences.
Engagement fit

When this service is useful

A clear fit decision protects assessment quality and prevents a broad request from becoming a shallow exercise.

Designed for

  • A release, migration, acquisition, or major architecture change with a defined target.
  • A web application, API, infrastructure range, mobile app, or client application under your authority.
  • Teams that can provide technical owners and act on remediation findings.
  • Organizations seeking manual validation beyond automated vulnerability scanning.

Not the right fit for

  • An undefined request to test every asset without ownership, boundaries, or priorities.
  • A substitute for secure development, patch management, or continuous attack-surface management.
  • Testing third-party systems without documented authorization.
Scope

Choose the boundary that matches the decision

Options can be combined after owners, environments, authority, safety limits, and expected evidence are agreed.

Applications and APIs

Web, REST, GraphQL, and SOAP interfaces, including identity, tenancy, workflows, inputs, outputs, and resource abuse.

Infrastructure and identity

External or internal hosts, network services, Active Directory, segmentation, privilege paths, and exposed management planes.

Mobile and client software

Android, iOS, desktop, local storage, binaries, runtime behavior, platform interfaces, and client-server trust.

Prerequisites

  • Confirmed ownership, target inventory, environments, test windows, and emergency contacts.
  • Representative user roles and test data for authorization and workflow coverage.
  • Architecture, API specifications, and deployment context where available.
  • Written rules of engagement covering safety limits, source addresses, and escalation.

Explicit exclusions

  • Denial-of-service, destructive changes, persistence, or social engineering unless explicitly approved.
  • Assets discovered outside the authorized target list.
  • Source-code review, cloud configuration review, or wireless testing unless included in scope.
  • A guarantee that no vulnerability exists after a time-bounded assessment.
Methodology

Evidence at every phase

Each phase produces an observable input to the final risk and remediation decisions.

  1. Scoping and threat modelling

    Define assets, roles, trust boundaries, business workflows, likely adversaries, safety constraints, and success criteria.

  2. Reconnaissance and mapping

    Build a complete target map from application routes, API operations, services, identities, and technology behavior.

  3. Manual security testing

    Test identity, access control, input handling, configuration, business logic, privilege boundaries, and chained attack paths.

  4. Controlled validation

    Safely demonstrate impact, preserve evidence, remove test artifacts, and escalate critical findings through the agreed channel.

  5. Reporting and retest

    Deliver prioritized findings, technical reproduction, remediation guidance, stakeholder readout, and verification of agreed fixes.

Standards and frameworks used

OWASP WSTGOWASP ASVSOWASP API Security Top 10PTESNIST SP 800-115MITRE ATT&CK
Outputs

Deliverables built for decisions and fixes

Reporting separates observed evidence, uncertainty, business priority, and the action needed to verify remediation.

  • Executive summary and attack-path narrative.
  • Risk-ranked findings with evidence and reproducible steps.
  • Affected assets, roles, requests, and security-control observations.
  • Developer and infrastructure remediation guidance.
  • Technical readout and agreed remediation retest.

Severity approach

PSC rates findings using technical exploitability and impact, then adjusts priority for exposed data, reachable privileges, business workflow, existing controls, and credible attack chaining. CVSS may support consistency, but it does not replace business context.

Readout

The readout separates immediate containment, near-term remediation, and structural improvements. Engineering teams receive the evidence needed to reproduce and fix each issue; leadership receives the attack path and decision context.

Remediation support

PSC answers finding-specific questions and helps teams distinguish root-cause fixes from narrow symptom patches. Recommendations are written for the technology and control boundary observed during testing.

Retest policy

The retest repeats the original path against the corrected environment and records fixed, partially fixed, accepted, or unresolved outcomes. New functionality or broad architecture changes require separate scope confirmation.

Typical process

A governed path from scope to verification

Timing depends on scope, access, environment, and evidence quality; PSC confirms milestones during scoping rather than publishing unsupported duration promises.

01

Define authority and scope

02

Prepare roles and test access

03

Map and test the attack surface

04

Escalate material findings

05

Read out and verify fixes

FAQ

Questions buyers ask before scoping

Final rules, access, and deliverables are confirmed in the engagement scope.

How is penetration testing different from vulnerability scanning?

Scanning identifies potential issues at scale. Penetration testing manually validates behavior, authorization, business logic, exploitability, and attack chains, while removing false positives and documenting observed impact.

Do you need source code?

Not for a black-box or grey-box assessment. Source, architecture, and API specifications can improve coverage when the objective includes design or implementation assurance, but they are agreed during scoping.

Will testing disrupt production?

The rules of engagement define safety constraints, test windows, escalation contacts, and prohibited actions. High-risk validation is adapted, simulated, or moved to a safe environment when production impact is plausible.

What happens after the report?

PSC provides a stakeholder readout, answers remediation questions, and retests agreed fixes. The retest records the status of the original evidence path rather than simply checking that code changed.

Scope this service

Discuss penetration testing with PSC.

Share the system, decision, and constraints. PSC will confirm whether this service fits before proposing a scope.

Request a scoped assessment