05 Service

Penetration testing

Penetration testing for web applications, APIs and infrastructure, with a prioritised report and retest.

The problem

Signs that this area needs attention.

01

The need to validate security before a launch.

02

Requirements from clients, contracts or investors.

03

New code or a migration without a security review.

04

Suspicion of an incident or unauthorised access.

What we do

Concrete deliverables, adapted to your context.

01

Scope definition and formal authorisation.

02

Web application and API testing.

03

Infrastructure and configuration testing.

04

Report with evidence and risk-based prioritisation.

05

Findings presentation session.

06

Retest after fixes.

How we work

01

Scope, rules and testing window alignment.

02

Reconnaissance and controlled testing.

03

Validation of findings and evidence.

04

Report and debrief session.

05

Retest and closure.

Who it is for

  • Companies about to launch a digital product.
  • Online stores and systems that handle payments.
  • Teams that need independent security evidence.

Expected outcomes

  • Vulnerabilities found before an attacker does.
  • Clear remediation priorities.
  • Technical evidence for clients and audits.

Frequently asked questions

Is the test authorised?

Yes. No test starts without a defined scope and written authorisation from the system owner.

What is the difference between a pentest and a scan?

An automated scan finds signals. A pentest validates exploitability, impact and context through human analysis.

Is the report technical or executive?

Both. There is an executive summary, technical details and evidence for the team to fix.

Need support in this area?

Describe the current scenario. The initial reply indicates scope, next steps and whether it makes sense to move forward.