Infrastructure
Network Vulnerability Assessment & Penetration Testing
Understand what is exposed, what is reachable and where segmentation holds.
Explore scopeInfrastructure / 7 of 32
Infrastructure & Firewall Configuration Review.
Check the settings behind the controls. Turn exceptions into an achievable hardening plan.
Configuration reviews are useful when a system is operational but its baseline has grown inconsistent. The review compares selected servers, databases, web servers and network devices with an agreed baseline. Exceptions are assessed in their business context rather than treated as identical failures.
A clear scope makes the differenceWhat the work
What the work
can cover.
Explore the areas that can shape this engagement. Final coverage follows your systems, priorities and access.
01 / Inside the scope
Operating system baseline
Review security settings, unnecessary services and local access on selected servers. Record benchmark applicability and operational exceptions.
02 / Inside the scope
Firewall rules
Assess rule intent, broad access, management paths and review ownership. Compare the rule set with the network’s intended trust boundaries.
03 / Inside the scope
Web hosting
Review selected web server and hosting settings, administrative exposure and transport configuration. Connect findings to the deployed application stack.
04 / Inside the scope
Database configuration
Review authentication, privileges, network access and relevant logging settings using supplied configurations or approved review access.
05 / Inside the scope
Administrative access
Examine remote management, privileged account use and access review evidence. Identify avoidable exposure in day-to-day administration.
06 / Inside the scope
Hardening exceptions
Separate recommended changes from operationally justified exceptions. Record compensating controls and the evidence needed to revisit the decision.
01 / 06
What your team receivesFrom evidence
From evidence
to owned action.
A useful result explains coverage, impact and next steps. The agreed proposal makes the deliverables clear.
- 01
Baseline and configuration coverage matrix
- 02
Observed gaps with evidence
- 03
Hardening backlog and exception register
- 04
Change verification checklist
Before the assessmentA useful
A useful
starting point.
These inputs establish the effort, coverage, intended use and timing.
- Product versions and system inventory
- Configuration exports or review access
- Existing baselines and business exceptions
Common questions
What defines the scope?
The systems, business objective and evidence you need determine the scope. The assets, access, deliverables and timetable are agreed before work begins.
What will our team receive?
A clear account of coverage, evidence-backed observations and prioritised next actions. The proposal sets out the exact deliverables and any follow-up review.
Can this fit an upcoming release or audit?
Share the milestone and the systems involved. The assessment can be shaped around that decision once technical fit and availability are confirmed.
Connected priorities
You may also need.
Infrastructure
Cloud Security Configuration Review
Make identity, exposure and configuration risks visible across your cloud estate.
Explore scopeInfrastructure
OSINT & External Attack Surface Review
See the public footprint your organisation presents before choosing what to test.
Explore scope