Start with what matters.
These are useful areas to discuss when defining your assessment. The checks we agree on will depend on your systems, access and goals.
Client information
Examine whether account permissions and document access keep one client's information separate from another's.
Connected workflows
Assess agreed API endpoints and user roles where information moves between your team, customers and business systems.
Public exposure
Review the websites, login pages and exposed services that provide a route into your environment.
The right assessment for your systems.
You don’t need to know which test to ask for. These services provide a starting point for a conversation about your environment.
Web application and API testing
Investigate authentication, record access and business logic in customer and staff portals.
Security configuration reviews
Review agreed access settings and configurations supporting sensitive workflows.
Network penetration testing
Understand exposed services and potential entry points across agreed network assets.
A clear scope comes first.
Identify the portals, user roles and integrations you want to understand. We can discuss test accounts and representative data, who owns each system and any operational constraints before agreeing on scope and written authorisation.
Findings your team can act on.
- A report explaining identified weaknesses, their potential impact and practical remediation guidance.
- A discussion of the findings to help you plan priorities with your developers, IT team or providers.
- A conversation about follow-up testing where needed, with any retesting scoped separately.
