How this simulation works
- Read the scenario, then open each exhibit tab. The exhibits hold everything you need to answer the tasks.
- Complete every task, then select Submit answers. Scoring gives partial credit where a task has more than one part, the same way CompTIA can award partial credit on PBQs.
- After you submit, each task shows the correct answer and an explanation. Select Reset simulation to clear your work and try again.
- On the real CySA+ exam, PBQs are simulations. You can flag a simulation, skip it, and return to it after you finish the multiple-choice questions, and each simulation has a reset button.
CS0-004 objectives practiced:
- 1.1 System and network architecture concepts
- 1.2 Analyze indicators of potential malicious activity
- 2.2 Analyze output from vulnerability assessment tools
The organization, people, and events in this simulation are fictional. Public IP addresses come from the RFC 5737 documentation ranges and domain names use the reserved .example top-level domain, so none of them route anywhere. This is a practice activity and is not graded.
Pacing timer
Scenario
Tamberlin Health Network hosts two public servers in its DMZ: a web server and a mail relay. An authorized external scanning service ran Nmap against both servers from the internet. Compare the results to the approved service baseline, then configure the DMZ inbound firewall rule set.
Exhibits
Approved DMZ service baseline
- web01 (198.51.100.5): HTTPS on 443/tcp for everyone. HTTP on 80/tcp only so the server can redirect visitors to HTTPS.
- mail01 (198.51.100.6): SMTP on 25/tcp for inbound mail delivery.
- SSH on 22/tcp to DMZ servers is approved only from the internal management network 10.20.9.0/24. It must never be reachable from the internet.
- Remote Desktop (3389/tcp) and Telnet (23/tcp) are prohibited on all DMZ servers.
External Nmap service scan results (run from the internet)
Nmap scan report for web01.tamberlin.example (198.51.100.5) Host is up (0.012s latency). Not shown: 996 filtered tcp ports (no-response) PORT STATE SERVICE VERSION 22/tcp open ssh OpenSSH 9.6p1 (protocol 2.0) 80/tcp open http nginx 1.24.0 443/tcp open ssl/http nginx 1.24.0 3389/tcp open ms-wbt-server Microsoft Terminal Services Nmap scan report for mail01.tamberlin.example (198.51.100.6) Host is up (0.011s latency). Not shown: 997 filtered tcp ports (no-response) PORT STATE SERVICE VERSION 23/tcp open telnet Linux telnetd 25/tcp open smtp Postfix smtpd 8080/tcp filtered http-proxy Nmap done: 2 IP addresses (2 hosts up) scanned in 31.42 seconds
DMZ inbound firewall requirements
- Rules are processed from top to bottom, and the first rule that matches a connection is applied.
- Anyone may reach web01 on 443/tcp. HTTP on 80/tcp to web01 is permitted for the HTTPS redirect.
- Anyone may deliver mail to mail01 on 25/tcp.
- SSH on 22/tcp to DMZ servers is permitted only from 10.20.9.0/24.
- Remote Desktop and Telnet are never permitted into the DMZ.
- Anything not explicitly permitted is denied.