Product

Vulnerability Scanning

Authorise sites, run security scans and manage the findings through to practical remediation.

Simplified illustrative scan findings workflow with fictional sample data

The outcome

Move from technical scan output to clear priorities, accountable work and evidence of improvement.

How it helps

How Vulnerability Scanning works

This product connects with the wider Apollo platform, so information can support action, evidence and reporting without being entered again.

Feature 1

Define the authorised scope

Maintain the sites that may be assessed and configure the access needed for the selected scan method.

  • Add and authorise scan sites
  • Configure supported authentication
  • Keep scope visible to administrators
Simplified illustrative define and scan the authorised scope workflow with fictional sample data

Feature 2

Run scans on a useful cadence

Start a scan when needed or schedule recurring checks so newly introduced issues are easier to identify.

  • Choose an appropriate scanner
  • Schedule recurring scans
  • Review run status and history
Simplified illustrative monitor scanning over time workflow with fictional sample data

Feature 3

Turn findings into work

Review what was discovered, focus on meaningful exposure and track remediation alongside other security priorities.

  • Filter findings by severity and status
  • Record remediation decisions
  • Connect technical work to reporting
Simplified illustrative record the remediation decision workflow with fictional sample data

What is included

One product, connected to the wider platform

Use the product you need now while keeping its records, work and evidence ready for related products across Apollo.

Included features

  • Site inventory
  • Scheduled scanning
  • Authenticated scanning
  • Finding prioritisation
  • Remediation tracking
  • Scan history

Customer proof

Vulnerability Scanning in practice

See how customers use this product as part of a broader security, governance or compliance outcome.

Questions and answers

Questions about Vulnerability Scanning

Practical answers to common questions about managing this responsibility well.

How should organisations manage internet-facing vulnerabilities?

Authorise sites, run security scans and manage the findings through to practical remediation. Move from technical scan output to clear priorities, accountable work and evidence of improvement.

What should a good process for internet-facing vulnerabilities include?

It should cover Site inventory, Scheduled scanning, Authenticated scanning, Finding prioritisation and Remediation tracking, with clear ownership, review and evidence rather than disconnected activity.

Who should be accountable for internet-facing vulnerabilities?

Ownership should sit with the person who can make decisions, allocate resources and keep the work current. A governance or specialist team may coordinate the process, but material records and actions need named accountable owners.

How often should internet-facing vulnerabilities be reviewed?

Use scheduled reviews based on risk and trigger an earlier reassessment after relevant incidents, regulatory change, audit findings or material changes to systems, suppliers or operating conditions.

What evidence should be retained for internet-facing vulnerabilities?

Retain the source information, owner, review and approval history, supporting documents and actions needed to explain what was known, what was decided and what happened next. Relevant records include site scanning, scan findings, task management and dashboards & reporting.

See Vulnerability Scanning in Apollo

Book a focused demonstration and we will show how the product fits your current responsibilities, existing information and next practical priorities.