Study guide
Least Privilege, AAA, Passwords, and MFA
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
Least Privilege, AAA, Passwords, and MFA
Key Takeaways Explain This Topic AI
Least privilege grants a user, service, or device only the access its role requires.
AAA = Authentication (who are you?), Authorization (what may you do?), Accounting (what did you do?).
Strong, unique, long passphrases beat forced complexity that drives reuse and sticky notes.
MFA combines factors: something you know, something you have, something you are.
Technicians never collect passwords in tickets/chat; they use approved reset and identity-verification workflows.
Last updated: June 2026
Identity and Access Basics
Security is not only blocking packets; it is deciding who may use systems, what they may do, and how activity is recorded. The principle of least privilege is the rule behind most access decisions: give a person, service, or device only the permission needed for the task. A receptionist needs the scheduling app, not firewall administration. A printer needs print jobs, not file-share access. A guest phone needs Internet, not router management.
AAA in one table
AAA stands for Authentication, Authorization, and Accounting .
- Function Question it answers Examples
- Authentication Who are you? Password, certificate, token, biometric, MFA
- Authorization What are you allowed to do? Read a folder, change a switch config, join a restricted SSID
- Accounting What did you do? Sign-in logs, config-change history, session records
A user can authenticate successfully yet still be denied an action — that denial is authorization, not a login failure. In larger networks a RADIUS server (Remote Authentication Dial-In User Service) provides centralized AAA for VPN, switch admin, and enterprise Wi-Fi, so credentials live in one directory instead of being copied onto every device. This matters on the exam because it explains how enterprise Wi-Fi can hand each employee a personal login rather than one shared key, and how an administrator can revoke a single person's access instantly without touching any access point.
Password hygiene
A strong passphrase is long, unique, and hard to guess. Length matters more than forced symbol rules that push users toward Password1! patterns or sticky notes; modern guidance (for example NIST SP 800-63B) favors long passphrases and screening against breached-password lists over arbitrary 90-day rotation. Reuse is the central danger: one breached site exposes every account sharing that password. Default credentials on routers, access points, cameras, printers, and NAS units must be changed before the device is trusted on a network.
Technician rules of conduct:
Never ask a user to tell or paste their password — use the approved reset workflow.
Never store passwords in tickets, screenshots, chat, or plain-text notes.
Verify identity before a reset per organizational procedure.
If a device ships with a vendor default login, document that it must be changed during installation.
For repeated lockouts, collect times and affected services instead of clearing the symptom over and over.
MFA — factors and abuse
Multi-factor authentication (MFA) requires at least two of three factor types:
Something you know — password or PIN.
Something you have — authenticator-app approval, one-time code, or a hardware FIDO2/U2F security key.
Something you are — fingerprint or face scan.
MFA matters because a stolen password alone may not be enough to sign in. But it is not magic. MFA fatigue (push bombing) floods a user with prompts hoping they tap approve . Train users to reject unexpected prompts and to report repeated unexplained requests immediately — these often mean an attacker already has the password. Phishing-resistant methods (hardware keys, passkeys) defeat fake login pages that defeat one-time codes.
Least privilege for devices
Least privilege also governs infrastructure. Management interfaces should be reachable only from trusted networks or a VPN, never from guest Wi-Fi or the public Internet. Administrative accounts must be separate from everyday accounts, departed-staff accounts disabled promptly, and service accounts kept narrow with documented owners. You may not own the identity system, but you should ask the right questions: who needs access, what exact access, for how long , and who approved it?
Accounting and accountability in practice
Accounting is easy to overlook but it is what turns a vague "something happened" into a timeline. Sign-in logs reveal when an account authenticated and from where ; configuration-change history reveals who altered a switch or router and what changed; session records reveal how long a connection lasted. When a manager asks "did this user access the file share last Tuesday?", accounting answers it. When investigating a possible compromise, accounting shows whether the attacker's logins succeeded and what they touched.
This is why shared accounts are dangerous: if five people log in as admin , accounting can no longer attribute an action to one person, and the audit trail becomes useless.
A least-privilege walk-through
Suppose a new contractor needs to upload files to one project folder for three months. The least-privilege answer is a new individual account (not a shared one), granted write access to that one folder only (not the whole share), with an expiration date set to the contract end, and a named approver recorded. Compare that to the lazy answer — adding the contractor to an existing admin group "so they can get in" — which violates every part of the principle and leaves access lingering after they leave. The CCST mindset is to ask the four questions every time: who needs access, what exact access, for how long, and who approved it.
Common traps
Treating an authorization denial as a broken login and resetting the password needlessly.
Assuming MFA makes phishing impossible — code-based MFA is still phishable; only passkeys/security keys are phishing-resistant.
Leaving a vendor default password "until later," then forgetting it.
Using one shared admin account, which destroys the accounting trail.