PTEST SECURITY

Questions? Start here.

Everything you might want to know before working with us, from scoping and penetration testing to reporting, retesting and private security training.

Getting started

Not sure what you need tested or where to begin? Start here.

These questions cover scoping, timescales, what we need from you, and what to expect when you work with us.

Working with us

How do I arrange a penetration test or training?

Get in touch through our contact form or email info@ptestsec.com and tell us a little about what you need.

For penetration testing, an overview of the systems or applications involved and any timescales you’re working towards is enough to start the conversation. For training, tell us who the training is for and what you’d like the team to learn.

Don’t worry if you haven’t worked out the exact scope yet. We can help you define that before anything is agreed.

How is an engagement confirmed?

Once we understand what you need, we’ll agree the scope, approach and commercial details with you before any work begins.

For penetration testing, this includes what will be tested, any important exclusions and the rules of engagement. For training, we’ll agree the course content, delivery format and requirements for your team.

Everything is agreed before the engagement starts, so both sides are clear on what’s being delivered.

Do you work outside London?

Yes. We’re based in London and work with organisations across the UK.

Engagements can be delivered remotely or on site depending on what we’re testing and what makes sense for the scope. Private security training can also be delivered remotely or at your organisation’s location.

Scope and testing

What do you need to scope a penetration test?

We need enough information to understand what you want tested, what the environment looks like and what you’re hoping to learn from the assessment.

That might include the applications or systems involved, whether they’re production or test environments, the types of users or access available, anything that needs to remain out of scope, and any timescales you’re working towards.

You don’t need to arrive with a finished scope. We’ll work through the details with you and agree exactly what’s included before testing begins.

Do you test production systems?

Yes. Penetration testing can be carried out against production systems where that is appropriate and agreed as part of the scope.

We take a risk aware approach to live environments, considering the potential impact of testing as we work. If an activity could introduce unnecessary risk to availability or data, we’ll discuss the appropriate approach with you rather than simply proceeding.

Where more intrusive testing is required, we can agree whether it is better suited to a staging or other non-production environment.

What is included in the penetration test report?

You’ll receive an executive summary that gives a clear picture of the overall assessment, followed by detailed technical findings for the people responsible for investigating and fixing them.

Each finding explains what we identified, the evidence behind it, why it matters and what can be done to address it. The aim is to give your team enough context to understand the risk, reproduce the issue where appropriate and make informed remediation decisions.

The report is written so technical teams and decision makers can work from the same assessment without needing the same level of technical detail.

What does retesting include?

Retesting verifies that vulnerabilities identified during the original assessment have been properly addressed.

We revisit the relevant findings, test the changes made to resolve them, and confirm whether the original issue can still be reproduced. The results are then updated to give your team a clear record of the outcome.

A retest focuses on previously identified findings rather than repeating the entire penetration test. If you need the wider environment assessed again, we can scope that as a new assessment.

How long does a penetration test take?

The time needed depends on what we’re testing, the size and complexity of the environment, the access available and what you want the assessment to cover.

Once we understand the scope, we’ll recommend an appropriate testing window. If you’re working towards a release, audit or other deadline, let us know when you enquire and we’ll take that into account when planning the engagement.

What happens if you find something critical?

If we identify a serious issue that we believe needs immediate attention, we’ll let you know during the assessment rather than waiting for the final report.

We’ll give you enough information to understand what we’ve found and agree any next steps while testing continues.

Training

Are training courses public or private?

Our courses are delivered privately for your organisation rather than as public, open enrolment sessions.

Training can be delivered on site or remotely, with the content and level adapted to the people attending. This gives us the flexibility to focus on the skills, technologies and security challenges that are most relevant to your team.

Can you tailor a course to our technology?

Yes. Our courses can be adapted around the technologies, architecture and security challenges that are most relevant to your team.

That might mean putting more emphasis on a particular area, adapting examples and exercises, or incorporating technologies your team works with day to day.

We’ll discuss what would be most useful during scoping and agree the course content with you before the training takes place.

Social engineering

How do you keep social engineering testing controlled?

Social engineering engagements are carried out with written authorisation and clearly agreed boundaries before testing begins.

We work with you to define who and what can be included, any people or teams that must remain out of scope, the scenarios that can be used, and how the engagement should be handled if someone identifies or reports it.

The aim is to create a realistic test while keeping everyone clear on what has been authorised and where the boundaries are.

What types of social engineering can you test?

We can assess a range of authorised social engineering scenarios, including phishing, vishing, smishing and pretexting.

The right approach depends on what you want to test, so we’ll agree the scenarios, targets and boundaries with you before the engagement begins.

Still have questions?

If you’re not sure what kind of testing you need, what should be in scope, or whether we’re the right fit, just ask. Tell us a little about your environment and what you’re trying to achieve, and we’ll help you work out the next step.