Skip to content
A symmetrical interior corridor between rows of server infrastructure.
Illustrative technical infrastructure

GIFGIF / OFFENSIVE SECURITY

Penetration testing

An authorised assessment of agreed systems and applications to help decision-makers understand security weaknesses and prioritise next steps.

AGREED TARGETSWRITTEN AUTHORITYDEFINED BOUNDARIES

No permission.
No test.

Written authorisation, identified targets and agreed rules of engagement are prerequisites. Activity stays within that scope.

01THE SECURITY QUESTION

A test is responsible only when its boundaries are clear.

Digital services support essential operations, sensitive information and relationships with customers and partners. A weakness in a system or application can matter to technical teams and to the people accountable for continuity, legal obligations and organisational risk. Penetration testing offers a bounded way to assess agreed systems for security weaknesses under explicit authorisation.

We assess agreed systems and applications within a defined scope. The purpose is to make relevant weaknesses understandable and help prioritise decisions. No test establishes that a system is entirely secure; an assessment reflects the systems, access, conditions and time period included in its agreed scope.

Written authority, clear boundaries and rules of engagement define what may be tested, what must remain untouched and how unexpected operational concerns should be handled. These are prerequisites, not administrative afterthoughts.

02ASSESSMENT AREAS

Systems in focus.
Boundaries in writing.

The work is defined by the systems and applications agreed for this assessment. These descriptions do not expand that scope.

01
APPLICATIONS

Web and business applications

Assess an agreed application surface for weaknesses relevant to its use and exposure.

Applications often connect users, business processes and sensitive data. A scoped assessment can examine agreed functionality and the security conditions relevant to the commissioning question. Exact coverage depends on authorised scope, available environments and constraints agreed in advance.

Findings should describe the observed issue, its potential significance and enough context for the responsible team to evaluate remediation. A reported weakness is not automatically evidence of compromise, and components outside the agreed scope are not represented as assessed.

02
SYSTEMS

Agreed systems and boundaries

Focus activity on explicitly identified systems, with ownership and permission established in advance.

Systems may be selected to answer a particular business question, such as assessing a defined service or environment. Before testing, the engagement needs to identify authority, permitted targets, exclusions, timing and operational restrictions.

Complex environments may involve third-party hosting, shared infrastructure and connected services. The client should identify dependencies and obtain any additional permissions required. A technical relationship alone does not establish authority; anything not clearly included remains out of scope until clarified.

03
DECISIONS

Findings that support remediation

Translate observed weaknesses into a clear record for technical owners and leadership.

A useful report explains what was assessed, what was found, why a finding may matter and what limits apply. Prioritisation helps teams consider the nature of a weakness in its system context; a single rating cannot resolve every business trade-off.

Remediation remains with the system owner and its technical team. The level of detail, validation or follow-up should be agreed for the engagement. Retesting or additional assurance must be separately confirmed and is not assumed from an initial assessment.

IMPORTANT BOUNDARYPenetration testing is a point-in-time assessment, not a guarantee of security, compliance, absence of compromise or coverage of untested systems.

03HOW AN ENGAGEMENT TAKES SHAPE

Authority first. Scope before activity.

Technical work proceeds only within written permission and an agreed operating framework appropriate to the systems involved.

01

Confirm authority

We identify the organisation able to authorise work and confirm written permission for in-scope systems.

02

Define the rules

We agree targets, exclusions, timing, boundaries, contacts and how unexpected operational concerns are handled.

03

Assess only the scope

We work within documented permission and constraints. Scope changes require clarification before expansion.

04

Explain findings and limits

We report observed weaknesses and context so owners can evaluate remediation and understand what was not tested.

04WHY GIFGIF / OUR APPROACH

Our approach treats authorisation as part of the work.

We bring technical assessment into focus for consequential decisions. Clear scope, explicit permission and candid reporting are the foundations for useful security testing.

01

Permission is explicit

We require written authority and identified systems before assessment activity.

02

Boundaries are meaningful

Agreed targets, exclusions and rules of engagement define responsible limits.

03

Findings serve decisions

We explain observed weaknesses and limits in terms technical owners and decision-makers can use.

05ILLUSTRATIVE COMMISSIONING CONTEXT

Reasons to consider a scoped assessment

Examples of questions to help frame an enquiry; these are not case histories.

01

A service is approaching launch

A product owner may want an authorised assessment of an agreed application before exposing it to customers or partners.

02

A material system has changed

A technical or risk team may want to assess defined systems after a significant change, with assets and timing agreed in advance.

03

Leadership needs a clearer risk picture

An organisation may need findings that help technical owners and business decision-makers discuss remediation priorities.

07CONFIDENTIAL ENQUIRY

Define what is authorised before testing begins.

A short outline of the question is enough to discuss a proportionate scope. Please do not include sensitive information or documents in an initial enquiry.

Make an initial enquiry