Penetration testing for software sold to enterprises and government
Procurement teams and tender documents often ask for independent security evidence before a platform is approved. We test the product they will run and give you a report you can attach to a tender or a vendor review.
- Role and permission models
- Multi-tenant separation
- Integrations and single sign-on
- Hosting and cloud
Why teams in this sector test
A tender or procurement review asks for a test
Some requirements name a type of auditor or a test within the last 12 months. Read the exact wording first.
A large rollout is approved
More users, more roles and more integrations than the product was tested with.
A major release is planned
New modules, a new identity provider or a move to new infrastructure.
Services most teams in this sector start with
Web application penetration testing
Manual testing of logins, roles, business logic and data access in your product.
API penetration testing
REST and GraphQL endpoints tested for broken authorisation and data exposure.
Cloud security assessment
AWS, Azure and Google Cloud configuration, IAM and exposed services.
Where we look first
Every engagement is scoped to your systems. These are the areas that most often decide the outcome in this sector.
Role and permission models
Department, district and administrator roles, and what each can reach.
Multi-tenant separation
Whether one organisation can see another’s records through the UI, API or exports.
Integrations and single sign-on
Connections to identity providers, payment gateways and other systems.
Hosting and cloud
Configuration, secrets and administrative access.
Guides for this sector
Other industries:
Answering security questionnaires on pentesting
What customer questionnaires ask about penetration testing, how to answer, and what to attach.
DORA and NIS2: what EU companies need to test
What DORA, NIS2 and GDPR say about testing security, and where a penetration test fits.
When to retest after a major release
Which changes should trigger a new test, and how to plan testing around frequent releases.
Tell us what needs testing and by when.
You receive a written proposal with scope, method, timeline and a fixed price. We reply within 1 business day.