Network / Infrastructure VAPT

1 Assessment Details

Mandatory

Organization name *

Technical contact for scope clarifications *

Target start date *

Number of locations / sites in scope *

Services required *

Vulnerability Assessment Penetration Testing Retest only

2 Scope Type and Testing Approach

Mandatory

Assessment type *

External infrastructureInternet-facing assets, tested from outside the network Internal infrastructureTested from inside the approved network

Testing approach * Must answer

Grey Box — recommended White Box Black Box Not sure

Grey Box shares limited information plus credentials. White Box adds full device configurations and network diagrams. Black Box shares nothing, so part of the effort goes into discovery rather than testing.

Assessment mode *

Unauthenticated only Authenticated Both

Internal testing location *

How frequently should the assessment be carried out? *

Single-time engagement Quarterly assessment Continuous assessment

Please note: assessment frequency is not included in the timeline estimate in section 7. The estimate covers a single assessment cycle only. Frequency, and the schedule for repeat cycles, is agreed while finalising the scope.

A single-time engagement covers one assessment cycle together with its retests.

Will network diagrams and asset inventory be shared?

Yes Partially No

Will device configurations be shared for review?

A full firewall rule-base audit is only possible when configuration access is provided.

3 Asset Inventory and Counts

Drives effort

Enter approximate counts — leave blank or zero where not applicable. These counts feed the timeline estimate in section 7.

Asset counts *

Perimeter and hosts

Public IP

Internal IP

Windows laptops / endpoints

Linux / Unix endpoints

Printers

IP Cameras / NVR

Servers and appliances

Servers

VMs

Application servers

DB servers

Network devices

Firewalls

Routers

Managed switches

IP ranges, hostnames and asset groups in scope *

Only addresses and hosts listed in the approved scope are tested.

Operating systems in scope *

Any end-of-life or unsupported systems in scope, and can they tolerate scanning?

Endpoint testing approach

Virtualization platform

Environment in scope *

Production Environment UAT / Test Discussed during Scope Call

Active Directory in use Adds 4 days

Active Directory is in use

Tick this if the network uses Active Directory — the system most Windows networks use to manage staff logins and permissions. It is assessed as its own piece of work, which adds 4 days to the estimate.

4 Data Sensitivity and Standards

Drives severity ratings

What kind of data do the in-scope systems handle? *

This decides how serious a finding is, so an approximate answer is fine.

Standards and compliance requirements to be referenced

5 How We Test

Nothing here needs an answer — it is what you are buying.

How the assessment runs

We confirm exactly which addresses and systems are in scope, then map what is actually reachable on them. Automated scanning covers the whole estate quickly, and every result is checked by hand — scanners over-report badly on infrastructure and nothing goes into your report unverified. We then test manually where it matters: exposed services, weak or default credentials, missing patches and configuration mistakes. Each finding is reproduced, evidenced and rated, and retested once your team has fixed it.

What we look for

Systems reachable from outside that should not be. Services running with default or weak passwords. Missing patches on operating systems and network devices. Firewall and network rules that allow more than intended. Insecure remote access. Weak encryption. And whether the network is genuinely separated, or whether reaching one machine means reaching everything.

What we will not do

This is a controlled assessment, not a red-team exercise. No phishing, no social engineering, no physical security testing, no denial-of-service, and nothing destructive. We do only the minimum needed to prove a finding is real.

6 Vulnerability Risk Classification

Severity	Description
Critical	May result in complete system compromise, remote code execution, administrative access, widespread infrastructure impact or significant sensitive-data exposure.
High	May result in unauthorized access, privilege escalation, system compromise, significant data exposure or access to additional approved systems.
Medium	May affect infrastructure security under specific conditions, or may require authentication, limited privileges, internal access or user interaction.
Low	Limited direct impact; remediated as part of infrastructure-hardening and security-improvement activities.
Informational	Configuration observation or hardening recommendation without direct exploitability.

After retesting each finding is marked Closed, Open, Partially Fixed, Risk Accepted or Not Retested.

7 Timeline Estimate

Calculated from the SysTools infrastructure effort model. Asset counts from section 3 are carried over automatically; the OS image, hypervisor and WLAN counts are entered by the assessment team.

Endpoints

Unique OS images

Windows endpoint hosts

Linux / Unix endpoint hosts

Printers

IP Cameras / NVR

Servers

General servers

Hypervisor hosts

VMs

Application servers

Database servers

Network devices

Firewalls

Routers

Managed switches

WLAN controllers with APs

Retest

Active Directory1 = in use

Number of retests

One retest is included as standard. Increase this only if additional retest cycles are required.

Estimated duration 0 working days

Testing0

Retest0

Subject to final scope review, access availability and resource confirmation. The final timeline is confirmed after the complete scope has been reviewed and understood.

Save and Export Response

Responses are stored in this browser until exported or cleared.