Capability

Site Scanning

Define authorised sites, configure scan access and run on-demand or scheduled security scans.

Simplified illustrative site scanning workflow with fictional sample data

The outcome

Check public-facing systems on a repeatable cadence with clear scope and scan history.

How it helps

How Site Scanning works

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

Feature 1

Define and scan the authorised scope

Configure the site, supported scanner and any dedicated authentication before starting work.

  • Add a site
  • Configure access
  • Authorise the scan
Simplified illustrative define and scan the authorised scope workflow with fictional sample data

Feature 2

Monitor scanning over time

Review run status and compare finding totals across recurring scans.

  • Schedule scans
  • Review run history
  • Compare totals
Simplified illustrative monitor scanning over time workflow with fictional sample data

What is included

One capability, connected to the wider platform

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

Included features

  • Authorised site inventory
  • Multiple scan engines
  • Authentication configuration
  • On-demand scans
  • Recurring schedules
  • Scan status and history

Questions and answers

Questions about Site Scanning

Practical answers to common questions about managing this responsibility well.

Why does site scanning matter?

Check public-facing systems on a repeatable cadence with clear scope and scan history.

What should site scanning include?

It should cover authorised site inventory, multiple scan engines, authentication configuration, on-demand scans and recurring schedules, with enough context to support action and explain decisions.

Who should be responsible for site scanning?

Ownership should sit with the person who can make decisions and keep the information current. A specialist or governance team may provide the method, but accountability should not be left with an unnamed group.

How do you keep site scanning current?

Set review dates according to risk and reassess after relevant incidents, material change, new evidence or overdue follow-up work. Preserve the history so changes remain explainable.

What evidence should be retained for site scanning?

Keep the source information, owner, review and approval history, supporting documents and resulting actions needed to show what was considered and what happened next.

See Site Scanning in Apollo

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