Engagement lead, offensive security
Alex Terrats
Leads SecurePeak's offensive security work: network penetration testing and application security assessments. The approach looks past how a system breaks to how an organisation would notice and respond, so each finding comes with the detection and response questions it raises.
- Network penetration testing
- Application security
- Engagement leadership
Engagement coordinator, threat emulation
Maite Urrea
Coordinates SecurePeak's assessments and leads threat emulation, connecting what an assessment demonstrates to the detection change it calls for.
- Threat emulation
- Assessment coordination
Responsibilities
How an engagement is run
Every engagement names who is responsible for what before work starts. The responsibilities stay the same from one engagement to the next.
Engagement lead
Agrees the scope, schedule and reporting arrangements with you and coordinates the people involved.
Technical lead
Owns the technical approach, the quality of the evidence and the conclusions in the report.
Your named owner
A person on your side who approves scope changes, receives findings and accepts the handover.
- Kick-offConfirm objectives, boundaries, contacts and evidence handling.
- Working updatesProgress and blockers, at a cadence agreed in the scope.
- Findings reviewWalk through the evidence and agree priorities together.
- HandoverDeliverables, open questions and how results will be checked.
Clear ownership from the start.
The named team, responsibilities and communication channels are agreed during scoping. Start with your objectives and the systems involved.
Discuss your projectInterested in the work?
Introduce your security or engineering experience. A public write-up is optional.
Introduce yourself