Checking Guest and Staff Network Access is a practical Nmap project for learners who want to turn scan results into a careful network-opening review. Observe the same server from guest and staff network positions, confirm the public business on both sides, and decide whether each source-service relationship matches its agreement.
One Guided Lab develops the workflow from normal public responses to separate scans and a complete six-row review. One independent Challenge changes the addresses, ports and access relationships, including a visitor service that staff should not reach. Each unit provides its own prepared environment.
What You Will Learn
- Keep a scan observation tied to its real source, target, protocol and complete port scope.
- Read open, closed and filtered results without inventing an underlying cause.
- Use selected HTTP evidence to identify responsive candidates and retain complete Nmap XML.
- Distinguish unexpected access from unavailable required services using an explicit agreement.
- Deliver a complete access review while preserving clients, original services, data and network configuration.
Who This Course Is For
This course is for Nmap beginners and junior network or support learners who want a focused, complete audit task.
Prerequisites: Basic terminal input, paths and switching lab tabs. Finding the Live Workshop Service is recommended preparation, but the required options and shell syntax are explained. No programming or firewall administration is required.
Learning environment: A prepared Ubuntu training VM with Nmap, real HTTP services, and Guest Scanner and Staff Scanner terminals. Their network namespaces provide distinct source addresses and routes on one VM; they share files and are not separate VMs. All records are synthetic. Use only the stated target and ports.
Frequently Asked Questions
Do I need to build the network or install tools?
No. Each unit provides the tools, services and two prepared scanner roles.
Should I fix access problems as I find them?
No. This task delivers an accurate review to the owner. Preserve the original scene, including problems that prevent opening.
Does a closed or filtered port always mean success?
No. A required service that cannot be reached is a finding. Interpret each observation against that source's allow or block relationship; it does not prove the exact root cause or every network path.
What makes the Challenge independent?
The addresses, ports and policy relationships change, while the tools and review format stay familiar. A clear scope and separate complete solution support independent practice.
