Wire Hold
← All services

Validate security in an agreed environment

Scoped Penetration Testing

Test defined security boundaries and explain what the evidence means for your business.

Request a testing scope

Quoted to scope. Deliverables, schedule and fees are agreed before work begins.

Who it is for

Organizations needing a focused assessment of applications, APIs or selected infrastructure

What we can deliver

  1. Written scope, authorization, rules of engagement and test windows.
  2. Testing of agreed targets and risk scenarios.
  3. An evidence-based report with prioritized findings and fix guidance.
  4. A technical debrief and retesting where included in the engagement.

The final scope, access requirements, schedule and included handoff are agreed for your engagement.

01 / Fit

When this is a useful next step

  • You need evidence about defined security boundaries in a system you can authorize for testing.
  • There is a clear question, such as whether a user can reach another role's data or an API enforces expected access.
  • You can provide a technical contact, a test window and written rules of engagement.

02 / Delivery

How the work unfolds

  1. Authorize and plan

    Confirm asset ownership, targets, environments, accounts, permitted methods, excluded activities, stop conditions and escalation contacts in writing.

  2. Test agreed scenarios

    Evaluate the scoped attack paths and controls using the approved level of activity. Keep records that connect observations to the relevant target and test condition.

  3. Explain findings

    Report reproducible evidence, business relevance, affected boundaries and remediation priorities. Communicate urgent findings through the agreed channel.

  4. Debrief and retest

    Review results with technical owners. If retesting is included, check the specified fixes within the agreed window and document the result.

We agree on the scope, responsibilities, schedule and completion criteria before starting. These steps are adapted to that agreement.

03 / Handoff

What you can put to use

  • Rules of engagement

    A written testing boundary, permitted activity, test window and communication process.

  • Assessment report

    Executive context, technical findings, supporting evidence, remediation guidance and coverage limitations.

  • Debrief and optional retest record

    A technical walkthrough and, when contracted, validation results for agreed remediated findings.

Your proposal identifies the included outputs, their format and the review or handoff session. Further implementation or support is agreed separately.

04 / Preparation

What we need from you

  • Provide an asset list and a person authorized to approve testing.
  • Identify system owners, emergency contacts and any third-party approval requirements.
  • Prepare agreed test accounts, backup or recovery arrangements and a suitable environment.

Scope boundaries

Testing starts only after written authorization and scope agreement. Destructive activity, denial-of-service testing, social engineering and third-party systems are excluded unless expressly authorized and feasible within the engagement. Findings reflect the permitted scope and time available.

05 / Illustrative scope

What an engagement could look like

This is a planning example, not a client result or a promise of outcomes.

  • Starting situation

    A software owner wants to evaluate role boundaries in one customer portal.

  • Agreed work

    Agree on test accounts and API targets, assess selected authorization scenarios and document reproducible findings.

  • Useful handoff

    A focused report and debrief, with a retest option defined in the proposal. This is a sample scope, not a claim that a target is vulnerable.

06 / Questions

Before you inquire

Can testing happen in production?

Only if it is explicitly authorized and the rules, operational risks and recovery arrangements are agreed. A representative non-production environment may be a better starting point.

Does a clean report guarantee security?

No. It describes what was tested and observed within the agreed constraints. Untested components, later changes and new attack methods remain outside that evidence.

Start with a conversation.

Tell us who the work is for, what you want to improve and your preferred timing. We will confirm fit and provide a scope-based quote, with deliverables, schedule and fees agreed before work begins.