Study guide
Common Threats and Safe User Practices
CCST Networking Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Orientation, Official Sources, and Exam Strategy
Official Exam Profile and Source Hierarchy Registration, Delivery, Attempts, and Results Using the Six Official Topic Areas Building a Practical Study Plan Exam Strategy Without Unsupported Shortcuts Ethical Preparation and Path Forward
2 Network Standards, Models, and Common Protocols
Network Building Blocks OSI and TCP/IP Models Frames, Packets, Segments, and Data Flow Network Types and Scope Cloud, On-Premises, Protocols, and Ports Bandwidth, Throughput, Latency, and Jitter
3 Chapter 3: IPv4, IPv6 Addressing, and Subnet Formats
3.1 Public, Private, and Local Addressing 3.2 IPv4 Dotted Decimal and Binary Basics 3.3 Subnet Masks, CIDR, and Prefix Lengths 3.4 Subnet Logic, Host Ranges, and Gateways 3.5 IPv6 Address and Prefix Formats 3.6 MAC vs IP in Addressing Troubleshooting
4 Endpoints, Media, Cabling, and Client Connectivity
Endpoint Devices and Network Roles Network Interface Cards and Link Status Copper, Fiber, Coax, and Connector Basics Wired, Wi-Fi, and Cellular Access Methods Interference, Signal Quality, and Physical Reliability Client Connectivity Checks by Operating System
5 Infrastructure Devices, Ports, and Physical Installation
Infrastructure Device Roles Ports, Connectors, and Device Identification Cisco Device LEDs and Status Checks Network Diagrams and Cabling Instructions Power over Ethernet and Powered Devices Racks, Patch Panels, and Installation Basics
6 Switching, Routing, and Network Services
Basic Switching and MAC Learning VLANs and Local Boundaries Routing, Default Gateway, and ARP DNS, DHCP, and NAT Services Transport-Layer Services Small Network Traffic Flow
7 Troubleshooting Methodology, Ticketing, and Documentation
Help Desk Intake and Information Gathering Scope, Impact, and Prioritization Reproduce, Isolate, and Escalate Ticket Quality and Operational Documentation User Communication and Change History Physical, Data Link, and Network Layer Triage
8 Diagnostic Commands, Packet Capture, and Device Data
Command-Line Triage and Ping Path and Client Configuration Commands DNS and Socket Diagnostics Wireshark Capture and Save Device Access and Data Collection Basic Cisco Show Commands
9 Security, Firewalls, Wireless, and Safe Defaults
Firewall Filtering and Traffic Policy Least Privilege, AAA, Passwords, and MFA Wireless Security, WPA2, WPA3, and WPAx Guest Networks, Segmentation, and Shared Devices Common Threats and Safe User Practices Secure Home Router Baseline
10 Integrated Small Network Build and Repair Labs
Lab 1: Build a Basic Office LAN Lab 2: Repair No Internet After an Office Move Lab 3: Wireless Clients Cannot Reach Local Resources Lab 4: DHCP, DNS, and Default Gateway Symptoms Lab 5: Switch, Router, and Service Boundaries Lab 6: Escalation, Documentation, and Handoff
11 CCST to CCNA Career Path and Operational Readiness
Entry-Level Networking Roles and Expectations CCST vs CCNA and the Cisco Roadmap NetAcad 70-Hour Path and Study Plan Lab Habits for Real Operational Readiness Ethical Preparation, Portfolio, and Logbook Exam Scheduling Calendar and Readiness Check
12 Final Review, Exam Day, and Remediation Plan
Final Review Map to Official Objectives 50-Minute Exam Day Timing Unsupported Facts and Ethical Preparation Retake Planning Before the First Attempt Post-Fail Remediation Workflow Post-Pass Next Steps and Validity
Common Threats and Safe User Practices
Key Takeaways Explain This Topic AI
Most incidents are ordinary: phishing, malware, credential reuse, rogue/evil-twin APs, unpatched devices, exposed services.
Phishing and social engineering target people; verify unusual requests through a separate trusted channel.
Malware symptoms justify triage, not improvised cleanup tools downloaded from the web.
Rogue APs and evil twins exploit trust in SSID names; connect only to known, approved networks.
On a suspected incident: collect who/what/when/where/how, preserve evidence, and escalate — do not wipe or reset on your own.
Last updated: June 2026
Recognizing Everyday Security Risks
Foundational security means knowing the threats that show up in normal support work. The exam favors realistic scenarios over jargon.
Threat catalog
Threat What it is Telltale sign
Phishing Fake email/text/login page that steals credentials or money Urgent tone, mismatched sender domain, look-alike URL
Spear phishing / BEC Targeted message impersonating an exec or vendor "Buy gift cards now," changed bank details
Malware Harmful software (virus, worm, trojan, spyware, ransomware ) Pop-ups, disabled AV, encrypted files, high CPU
- Credential stuffing Reusing leaked passwords against other sites Logins from new locations after a breach
- Brute force Automated guessing Many failed logins, account lockouts
- Social engineering Manipulating people to bypass controls "This is the help desk, read me your code"
- Rogue AP Unauthorized access point on/near the network Unexpected SSID, MAC anomalies
- Evil twin Fake AP imitating a trusted SSID Two identical SSIDs, no captive portal
Phishing is the most common entry point. Treat reports of suspicious messages seriously, do not click the link from the user's session to "investigate," and follow the reporting process. Social engineering bypasses technical controls entirely; the defense is to verify unusual requests — passwords, MFA codes, payment changes, remote access, urgent exceptions — through a separate trusted channel, never by replying to the suspicious message.
Malware response
Symptoms (pop-ups, disabled security tools, unknown extensions, renamed/encrypted files, strange network traffic) justify careful triage but are not proof alone. Do not download a random "cleaner" from a web search — that is often how more malware arrives. Preserve the device state if policy requires it, disconnect from the network only if instructed, and escalate to security/IT. Ransomware specifically encrypts files for extortion, which is why reliable offline or versioned backups are a genuine security control.
Wireless-specific threats
A rogue access point is an unauthorized AP connected to or near the network; an evil twin imitates a legitimate SSID to lure users onto an attacker's AP, where traffic can be intercepted. Defenses: define approved SSIDs, train users not to join look-alike names, and treat open public Wi-Fi as untrusted. A VPN , HTTPS, and avoiding sensitive admin work on public Wi-Fi reduce exposure, but the strongest control is connecting only to known, approved networks.
Unpatched devices and exposed services
A router, camera, NAS, printer, or server running old firmware may carry known vulnerabilities. Port forwarding to remote desktop (RDP) or a camera web page exposes weak services straight to the Internet, and default credentials make it far worse. Basic but powerful controls: apply vendor updates, disable unused services, restrict management access, and replace unsupported (end-of-life) hardware.
Incident posture (what NOT to do)
Collect who, what, when, where, how : affected user, device name, IP, network, safe screenshot or error text, suspicious sender, the URL shown, time of event, and actions already taken. Then:
Do not delete emails, wipe devices, or reset accounts unless the procedure says so — you may destroy evidence.
Do not declare a system "clean" after a quick look.
Do not put the user's password in the ticket.
Escalate when credentials may be exposed, sensitive data is involved, malware is suspected, unauthorized access is possible, or a device's management interface may be compromised.
Spotting phishing in a real message
The exam likes concrete tells. A phishing email often shows a display name that does not match the actual sender domain ("IT Help Desk" from a random free-mail address), a look-alike or shortened URL that does not point to the real company domain when you hover, urgency or fear ("your account will be closed in 24 hours"), unexpected attachments , and requests for credentials, codes, or payment changes . Hovering over a link to read its true destination — without clicking — is a safe inspection step you can teach users. The reply address is also revealing: legitimate password resets never ask you to send the password back.
The difference between a threat, a vulnerability, and an exploit
These three terms appear in security objectives and are easy to confuse. A vulnerability is a weakness, such as an unpatched router with a known flaw or a default password still in place. A threat is something that could act against that weakness, such as a botnet scanning the Internet for that exact router model. An exploit is the actual technique or code that takes advantage of the vulnerability.
Risk rises when a real threat can reach an unpatched vulnerability with a working exploit — which is exactly why patching, disabling unused services, and changing defaults matter: they remove the vulnerability so the threat has nothing to act on.
Common traps
"Helpfully" approving an MFA prompt to stop the noise — that hands an attacker the login.
Investigating a phishing link from the victim's own session.
Running an unknown cleanup tool on a suspected-malware machine.
Confusing a vulnerability (the weakness) with the threat (the actor) or the exploit (the technique).
Declaring a device "clean" after a surface check rather than escalating to the people and tools that can confirm it.