Security analysts reviewing vulnerability findings
Vulnerability management

Vulnerability assessments

An assessment should establish where you have exposure and what to do about it. It is not simply an unauthenticated scan followed by a PDF. Scope, access and interpretation make the difference between useful evidence and a noisy list.

Agree what is in scope and what is not

Use the asset inventory, business services and known external addresses to define the assessment. Include remote devices, cloud workloads and supplier-managed systems where you have authorisation. Confirm that someone can explain what remains outside the assessment and why.

Production and operational technology need particular care. Scanning approval, safe profiles, maintenance arrangements and a route to stop the work should be agreed before activity begins. A general claim that every scan is non-disruptive is not appropriate for a mixed estate.

Check whether the scanner can actually see the system

Authenticated assessment can reveal installed software and local configuration that an external scan cannot. Confirm successful authentication and sufficient permissions rather than assuming stored credentials worked. Cloud agents and network scanners provide different views and may both be needed.

Document unreachable hosts, unsupported systems and incomplete results. Do not silently exclude them from the report denominator. The coverage gaps can represent a more significant issue than the highest-scoring detection on a well-managed device.

Turn detections into a realistic fix order

Validate important findings against system context and vendor guidance. Consider exposure, known exploitation, business importance and available mitigations alongside technical severity. A scanner detection is evidence to investigate, not an automatic demonstration of exploitability.

Group remediation around owners and changes: application update, operating system update, configuration hardening or retirement. State where further testing is needed and distinguish a recommended fix from an approved change. The application owner must be involved when compatibility is uncertain.

Leave a baseline that can be repeated

The deliverable should include scope, coverage limitations, prioritised findings, owners where agreed and the method for verifying remediation. A follow-up assessment can compare the same estate and explain additions, removals and changed access.

A one-off assessment is useful for establishing the starting position, but it cannot describe the state months later. Link it to managed scanning or continuous vulnerability management if the estate changes regularly. Penetration testing remains separate where you need adversarial validation of attack paths.

Questions

Frequently asked questions

What access is required?

That depends on the assessment. Authenticated internal checks may need dedicated restricted credentials or agents; external assessment needs an authorised scope. Agree permissions and credential handling before starting.

Will the assessment include exploitation?

Not by default. Vulnerability assessment identifies and interprets weaknesses. Any intrusive validation or penetration testing requires explicit scope, authorisation and safety arrangements.

What should we do with the report?

Assign owners and changes, record exceptions and verify important fixes. If nobody is accountable for acting on it, another assessment will usually report the same unresolved issues.

Work through your vulnerability backlog with us.

Bring the coverage report as well as the vulnerability totals. We will discuss ownership, patch constraints and what would make remediation workable in your environment.

Book a consultation