Study guide
4.6 Endpoint Assessment Tools & Malware Removal
Cisco CCST Cybersecurity Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Introduction & Exam Strategy
1.1 About the Cisco CCST Cybersecurity Exam 1.2 Study Roadmap & Preparation Strategy
2 Chapter 2: Essential Security Principles
2.1 Information Security Principles & The CIA Triad 2.2 Confidentiality, Integrity & Availability Controls 2.3 Authentication, Authorization & Accounting (AAA) 2.4 Social Engineering & Human Vulnerabilities 2.5 Security Principles & Access Management 2.6 Encryption, Hashing, Certificates & PKI
3 Chapter 3: Basic Network Security Concepts
3.1 Network Architecture & The OSI/TCP-IP Models 3.2 Network Defense Infrastructure & Firewalls 3.3 Intrusion Detection & Prevention Systems (IDS/IPS) 3.4 Virtual Private Networks & Encryption Protocols 3.5 Network Segmentation, DMZ & Access Control Lists 3.6 Secure Network Protocols & Services
4 Chapter 4: Endpoint Security Concepts
4.1 Endpoint Protection & Host-Based Defense 4.2 Operating System Hardening & Security Baselines 4.3 Patch Management & Vulnerability Remediation 4.4 Mobile Device Management (MDM) & BYOD Security 4.5 Endpoint Detection & Response (EDR) & Compliance 4.6 Endpoint Assessment Tools & Malware Removal
5 Chapter 5: Vulnerability Assessment & Risk Management
5.1 Risk Assessment & Risk Management 5.2 Vulnerability Scanning & Penetration Testing 5.3 CVSS Scoring & Threat Intelligence 5.4 Business Continuity & Disaster Recovery
6 Chapter 6: Incident Handling & Response
6.1 NIST Incident Response Lifecycle & Frameworks 6.2 Incident Containment, Eradication, & System Recovery 6.3 Digital Forensics Fundamentals & Evidence Preservation 6.4 Post-Incident Activity & Compliance Reporting 6.5 SOC Operations, Log Triage, & Event Monitoring 6.6 Attack Attribution: Cyber Kill Chain, MITRE ATT&CK & Diamond Model
4.6 Endpoint Assessment Tools & Malware Removal
Key Takeaways Explain This Topic AI
netstat lists active connections and listening ports; on Windows netstat -ano adds the owning process ID so a suspicious port can be traced to a running executable.
nslookup queries DNS directly and can target a specific server, which is how a technician confirms whether a host has been redirected by DNS poisoning or a modified hosts file.
tcpdump captures live packets with BPF filters and requires root or CAP_NET_RAW; -n suppresses name resolution and -w writes a .pcap file for later Wireshark analysis.
The standard malware removal procedure quarantines the host first, remediates with updated definitions from a trusted boot environment, then verifies with a clean rescan before returning the system to production.
Cleaning is not always sufficient — confirmed rootkits, bootkits, or any host where the extent of compromise is unknown should be rebuilt from a known-good image rather than disinfected.
Last updated: August 2026
4.6 Endpoint Assessment Tools & Malware Removal
Quick Answer: Three built-in commands do most of the first-line diagnostic work on a suspect endpoint. netstat answers "what is this machine talking to, and which process is doing it?" nslookup answers "is this machine resolving names correctly, or has DNS been tampered with?" tcpdump answers "what is actually on the wire?" Once a compromise is confirmed, the malware removal workflow runs quarantine → scan with updated definitions → review scan logs → remediate → verify → restore , with a rebuild-instead-of-clean decision point for rootkits and unknown-extent compromises.
Blueprint sub-topic 3.2 names exactly three tools — netstat , nslookup , and tcpdump — and sub-topic 3.6 covers malware removal. Both are hands-on tasks a Tier 1 technician performs, and both are best learned by running the commands rather than reading about them. Everything below can be practised on your own machine.
1. netstat — Active Connections and Listening Ports
netstat (network statistics) reports the endpoint's TCP and UDP connections, listening sockets, and routing information. It is the fastest way to spot a host beaconing to an unexpected destination or a service listening on a port nobody authorised.
Key switches
Command Platform What it shows
netstat -ano Windows A ll connections and listening ports, n umeric addresses (no DNS lookups), plus the o wning process ID. The single most useful form.
- netstat -anob Windows (admin) As above, plus the b inary/executable name responsible for each connection
- netstat -r Both Routing table
netstat -tunap Linux t cp, u dp, n umeric, a ll sockets, p rocess owning each (needs root to see other users' processes)
- netstat -tulnp Linux Listening sockets only — the fast "what is exposed on this host?" check
- ss -tunap Linux Modern replacement for netstat ; same information, faster on busy hosts
- Reading the output
- A typical Windows line looks like: Proto Local Address Foreign Address State PID
- TCP 192.168.1.42:51544 203.0.113.77:443 ESTABLISHED 4812
- TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING 1044
Connection states worth knowing:
State Meaning Security relevance
LISTENING A service is waiting for inbound connections on this port An unexpected listener is a potential backdoor or unauthorised service
ESTABLISHED An active two-way session Where you look for beaconing to command-and-control infrastructure
SYN_SENT This host sent a connection request and is awaiting a reply Many rapid SYN_SENT entries to sequential addresses indicate the host is scanning — a strong sign of worm activity or a compromised machine
TIME_WAIT Connection closed, socket held briefly before release Normal; large numbers are usually a performance artefact, not an attack
CLOSE_WAIT Remote end closed; local application has not Usually an application bug rather than a security event
Tracing a suspicious connection to its process
This is the workflow the exam expects you to be able to describe:
netstat -ano and identify the suspicious foreign address and its PID .
Match the PID to a process: tasklist /FI "PID eq 4812" on Windows, or ps -p 4812 -o pid,user,cmd on Linux.
Inspect the executable's path and digital signature. A process named svchost.exe running from C:\Users\Public\ rather than C:\Windows\System32\ is a classic masquerading technique.
Record the finding, then escalate or contain — do not simply kill the process, because doing so destroys volatile evidence and tips off an active intruder (see Section 6.3 on order of volatility).
Baseline first. netstat output is only meaningful against a known-good baseline. Run it on a healthy machine of the same build so you know what "normal" looks like before you have to judge an incident under pressure.
2. nslookup — Querying DNS Directly
nslookup (name server lookup) queries DNS records directly rather than relying on whatever the operating system resolver has cached. It is the tool for confirming whether name resolution itself has been tampered with — the mechanism behind pharming, DNS cache poisoning, and hosts-file hijacking.
Common usage
- Command Purpose
- nslookup example.com Standard forward lookup using the system's configured DNS server
- nslookup example.com 8.8.8.8 Query a specific DNS server, bypassing the local one entirely
- nslookup 203.0.113.25 Reverse lookup — which name maps to this address
- nslookup -type=MX example.com Mail exchanger records, used when investigating spoofed or misrouted email
- nslookup -type=NS example.com Authoritative name servers for the zone
- nslookup -type=TXT example.com TXT records, where SPF and DMARC policies live
- nslookup -type=SOA example.com Start of authority — zone serial and administrative contact
- The diagnostic that matters
Compare the answer from the local DNS server against the answer from a known-good external server: nslookup intranet.example.com # what this host is being told
nslookup intranet.example.com 1.1.1.1 # what a trusted resolver says
If the two disagree, something between the host and the authoritative zone is lying. Investigate in this order: the local hosts file ( C:\Windows\System32\drivers\etc\hosts or /etc/hosts ), the DHCP-assigned DNS server setting (a rogue DHCP server can hand out a malicious resolver), the local resolver cache ( ipconfig /flushdns on Windows), and then the DNS server itself.
A precision point: nslookup bypasses the hosts file, because it queries DNS directly rather than going through the operating system's resolution order. A name that resolves correctly under nslookup but still sends the browser to the wrong site is a strong indicator that the hosts file has been modified — a technique malware uses to redirect antivirus update domains to nowhere.
Two related notes: dig provides more detailed output and is preferred on Linux, and DNS query logs are a high-value SIEM source because most malware resolves a domain before it beacons.
3. tcpdump — Capturing What Is Actually on the Wire
tcpdump is a command-line packet capture tool. Where netstat tells you a connection exists, tcpdump shows you the traffic itself. It uses Berkeley Packet Filter (BPF) syntax — the same filter language Wireshark uses for capture filters.
Core switches
- Switch Effect
- i eth0 / -i any Choose the capture interface; any captures across all of them
- n Do not resolve hostnames (faster, and avoids generating your own DNS traffic)
- nn Do not resolve hostnames or port service names
- c 100 Stop after 100 packets
- w capture.pcap Write raw packets to a file for later analysis in Wireshark
- r capture.pcap Read a previously saved capture
- A / -X Print payload as ASCII / as hex and ASCII — how you demonstrate that a protocol is cleartext
- v , -vv Increasing verbosity
- Filter expressions
- Filter Captures
- host 203.0.113.77 All traffic to or from that address
- src host 10.1.1.5 Only traffic originating from that host
- port 443 Traffic on port 443 in either direction
- tcp port 80 TCP web traffic only
- udp port 53 DNS queries and responses
- icmp Ping and other ICMP traffic
- net 10.20.30.0/24 An entire subnet
- host 10.1.1.5 and port 445 Combined conditions with and , or , not
Worked example — investigating a host suspected of beaconing: sudo tcpdump -i any -nn host 203.0.113.77 -w beacon.pcap
This records every packet between the endpoint and the suspect address, with no name resolution, into a file you can hand to a senior analyst or open in Wireshark.
Operational cautions
tcpdump requires root or the CAP_NET_RAW capability , because it puts the interface into promiscuous mode. An unprivileged user cannot run it.
Captured traffic frequently contains sensitive data — credentials on cleartext protocols, personal information, session tokens. A .pcap file is evidence and must be handled with the same care as any other artefact (Section 6.3).
Capture where the traffic actually is. On a switched network a host sees only its own traffic unless you configure a SPAN/mirror port or insert a network TAP (Section 3.3).
Filter at capture time. Unfiltered captures on a busy link fill disks in minutes and are painful to analyse.
4. The Malware Removal Workflow
Blueprint sub-topic 3.6 covers scanning systems, reviewing scan logs, and malware remediation. The industry-standard procedure below is what an exam scenario expects you to follow in order — and the ordering itself is what is usually tested.
Step 1 — Investigate and verify the symptoms
Confirm you actually have malware rather than a hardware fault, a failing disk, or a misbehaving update. Genuine indicators: unexpected outbound connections ( netstat ), new autostart entries or scheduled tasks, disabled antivirus or Windows Update, browser redirection, unexplained CPU or disk activity, new local accounts, or files with a ransom note extension.
Step 2 — Quarantine the system
Disconnect the host from the network before anything else — pull the cable, disable the wireless adapter, or have NAC move it to an isolation VLAN. This stops lateral spread and cuts the command-and-control channel. Leave the machine powered on if an investigation is likely, since powering off destroys memory-resident evidence.
Step 3 — Disable System Restore (Windows) before cleaning
Malware routinely hides copies of itself inside System Restore points, so a cleaned machine reinfects itself the first time a user rolls back. Disable System Restore, remove the existing restore points, clean the system, and create a fresh restore point afterwards.
Step 4 — Update definitions and scan from a trusted environment
Update the antimalware engine and definitions first , from clean media or a controlled network segment. Scanning with three-month-old signatures is the most common reason a scan comes back clean on an obviously infected machine.
Scan from an environment the malware does not control. Advanced malware hides from a scanner running under the operating system it has already subverted. Use Safe Mode , a Windows Recovery / pre-installation environment , an offline scan such as Microsoft Defender Offline, or a bootable rescue medium.
Run a full scan, not a quick scan. Quick scans check only common locations.
Step 5 — Review the scan logs
The blueprint calls out reviewing scan logs specifically, because the log — not the summary dialog — is where the useful information is:
What was found, and where. A detection in %TEMP% is routine; one in C:\Windows\System32\ or in a boot record is serious.
What action was taken. Quarantined , removed , and access denied mean different things. "Access denied" or "removal failed" means the file is still there and probably in use — treat the host as still infected.
How many detections and of what family. Multiple unrelated families usually indicate the host was exposed for a long time, or that a dropper has been pulling down additional payloads.
Whether items reappear after reboot. A detection that returns after a clean scan indicates a persistence mechanism the scanner did not remove.
Step 6 — Remediate
Remove or quarantine detected files, then clear the persistence the scanner may have missed: unwanted registry Run keys, scheduled tasks, services, startup folder entries, browser extensions, and unexpected local accounts. Reset credentials that were used on the machine while it was compromised, and patch the vulnerability that allowed entry — otherwise you have cleaned the symptom and left the door open.
Step 7 — Verify, then restore normal operations
Rescan with updated definitions and confirm a clean result. Re-enable System Restore and create a new restore point. Confirm real-time protection, the host firewall, and automatic updates are all back on — malware commonly disables them. Reconnect to the network, then monitor the host for anomalous connections for the following days.
Step 8 — Educate the user
If the entry point was a phishing email, a side-loaded application, or a USB drive, closing that behavioural gap prevents the repeat you would otherwise see within weeks.
5. When to Rebuild Instead of Clean
Cleaning is the default, but it is not always adequate. Rebuild from a known-good image when any of the following is true:
A rootkit or bootkit is confirmed. Kernel- or firmware-level code can hide from and subvert the very tools you are using to check the machine.
The extent of compromise cannot be established — you can prove something got in but cannot prove what it did.
Removal repeatedly fails or detections reappear after each clean scan.
The host held administrative credentials or sensitive data , so the cost of being wrong is high.
Ransomware encrypted the system. Restore data from clean backups; do not attempt to clean and reuse the running installation.
The rebuild sequence is: preserve any evidence needed first, image or wipe the disk, reinstall from trusted media or a golden image, patch fully before returning the machine to the production network, restore data from a backup taken before the infection date, and reset every credential the host touched. Section 6.2 covers the containment, eradication, and recovery decision in full.