Two roles should never share this record
A small application needs to know whether a user can reach another role’s data. Testing uses authorised accounts and records minimal evidence for the responsible developer.
OSINT, Pentesting & Red Teaming
Find weak points. Prioritise the fixes.
Replace assumptions with findings your developers can act on. Understand the tested attack paths, the business impact and the order in which to fix them.
No one-size-fits-all price. Scope, deliverables and cost are agreed in writing.
Is this your team?
Made for teams like yours.
For product owners, engineering teams and security leads that need a focused test of their application, API or AI attack surface.
- You are releasing a web application or API and need to test how access controls behave in practice.
- An AI feature introduces new prompts, tools or data flows that deserve a focused security assessment.
- You need a report that engineers can use and decision-makers can understand.
What changes for you
Before the next launch, know what has actually been tested—and what still needs attention.
A focused assessment with evidence, business context and prioritised remediation. OSINT/CTI, code review, vulnerability scanning, penetration testing, red-team exercises and AI security testing are distinct services.
Scope first. Useful work next.
The value, in plain English
Web application penetration testing looks at what an attacker can do inside the agreed boundaries. API penetration testing and manual security testing examine access, authorisation and business logic, then turn the findings into a fix list your team can work from. Written permission comes first.
From the first question to a useful handover
Agree the boundaries before touching the target
Penetration test scope definition identifies the application, roles, endpoints and restrictions. Pentest rules of engagement record owner authorisation, stop conditions and the emergency contact.
Test the paths a scan can miss
Authenticated pentesting uses agreed test accounts for application access-control testing, API authorisation testing and business logic security testing. Supporting scans complement the manual work.
Make the findings useful
Vulnerability risk prioritisation connects evidence with business impact. An actionable penetration test report, a pentest executive summary and remediation retesting support the fix decision and handover.
Where this earns its place
Illustrative use cases. The actual work and acceptance checks are agreed in your proposal.
An AI feature changes the attack surface
An explicitly scoped AI security assessment can examine permissions, interfaces and data flows. The method and targets are agreed before testing begins.
CLIENT FEEDBACK
What our methodology delivers
What to agree for this service
Compare services and prepare your brief ↗Deliverables
- Written scope, methodology, Rules of Engagement, targets, stop conditions and third-party restrictions before testing.
- Protected evidence, finding severity and business impact, test limitations and practical remediation guidance.
- Management summary, technical report, handover session and one verification of the included fixes within 30 days of delivery.
- Package scope
- Scoped Web / API Pentest: one small web application, up to two roles and up to ten API endpoints. Focused manual testing with supporting automated review, a report, handover and one remediation verification within 30 days.
- What your team provides
- Provide written authorisation from the appropriate asset owner, a test environment or agreed production restrictions, test accounts and an emergency contact. You remain responsible for remediation and risk decisions.
- Outside the package
- Complete code coverage is not promised. Extensive OSINT, organisation-wide red teaming, phishing, load testing and destructive testing are separately quoted. An automated scan alone is not a full pentest.
Acceptance examples to discuss
Illustrative checks for negotiation. These are not completed test results, new contractual promises or additions to the package. The written proposal defines the actual acceptance criteria.
- Any reported finding records an authorised target, proportionate reproduction evidence, severity and remediation guidance.
- The agreed verification records the status of included fixes within the authorised scope and the package’s 30-day window.
Stuck on an AI decision? Get a clear next step.
A focused review of one AI purchase, integration or agent idea. Turn an uncertain decision into a written brief your team can act on.
€490 for one decision. Any applicable VAT and the agreed scope are confirmed in writing before acceptance. Requesting a review is not a purchase or a confirmed booking.
YOUR NEXT MOVE
Get your tailored proposal
Tell us about your organisation, your team and the product or process you want to improve. We will review the fit and follow up with the questions needed to shape a proposal. Scope, deliverables, timing and price are agreed before work begins.
Q&A
Good questions. Straight answers.
Can you test any website or third-party service?
No. Testing requires written authorisation, defined targets and Rules of Engagement. Third-party terms and permissions must allow the agreed tests; stop conditions apply throughout.
Can the scope cover AI and sensitive workflows?
Yes, where agreed. AI interfaces, permissions, configuration, code and APIs can be examined. Call documentation, care and sales systems also need checks of information restrictions and data flows.
What is the difference between a vulnerability scan and a pentest?
Vulnerability scan versus pentest is a useful buying distinction: a scan flags potential issues; a scoped pentest combines manual investigation with supporting tools and interprets findings in context. Automated output alone is not a complete pentest.
What does the initial web and API package cover?
One small web application, up to two roles and up to ten API endpoints, with a report, handover and one verification of included fixes within 30 days of delivery. The proposal states the exact targets and acceptance criteria.
How do you protect sensitive test evidence?
Secure pentest evidence handling uses limited, protected evidence needed to explain a finding. Access, sharing and retention are agreed for the assessment; live secrets and unnecessary personal data do not belong in a broadly circulated report.
Can we add OSINT and threat intelligence?
A separate passive OSINT assessment or cyber threat intelligence snapshot covers one organisation and up to three owned domains. It is distinct from intrusive testing and continuous monitoring. The scope and sources are agreed separately.
Is a red-team exercise included?
A scoped red team exercise is a separate engagement with its own objectives, authorisation and restrictions. Phishing, organisation-wide red teaming, load testing and destructive testing are not part of the entry web/API package.
What can a clean report actually tell us?
Penetration testing limitations matter: findings reflect the targets, methods and test period. A report supports a risk decision and remediation retesting; it cannot prove that every vulnerability has been found or establish complete compliance.
Make an informed move.
Practical guides to help your team ask better questions before committing.