WHAT WE LOOK AT
Exposure needs context.
An open service or missing patch matters differently depending on what sits behind it. We examine reachable services, configuration and access boundaries to explain the likely impact on your environment.
External exposure
Internet-facing services and the information available to an unauthenticated visitor.
Internal access
Reachable systems and access boundaries from an agreed internal starting point.
Service configuration
Risky settings, unnecessary exposure and software weaknesses within scope.
Paths to compromise
How findings can combine to affect accounts, systems or sensitive information.
BEFORE WE BEGIN
Get the scope right.
Provide the IP ranges, hostnames, relevant cloud services and the business purpose of the environment. We agree ownership, third-party permissions, exclusions, testing windows and any checks that could affect availability.
Internal and external assessments start from different positions. The right scope depends on whether you need to understand your public exposure, your internal boundaries, or both.
WHAT YOU RECEIVE
Findings your team can work with.
A prioritised report explaining the findings, evidence, business impact and recommended remediation.
We can discuss findings with your developers or IT team while they make changes. Retesting checks whether the reported issues have been resolved; coverage and timing are agreed as part of the engagement.
- Evidence and reproduction steps
- Risk ratings with business context
- Remediation guidance and agreed retesting
COMMON QUESTIONS
A few things to know.
Can we test only our external perimeter?
Yes. An external assessment can focus on an agreed list of public systems. Internal testing is a separate scope or an additional part of the engagement.
How do you plan around production services?
We agree the testing window, operational contacts, exclusions and limits before starting. Tests that could affect availability need specific agreement; no assessment can promise zero operational risk.
