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.
Patient-facing services
Examine agreed booking applications, forms and portals for weaknesses in how information is submitted and accessed.
Access to records
Investigate whether application roles and permissions separate access to sensitive information as intended.
Operational boundaries
Agree appropriate environments, testing windows and stop conditions before any assessment begins.
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
Assess authentication, permissions and data access within agreed patient-facing applications.
Website security testing
Review your public website, forms and supporting components for exposure.
Security configuration reviews
Examine agreed access settings and configuration choices supporting your digital services.
A clear scope comes first.
Identify the applications you operate, their providers and a suitable test environment. We discuss operational dependencies, representative test data and written permissions. Medical devices and clinical systems require a separate suitability discussion before any scope is proposed.
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.