- Learn
- Computer Science & IT
- Information Technology
- IT Support Fundamentals
- Endpoint Security for Support Technicians
Endpoint Security for Support Technicians
BeginnerLesson 5 of 8 in IT Support Fundamentals Course
What you will learn
- Identify the main kinds of malware, the tricks social engineers use on people, and the attacks and weaknesses that put workstations and mobile devices at risk.
- Tell the main types of malware apartDescribe how viruses, worms, trojans, ransomware, spyware, rootkits and other malware get onto a device and what each one does there.
- Spot phishing and other social engineeringRecognize phishing by email, phone, text and QR code, in-person tricks such as tailgating, and respond correctly when someone is targeted.
- Recognize attacks on passwords, networks and weak systemsExplain how brute-force, dictionary, on-path, evil twin, spoofing and zero-day attacks work, and which weaknesses on a device let them succeed.
- Tell the main types of malware apart
- Set up the passwords, extra authentication factors and Windows account types that decide who can use a device and with how much power.
- Create and manage strong passwordsApply password rules on length, uniqueness, complexity and expiration, use password managers and lockout policies, and handle password resets safely.
- Add a second factor with multifactor authenticationExplain authentication factors, compare MFA methods from SMS codes to security keys, and support users who enroll, lose or misuse a factor.
- Set up Windows accounts, UAC and sign-in optionsChoose between local, Microsoft and work accounts and between standard and administrator rights, use UAC and Run as administrator correctly, and configure Windows Hello sign-in.
- Create and manage strong passwords
- Use the protections built into Windows: Microsoft Defender Antivirus, Windows Defender Firewall, file permissions and hardening settings that shrink a workstation's attack surface.
- Configure Microsoft Defender Antivirus and Windows FirewallTurn on, update and run Microsoft Defender Antivirus, and allow only the applications and ports a user needs through Windows Defender Firewall.
- Control file access with NTFS and share permissionsWork out who can open, change or delete a file through NTFS and share permissions, inheritance and file attributes, and predict what happens when files are copied or moved.
- Harden a Windows workstationReduce a workstation's attack surface with account restrictions, screen locks, firmware passwords, AutoPlay and service settings, updates and good user habits.
- Configure Microsoft Defender Antivirus and Windows Firewall
- Keep data unreadable on lost or stolen devices with disk and file encryption, and make sure no data survives when storage is reused, recycled or destroyed.
- Encrypt drives, files and devicesTurn on BitLocker, device encryption, BitLocker To Go and EFS, manage recovery keys, and know how macOS, iPhones and Android phones encrypt their storage.
- Wipe or destroy storage before reuse or disposalChoose between formatting, overwriting, secure erase, cryptographic erase and physical destruction for hard drives, SSDs and phones, and document disposal properly.
- Encrypt drives, files and devices
- Pick the right wireless security protocol, lock down a small office or home router, and protect phones, tablets and laptops that leave the building.
- Choose wireless encryption and authenticationCompare WEP, WPA, WPA2 and WPA3, TKIP and AES, and personal and enterprise authentication with RADIUS, and pick the right setting for a network.
- Lock down a small office or home routerApply secure router settings: credentials and firmware, management access, SSID and guest networks, WPS and UPnP, port forwarding, filtering and physical placement.
- Secure smartphones, tablets and laptops on the moveProtect mobile devices with screen locks, encryption, updates, locator and remote-wipe tools, backups and mobile device management for company-owned and personal devices.
- Choose wireless encryption and authentication
- Recognize the signs of an infected computer or phone, clean it with a structured removal procedure, and prevent new infections with layered tools, safe browsing and user education.
- Recognize the symptoms of an infected computer or phoneSpot the system, browser and mobile signs that suggest malware, and rule out ordinary faults that look similar before acting.
- Follow the malware removal procedureApply the standard malware removal steps in order, from verifying symptoms and quarantining the system to cleaning, restoring protection and educating the user.
- Prevent infections with layered tools and safe browsingCombine antivirus, EDR, email filtering, firewalls and user education, and configure browsers safely, from trusted downloads and extensions to certificates and privacy settings.
- Recognize the symptoms of an infected computer or phone
Endpoint Security for Support Technicians study guide
1Recognize threats to devices and people
A threat can arrive as an infected download, a convincing phone call or a connection to a fake wireless network. Recognizing the route helps you choose a useful response. Malware names describe different features, so several names can fit the same attack. Social engineering targets a person’s decisions, while technical attacks use weaknesses in accounts, applications or networks. Learn to connect the signs you see with the access an attacker wants.
1.1 How malware spreads and what it does
A slow computer and a locked document can both be signs of malware, software designed to damage devices, steal or lock data, or use resources without informed consent. Identify how it arrived separately from what it does. A fake installer can be a trojan that delivers ransomware.
Follow the route in
| Type | How it works | Useful distinction |
|---|---|---|
| Virus | Inserts code into a host file or program; runs when the host runs | Needs the infected host to execute |
| Worm | Spreads across a network by exploiting weaknesses | Can spread without a user opening a file |
| Trojan | Poses as useful software to persuade someone to install it | Does not reproduce by infecting other files |
| Boot sector virus | Infects drive boot code and loads before the operating system | Secure Boot helps reject untrusted boot code |
A remote access trojan (RAT) gives an attacker remote control. A fake PDF converter might install a RAT while still converting a document, so apparent usefulness does not make it safe.
Recognize the damage
Ransomware encrypts files and demands payment for a key. Attackers often steal data first. Files ending in .locked and a ransom note such as HOW_TO_RECOVER.txt are urgent warning signs. Mapped shares and synced cloud folders can be affected too. Disconnect an affected device promptly; recovery depends on cleaning or rebuilding it and restoring clean backup data. Payment offers no guarantee of recovery.
Spyware collects information secretly. A keylogger records keystrokes and can be software or a hardware adapter at a keyboard connection. Check physical connections on shared computers as well as installed software. Stalkerware tracks a person’s messages or location for someone they know. Its removal can alert that person; let the device owner decide when removal is safe.
A cryptominer uses CPU or GPU time to mine cryptocurrency. Heat, loud fans and battery drain while the device is idle can fit this pattern. Check the running processes before deciding what caused it.
Understand hidden infections
A rootkit changes the interfaces or components that report system activity. It may operate through application interfaces, the kernel, startup code or firmware. The infected operating system can give a scanner a false view. An offline scan examines the device while that system is not running. Reinstallation is often needed; firmware infection can also require trusted firmware recovery.
Fileless malware works in memory and may misuse PowerShell or Windows Management Instrumentation (WMI). Scheduled tasks or registry entries can bring it back after a restart. Behavior-based tools can recognize its actions even when there is little on disk to match against a known signature.
Separate unwanted software from malicious software
Adware displays unwanted ads or changes search results. A potentially unwanted program (PUP) may have been bundled into an installer with a preselected offer. It can be unwanted without being malicious. Review installed apps and browser extensions, remove unwanted additions, and use custom installation options to decline bundled extras.
Malware targets Macs and phones as well as Windows PCs. A clean scan is useful evidence, but unresolved symptoms still need investigation because hidden or new malware may evade detection.
Key Takeaways
- A virus infects a host; a worm spreads independently; a trojan disguises its purpose.
- Ransomware can affect local, shared and synced files; clean backups support recovery.
- Keyloggers collect input, while rootkits hide activity and fileless malware may leave few files.
- PUPs and adware need attention even when they are not classified as malicious.
- Persistent symptoms need investigation after a clean scan.
1.2 Phishing, impersonation and safe verification
Social engineering manipulates people into providing access, information or an action. The attacker may create urgency, claim authority or appeal to helpfulness. A well-configured computer cannot stop a person from authorizing a fraudulent payment.
Recognize the message and its target
Phishing imitates a trusted sender to obtain credentials, clicks or attachment openings. Vishing uses voice calls; smishing uses text messages; QR code phishing hides a destination inside a scannable code. Preview a QR destination before opening it. A code on a familiar poster can have been replaced.
Spear phishing uses details about a particular person or team. Whaling targets senior executives. These describe the target, so a carefully researched text message can be both smishing and spear phishing.
Business email compromise (BEC) requests money, gift cards or bank-detail changes through an impersonated or compromised mailbox. It may contain no link or attachment. Confirm a requested payment change using a number already on file. Calling the number in the suspicious message simply follows the attacker’s instructions.
Read a destination accurately
Suppose staff normally use northwind.example. A message arrives from helpdesk@northwind-support.example with the subject “Mailbox full: confirm your account within 2 hours.” The displayed link says https://portal.northwind.example, but its destination is https://northwind.example.login-verify.net/reset.
- Check the sender’s full address. The extra word changes the domain.
- Inspect the actual destination without opening it. Link text can be chosen freely.
- Read the hostname between
https://and the next single slash. Its registered domain islogin-verify.net; the familiar words to its left are subdomains controlled by that domain’s owner. - Treat the deadline as pressure to bypass checking. Open the service through a known bookmark to investigate independently.
HTTPS encrypts the connection to the named domain. A phishing site can have a valid certificate too.
Respond without extending the attack
Report a suspected message through the organization’s report button or help desk. Do not reply, open attachments or try the link to see what happens. A quick report lets support remove copies from other inboxes.
If a user entered a password, use a known-clean device to change it, revoke active sessions and check for unfamiliar MFA methods or forwarding rules. Record what happened in a ticket. A password change alone leaves other access routes worth checking.
Check people as carefully as messages
Impersonation uses a believable role or story. Tailgating follows someone through a secured door without separate authorization. Shoulder surfing watches a screen or keypad; shielding a PIN and using a privacy filter help. Dumpster diving searches trash for useful documents or drives.
A caller claiming to be a director may demand an urgent reset. Follow the approved identity checks, such as a directory callback or confirmation through the ticket process. Rank and urgency do not replace verification. Trained staff can also be fooled by a convincing approach; prompt reporting helps more than blame.
Key Takeaways
- Channel names describe how a message arrives; spear phishing and whaling describe whom it targets.
- Check the actual registered domain; familiar subdomain text and HTTPS do not establish trust.
- Confirm payment changes through an independent, established contact route.
- Use the same identity-verification procedure for every password-reset caller.
- After credential theft, change the password, revoke sessions and inspect account changes.
- Tailgating, shoulder surfing and discarded data give attackers access without malware.
1.3 Password attacks and exposed systems
A vulnerability is a weakness, such as an unpatched application. A threat is something that could exploit it, such as a malicious insider. An attack is the attempt to use that weakness. These words identify different parts of the problem.
Understand password guessing
Brute force tries possible combinations. For a fixed alphabet, the search space is:
Here, is the number of allowed characters and is the password length. With 26 lowercase letters, 8 characters give about 209 billion combinations. At an illustrative offline rate of 10 billion guesses per second, testing all of them takes about 21 seconds. Eight characters chosen from 94 symbols give about 7.1 days at that rate; 16 lowercase letters give about 138,000 years. These compare full search spaces for random choices. Real attack speed depends on the password-hashing system and hardware; predictable phrases can fall much sooner.
An online attack sends guesses to a live sign-in service, where lockouts and rate limits slow it. An offline attack works on stolen password hashes, away from those controls. A dictionary attack prioritizes common words, leaked passwords and variations such as “Summer2026!”. Credential stuffing tries already leaked username/password pairs at other services. Long, unique passwords and MFA address different parts of these risks.
Recognize interception and false identities
An on-path attack (man-in-the-middle) puts an attacker between communicating parties. An evil twin copies a legitimate Wi-Fi network name to attract connections. Do not auto-join open networks; check network identity, use HTTPS, heed certificate warnings and use the approved VPN on public Wi-Fi. A VPN protects its traffic path but does not make a fake sign-in page trustworthy.
Spoofing fakes an identity such as a sender address, caller ID or MAC address. A zero-day attack uses a weakness for which a fix is not yet available or which the vendor has not yet learned about. Behavior detection, restricted accounts and firewalls help limit exposure before a patch arrives.
Recognize service and application attacks
A DoS overloads a service; a DDoS uses many sources, often a botnet of compromised devices. An insider threat misuses legitimate access intentionally or through carelessness.
SQL injection makes an unsafe application treat input as database commands. Cross-site scripting (XSS) makes a website run attacker-supplied script in visitors’ browsers. A supply chain attack compromises a trusted product or update; the SolarWinds Orion compromise in 2020 is an example. Support staff keep software current and report signs of compromise; application developers fix unsafe input handling.
Find the exposed endpoint
An unpatched device lacks available fixes. An unprotected device lacks working antivirus or firewall protection. A non-compliant device breaks policy, perhaps by missing encryption. BYOD means personally owned devices used for work, whose security must also be checked.
End-of-life (EOL) software no longer receives normal security fixes. Windows 10 Home and Pro reached end of support on October 14, 2025; enrolled devices can receive limited Extended Security Updates. Replace or isolate unsupported systems. Prioritize fixes for weaknesses attackers are already exploiting.
Key Takeaways
- Online guessing meets service controls; offline guessing against hashes does not.
- Random length increases the brute-force search space; password reuse enables credential stuffing.
- An evil twin copies a network identity; certificate warnings still matter on a familiar SSID.
- Unpatched, unsupported and unprotected systems expose different weaknesses.
2Protect sign-in and account access
Account security starts before a user signs in and continues after access is granted. A long, unique password limits guessing and reuse attacks; a second factor adds a separate check. On the device, account rights decide which changes a signed-in user or their software can make. Support technicians also protect recovery routes, because a rushed password reset or lost-phone replacement can bypass an otherwise strong sign-in process.
2.1 Passwords, managers and safe resets
A strong password needs both length and uniqueness. Adding characters expands the guessing space, but reusing a strong password lets one breach affect several accounts. Character types, complexity requirements and expiration are separate policy settings.
Apply policy with an understanding of its purpose
NIST’s 2025 guidance requires at least 15 characters for a password used alone. When a password is used with MFA, the minimum may be 8. It recommends accepting at least 64 characters and rejects mandatory character mixtures and routine scheduled changes. A change is required when there is evidence of compromise, and common, expected or breached passwords must be blocked.
Many employers still require mixed character types, password history or expiration. Apply the organization’s policy and explain its settings accurately. Meeting a complexity rule does not make a familiar word unpredictable: “P@ssw0rd!” is a standard guessing target.
A passphrase combines random, unrelated words. “Violet harbor tractor sings” has 27 characters including spaces. A famous quotation, song lyric or personal detail is easier to anticipate. Keep any real passphrase private and unique to one account.
Use a manager to make uniqueness practical
A password manager stores passwords in an encrypted vault and generates long random values for separate sites. Protect the vault with a strong master password and MFA. Browser and operating-system managers can provide this function, as can separate applications.
Autofill is also a useful check. A manager normally matches a saved login to its website, so a familiar-looking page where the saved password is not offered deserves investigation. Open the real service through a known route instead of copying credentials into the page to force it to work.
Know what Windows settings control
On Windows Pro and higher, open Local Security Policy with secpol.msc, then inspect Account Policies. Domain policy may manage these settings centrally.
| Policy group | Main controls |
|---|---|
| Password Policy | Minimum length, complexity, history and maximum age |
| Account Lockout Policy | Failure threshold, lockout duration and counter reset time |
Lockout slows guesses against the live sign-in service. It does not slow an attacker testing stolen hashes offline. A very low failure threshold also lets an attacker deliberately lock out many accounts and creates avoidable support calls.
For a simple rate-limit example, suppose a service permits 5 guesses in each 15-minute window. There are 96 windows in a day, so it permits 480 guesses a day. Exhausting 10,000 possible four-digit PINs would take about 21 days at that limit. Real lockout behavior depends on the configured threshold, reset window and duration.
Reset without exposing the secret
Verify the caller through the approved process before changing anything. Where temporary passwords are used, set “User must change password at next logon” and deliver the temporary secret through the approved secure channel. Never ask for the current password or place a password in a ticket, ordinary chat or email. Record the identity checks and action, without recording the secret.
Key Takeaways
- Use a different long password for every account; a password manager makes this manageable.
- Current NIST guidance favors length and breached-password screening over routine expiration.
- Lockout controls live guessing and can also create deliberate lockout problems.
- Verify identity before a reset and keep secrets out of tickets.
2.2 MFA methods and account recovery
Authentication checks a claimed identity. Its main factor categories are something you know, such as a password; something you have, such as a security key; and something you are, such as a fingerprint. Location and typing behavior may provide extra signals.
Count categories, not screens
Multifactor authentication (MFA) combines at least two factor categories. A password plus a phone-generated code combines knowledge and possession. A password plus a security question uses knowledge twice, even when the service shows two screens.
| Method | Main support issue |
|---|---|
| SMS or voice code | SIM swapping can transfer the number to an attacker |
| Email code | Mailbox compromise exposes the code; NIST does not accept email as this authentication channel |
| Authenticator code | Can work offline, but typed codes can be phished |
| Push approval | Unexpected prompts can pressure users into approving |
| FIDO2 security key or passkey | Cryptographic proof is bound to the genuine service |
| Smart card with PIN | Combines possession of the card with knowledge of its PIN |
A password and a biometric check can also combine categories when implemented as independent checks. On phones and Windows Hello devices, a local fingerprint or face check usually unlocks a protected key on the device.
Support codes and prompts correctly
A time-based one-time password (TOTP) uses a shared secret enrolled in the app, commonly by scanning a QR code. The app combines it with time to generate a code, often six digits changing every 30 seconds. No network is needed to calculate it, but a wrong device clock can cause failures. An OTP is valid for one use; a six-digit code has one million possible values.
MFA fatigue, or push bombing, sends repeated prompts until someone approves. Users should deny and report prompts they did not initiate. Number matching asks them to enter the number from their own sign-in screen and reduces casual approval. It does not make a typed or relayed process equivalent to a phishing-resistant key.
FIDO2 security keys and passkeys resist fake-site relay because they authenticate to the correct service. Codes entered into a fake page can be forwarded to the real service while still valid.
Plan for loss without bypassing identity checks
For a lost authenticator phone, verify identity, revoke the lost method, use an approved backup method or recovery code, then enroll the replacement. Encourage two enrolled methods so a single loss does not block access. Do not enroll a new phone merely because a caller knows the username.
Biometric readers can falsely accept the wrong person or reject the right one. Protected hardware holds the local template, and a PIN or password remains available as fallback. A biometric is harder to replace than a compromised password.
Recognize the service behind the prompt
Kerberos gives time-limited tickets for Windows Active Directory sign-in; its default clock tolerance is five minutes, so investigate time synchronization when domain authentication fails. RADIUS checks Wi-Fi and VPN access. Single sign-on (SSO) lets one sign-in open several apps, often through SAML assertions. Protecting that central sign-in with MFA protects an important route into connected applications.
Key Takeaways
- MFA uses different factor categories; two knowledge checks remain one category.
- TOTP needs the shared secret and a reasonably accurate clock, not a live network.
- Phishing-resistant keys bind proof to the genuine service; typed codes can be relayed.
- Deny and report unexpected approval prompts.
- Lost-factor replacement requires identity verification and revocation of the lost method.
- Kerberos uses tickets and synchronized clocks; SSO shares a sign-in across applications.
2.3 Windows identities, rights and elevation
Windows separates who the account belongs to from what it can change. A local, Microsoft or work account can have different rights. Choosing the right identity does not by itself justify administrator access.
Choose the identity
| Account kind | Where it belongs |
|---|---|
| Local account | One PC, with credentials managed there |
| Microsoft account | An online identity for services, settings sync, online reset and recovery-key storage |
| Work or school account | An organization’s directory, such as Active Directory or Microsoft Entra ID |
A standard user can run installed apps and change personal settings. An administrator can also make system-wide changes and manage other accounts. Use standard rights for daily work and a separate administrator identity for approved maintenance. This limits what software started in an ordinary session can change.
Keep Guest disabled. The legacy Power Users group remains for compatibility and gives no extra rights over a standard user by default.
Elevate a task without promoting a person
User Account Control (UAC) keeps applications at ordinary rights until elevation is requested. An administrator normally sees a consent prompt; a standard user must supply administrator credentials. The dimmed secure desktop helps protect the prompt from other applications.
A shield marks settings that need elevation. Right-clicking a program and choosing Run as administrator elevates that program. For example, an approved repair using sfc /scannow needs an elevated command window. Confirm both the program and the reason before approving. A malicious program with elevated rights can change the system too.
Do not make an employee an administrator just to install one approved program. Supply authorized credentials at the UAC prompt for that task. Keep UAC enabled; “Never notify” removes a useful check.
Understand Windows Hello
Windows Hello provides a device PIN, fingerprint or facial recognition. Face recognition needs suitable infrared hardware. Passwordless settings can hide the password sign-in option.
A Hello PIN unlocks a key protected by the device’s Trusted Platform Module (TPM), with defenses against repeated guessing. It is not the reusable password sent to an online account. Knowing the PIN without holding the device does not provide the same remote access as knowing that account’s password. This explains why a short local PIN and a long online password have different security roles.
Prepare and maintain an employee laptop
- Enroll or join it using the organization’s approved work-account process.
- Confirm the employee has standard rights and the technician has a separate maintenance identity.
- Set up Hello and keep UAC at the approved level.
- Disable unused local accounts and confirm Guest stays disabled.
- Check that required management settings apply.
An Active Directory domain centralizes accounts and settings. Group Policy can apply password, firewall and encryption rules, log-in scripts, home-folder mappings and folder redirection. Policy targets depend on organizational units and security groups. gpresult /r shows applied policy; gpupdate /force requests a refresh. If a local setting keeps reverting, check the managing policy before changing it again.
Key Takeaways
- Account identity and administrator rights are separate choices.
- Use standard accounts daily and elevate only approved maintenance tasks.
- A Hello PIN unlocks a device-bound key; it is different from a reusable online password.
- Check Group Policy when local settings return to a managed value.
- Guest stays disabled; Power Users gives no extra default rights.
3Keep Windows protections working
Windows protections solve different problems: antivirus checks software, a firewall limits connections, and permissions limit access to files. Hardening removes unnecessary entry points and keeps the remaining ones secure. A useful support fix identifies the specific control blocking legitimate work, changes it narrowly and tests the result. Check central policy before changing a managed PC so the repair works with the organization’s settings.
3.1 Defender scans and firewall rules
Open Windows Security to inspect Virus & threat protection, Account protection, Firewall & network protection, App & browser control, and Device security. SmartScreen warns about suspicious downloads and phishing. Device security exposes features such as the TPM and Secure Boot.
Keep antivirus active
Microsoft Defender Antivirus provides real-time checks, cloud-delivered checks and tamper protection. Its security intelligence updates contain current detection information and arrive through Windows Update. Check Protection updates when definitions need refreshing manually.
Turning off real-time protection through the interface is temporary; Windows normally turns it back on. A registered non-Microsoft antivirus becomes the main real-time engine. Defender may be disabled or run in a managed passive mode, depending on configuration. Check which product is responsible before treating an inactive Defender screen as a fault. Two competing real-time engines can conflict and slow the computer.
Choose the scan that answers the problem
| Scan | Purpose |
|---|---|
| Quick | Common startup and infection locations |
| Full | Files and programs across the device; may take hours |
| Custom | A selected drive, file location or folder |
| Defender Offline | Restarts into a scanning environment outside normal Windows |
Defender Offline supports x64 Windows 11 PCs; it is not available on ARM-based Windows 11. Save the user’s work before an offline scan. It takes about 15 minutes and helps find malware that hides while Windows runs. Review the findings and unresolved symptoms afterward.
An exclusion tells Defender to skip a specified location or process. Use one only for a verified application need, with the smallest approved scope. Excluding Downloads or an entire drive creates a large blind spot. A blocked installer needs investigation; disabling antivirus to let it run removes the check that raised the warning.
Match firewall rules to the network
Windows Defender Firewall is a host firewall, protecting this computer. Its profiles are Domain for a recognized domain connection, Private for a trusted home or office network, and Public for unfamiliar networks. Choose Public on a network you do not control. Keep protection enabled on every profile.
By default the firewall blocks unsolicited inbound connections unless a rule permits them, while allowing outbound traffic. An application rule permits a program on selected profiles. Advanced rules in wf.msc can also restrict protocol, port and remote addresses.
Repair access with a narrow change
Suppose the help desk cannot reach a domain PC through Remote Desktop:
- Confirm Remote Desktop is approved and enabled on the destination.
- Inspect its existing inbound rule for TCP 3389.
- Allow the Domain profile and the approved help-desk address range.
- Test from an authorized source and record the rule change.
Opening the same port on every profile to every source creates unnecessary exposure. Switching the entire firewall off also removes unrelated protections. A rule should describe the required traffic as closely as the task allows.
Key Takeaways
- Check the registered real-time antivirus provider before changing Defender settings.
- Quick, full, custom and offline scans examine different scopes.
- Keep exclusions specific and verified.
- Use Public on unfamiliar networks and keep all firewall profiles protected.
- Limit an access rule by application or protocol, port, profile and source where possible.
3.2 Effective access to files and shared folders
A user’s access depends on the route to the file and the permissions along that route. NTFS permissions apply locally and over the network. Share permissions apply only when someone reaches a shared folder across the network.
Combine the right controls
NTFS offers Full control, Modify, Read & execute, List folder contents, Read and Write. Share permissions offer Full Control, Change and Read. For network access, the user needs the requested action allowed by both layers.
Suppose the Reports share gives Everyone Read, while NTFS gives the Sales group Modify. Ana belongs to Sales:
- Through the share, the share layer permits reading only.
- NTFS permits modification, but cannot add a right blocked by the share layer.
- Ana can therefore read over the network. When signed in locally, the share limit is absent, so her NTFS Modify permission applies.
A common design keeps share permissions broad enough for intended work and manages detailed access through NTFS groups.
Understand multiple groups and inheritance
Allow permissions from group memberships generally add up. Read from one group and Modify from another allow Modify. A Deny at the same precedence level overrides the matching Allow, but explicit entries take precedence over inherited entries. An explicit Allow can therefore beat an inherited Deny. The shortcut “Deny always wins” hides this distinction.
New files and subfolders normally inherit the destination folder’s entries. Inherited entries appear grayed out. Turning inheritance off lets you convert them to explicit entries or remove them. For a private HR subfolder, inspect the inherited department access before deciding which entries should remain.
Grant rights to groups where possible and use Deny sparingly. The Advanced Security Settings Effective Access tab helps examine NTFS access for a particular user. Check share permissions separately for a network-access problem.
Predict copying and moving
| Operation with normal file-management behavior | Permission result |
|---|---|
| Copy to an NTFS folder | New copy inherits destination permissions |
| Move within one NTFS volume | Existing permissions stay with the file |
| Move to another volume | Copy-and-delete behavior gives destination permissions |
| Copy to FAT32 or exFAT | NTFS permissions cannot be retained |
For example, moving a restricted file between folders on the same volume can leave it restricted even when its neighbors are readable. A copy into the destination usually receives that folder’s permissions. Tools with special preservation options can deliberately behave differently, so check the operation used when diagnosing an unexpected result.
Keep attributes separate
Read-only, Hidden, System and Archive are attributes, not a replacement for access permissions. attrib +r +h notes.txt marks a file read-only and hidden. A user with suitable rights can change attributes, and showing hidden files exposes hidden names. Advanced attributes also include compression and EFS encryption.
Avoid granting Everyone Full control to fix an access failure; it can expose the data to accounts that do not need it.
Key Takeaways
- NTFS applies locally and remotely; share permissions apply across the network.
- Network access is limited by both permission layers.
- Explicit entries take precedence over inherited entries; equal-level Deny overrides Allow.
- Copies normally inherit the destination; same-volume moves normally retain existing permissions.
- Hidden and Read-only attributes do not secure files against authorized access.
- Inspect Effective Access and share settings before granting more rights.
3.3 Workstation hardening and updates
Hardening reduces the attack surface: the accounts, services, programs and connections that could provide a way in. Keep what the job needs, secure it and remove unused access.
Restrict account access
Replace factory administrator credentials with unique ones, rename default administrator accounts where policy requires, and disable unused accounts and Guest. Renaming alone leaves the password unchanged and is not sufficient protection. Use standard rights for everyday work.
Set expiration dates for temporary workers and restrict logon hours when appropriate. For a local account, net user jdoe /times:M-F,08:00-18:00 sets weekday logon hours; domain accounts can have centrally managed hours. Configure failed-attempt lockout through policy. Check planned work and support needs before tightening schedules.
Set a short idle lock, such as five minutes on an office PC, and require sign-in when returning. Users can press Windows key + L before leaving and log off at the end of the day. Dynamic Lock uses the paired phone’s Bluetooth presence to help lock the computer when the user moves away.
Protect startup settings and stored data
A firmware administrator or supervisor password protects BIOS/UEFI settings. A user or power-on password is requested before startup. They serve different purposes.
An administrator password alone may leave the one-time USB boot menu available. Set the internal drive first, disable or password-protect external boot and the one-time menu, and retain Secure Boot. Disk encryption protects data if someone removes the drive entirely. Store firmware credentials securely; a lost business-laptop password may require manufacturer service.
Remove unnecessary ways to run software
Current Windows does not automatically execute programs from ordinary USB drives through autorun.inf, but AutoPlay can still offer actions when media is inserted. In Settings > Bluetooth & devices > AutoPlay, disable it or require a choice each time. Group Policy can manage these choices.
Uninstall unused trial software, obsolete plug-ins and unnecessary applications. Disable unused services only after checking dependencies in services.msc. Turning off Remote Desktop is sensible on a PC that has no approved remote-access need; disabling a required service can instead break the user’s work.
Keep fixes moving
Install operating-system, application and driver security updates promptly. Prioritize a flaw already being exploited. A patch cannot help until it is installed and any required restart is completed. Replace or isolate unsupported products that no longer receive fixes.
For a spare office laptop, a useful sequence is to remove stale accounts and software, apply current updates, check antivirus and firewall status, verify the idle lock and encryption, then test the required applications. This confirms that the hardened device remains usable.
Protect the hardware and the information around it too. Secure a laptop when unattended, avoid leaving it in a car, lock away sensitive printouts, clear the desk and use privacy filters where screens can be overlooked. Personally identifiable information (PII) is data that identifies a person and needs protection throughout ordinary support work.
Key Takeaways
- Remove unused accounts, software and services after checking what the job needs.
- Use screen locks and secure startup settings alongside disk encryption.
- AutoPlay settings still matter even though USB AutoRun behavior has changed.
- Install exploited-vulnerability fixes first and finish required restarts.
- Protect printouts, passwords and unattended hardware as part of daily work.
4Keep data safe through loss and disposal
Encryption protects stored data when a device is lost, stolen or opened outside its normal operating system. Recovery information lets authorized people regain access after a startup change or account problem. Disposal has a different aim: removing access permanently before storage is reused or leaves the organization. Match the protection or erasure method to the storage type, and check the result before returning or releasing the device.
4.1 Drive encryption and recoverable keys
Data at rest is stored on a device; data in transit is moving over a network. Disk encryption protects stored data if a powered-off device is stolen or its drive is removed. Once the user unlocks a session, applications and malware in that session can read accessible files. Keep screen locks and anti-malware working too.
Select the Windows tool
| Tool | Scope and use |
|---|---|
| BitLocker | Whole volumes on Windows Pro, Enterprise and Education |
| Device encryption | Simplified BitLocker protection on qualifying devices, including Home |
| BitLocker To Go | Removable drives, unlocked with a password or smart card |
| Encrypting File System (EFS) | Individual files and folders on NTFS for a user |
BitLocker normally uses a Trusted Platform Module (TPM) to protect key material and check startup integrity. It supports TPM 1.2 or later; Windows 11 requires TPM 2.0. A startup PIN adds a check before automatic unlocking. Without a TPM, supported configurations use a USB startup key. Run manage-bde -status to inspect encryption and protection state.
Windows 11 version 24H2 expanded automatic device-encryption eligibility. On a qualifying clean setup, encryption can initialize before protection is armed. Signing in with a Microsoft or work account backs up the recovery key and enables protection. Local-account-only setup can leave a clear key, equivalent to suspended protection. Check Protection Status, not just the percentage encrypted. External drives need their own protection.
Recover from a startup change
The BitLocker recovery key is a 48-digit recovery password in eight groups of six digits. A Key ID identifies the matching record. Firmware changes, altered boot settings, a moved drive or repeated wrong startup PINs can trigger recovery.
For a recovery screen after a firmware update:
- Match its Key ID to the record in the organization’s directory or the owner’s Microsoft account.
- Retrieve the authorized 48-digit value and unlock the drive.
- Verify the startup change was expected and check that protection is active afterward.
Store recovery information outside the encrypted drive: in the approved directory, account, separate file location or protected printout. Microsoft cannot create a missing key. Before planned firmware or hardware work, follow the approved suspension process. Suspension leaves data encrypted but temporarily leaves a key accessible; resume protection after the change and verify it.
Protect files and other platforms
EFS uses a user certificate and private key to encrypt selected NTFS files. The owner opens them normally; other users, including administrators by default, cannot decrypt them merely by having administrator rights. Back up the certificate with its private key, normally as a protected .pfx file, or ensure an authorized recovery-agent key exists. Profile loss or an administrator’s local-password reset can otherwise leave files inaccessible. Copying to FAT32 or exFAT removes EFS protection.
BitLocker addresses possession of the drive; EFS addresses access to selected files by other users. FileVault provides Mac disk encryption with configured recovery options. iPhones and iPads use encryption and passcode-linked Data Protection. Current Android phones use storage encryption with screen-lock protection. Strong locks and tested recovery arrangements remain necessary on every platform.
Key Takeaways
- Disk encryption protects stored data; an unlocked session still exposes accessible files.
- Check both encryption progress and protection status.
- Match a recovery screen’s Key ID to its 48-digit recovery record.
- Back up EFS certificates with their private keys.
- BitLocker To Go protects removable drives separately.
4.2 Sanitizing storage before it changes hands
Deleting a file is not a dependable sanitization method. On an HDD, the reference is removed but data may remain until overwritten. SSD TRIM and garbage collection may erase deleted blocks, but their timing is not a reliable disposal procedure.
Choose the required result
NIST’s media-sanitization framework distinguishes three results:
| Level | What it achieves | Reuse |
|---|---|---|
| Clear | Defeats ordinary recovery through normal interfaces | Possible |
| Purge | Makes recovery infeasible even with advanced laboratory techniques | Often possible |
| Destroy | Makes recovery infeasible and the media unusable | No |
Choose the level using data sensitivity, organizational policy and the device’s destination. Confirm that important data is backed up and erasure is authorized before starting.
A quick format builds an empty file system. On an HDD, much of the previous content can still remain. Current Windows full formatting also overwrites the selected partition, but does not sanitize areas outside it or SSD spare blocks. A true low-level format belongs to manufacturing; utilities using that name generally overwrite storage.
Match the method to the medium
An approved full overwrite can clear an HDD; one pass is sufficient for modern drives at that level. Repeated passes add time without a useful improvement in ordinary recovery resistance. At 150 MB/s, writing 1 TB means writing 1,000,000 MB. Dividing gives about 6,667 seconds, or 1 hour 51 minutes; three passes take about 5.6 hours.
An SSD distributes writes through wear leveling and spare blocks. Operating-system overwrites can miss old data. Use an approved manufacturer sanitize or secure-erase process appropriate to that drive, or a validated cryptographic-erase process, then verify completion.
Cryptographic erase makes encrypted data inaccessible by destroying the key material needed to decrypt it. The data must have been adequately encrypted, and every usable copy of the relevant key material must be eliminated. Deleting one recovery-key file or removing one BitLocker protector is insufficient. An approved device sanitize process handles the required key lifecycle. Modern encrypted-phone reset processes can erase keys; sign out of the owner’s Apple or Google account before an authorized handover so Activation Lock or Factory Reset Protection does not block the next user.
Know when destruction is necessary
A failed drive can still hold readable data. Use approved destruction when erasure cannot be completed or policy requires it. Industrial shredding breaks media into sufficiently small pieces. Drilling a few holes can leave readable platter or chip fragments. Degaussing affects magnetic media such as HDDs and tape, not flash chips in SSDs. Licensed facilities may also use incineration.
For an employee handover, clear the laptop with the approved method and then install the company image. For a sensitive SSD leaving the organization, use an approved purge method and check the result. Reimaging by itself can leave old data behind.
Close the disposal record
Track devices through a documented chain of custody. A disposal provider’s certificate should identify serial numbers, date and method, and whether media was destroyed or recycled. Record verification evidence as well as the requested action. Follow applicable data-protection and electronic-waste requirements, and send devices and batteries to approved recycling channels.
Key Takeaways
- Clear, Purge and Destroy describe different sanitization outcomes.
- A quick format or reimage can leave previous data recoverable.
- HDD overwrites and SSD sanitization need different methods.
- Cryptographic erase must remove every usable copy of the necessary key material.
- Degaussing is for magnetic media; it does not erase SSD flash.
- Check the result and retain serial-number and custody records.
5Secure Wi-Fi, routers and mobile devices
A device’s protection travels with it, but its network and location can change throughout the day. Choose Wi-Fi settings that fit the equipment and the way users join and leave. Secure the router’s management interface as carefully as its wireless password. On phones and tablets, combine strong screen locks, updates, recovery tools and appropriate management so a lost device does not become an open route into work accounts.
5.1 Wireless modes and individual authentication
A Wi-Fi network needs modern encryption and an authentication method suited to its users. A strong shared password helps a small team, but individual identities make access easier to revoke as an organization grows.
Choose a supported security generation
| Setting | Security decision |
|---|---|
| WEP | Broken; do not use it |
| WPA with TKIP | Retired design; replace it |
| WPA2 with AES/CCMP | Widely supported secure fallback |
| WPA3 | Preferred current generation when devices support it |
TKIP was a stopgap for older hardware. It is weaker and prevents modern Wi-Fi high data rates. Avoid “WPA/WPA2 mixed TKIP+AES.” AES is the modern cipher used by WPA2 and WPA3. WPA3-Enterprise also offers an optional stronger 192-bit security mode.
Choose WPA3 where all devices support it. WPA2/WPA3 transition mode accommodates older devices, but those devices still use WPA2 protection. Keep AES enabled and plan to replace incompatible equipment.
Personal mode shares a secret
In Personal mode, everyone uses a shared passphrase, commonly 8–63 characters. WPA2-Personal uses a pre-shared key (PSK). Captured connection traffic lets an attacker test passphrase guesses offline, which makes a long random passphrase valuable.
WPA3-Personal uses Simultaneous Authentication of Equals (SAE) to resist passive offline guessing and provide forward secrecy: a later password leak does not reveal earlier captured traffic. WPA3-only operation requires Protected Management Frames (PMF), which protect certain management messages against forgery. Transition mode retains weaker compatibility behavior for WPA2 clients.
Anyone who knows the shared secret can keep joining until it changes. Separate guests and change the staff secret when it has been exposed or a former user should lose access.
Enterprise mode checks each user
Enterprise mode, using 802.1X, gives users separate credentials or certificates. The access point passes authentication to a server, usually RADIUS, connected to the organization’s directory. Disable a departing employee’s account without changing every device’s password. Configure clients to validate the approved authentication server’s certificate; a matching network name alone is not enough to trust a login request.
A dental practice with 12 staff might use WPA3-Personal and an isolated patient guest network. A 300-person company with frequent staff changes benefits from Enterprise mode and central account control. The decision is about access management as well as encryption strength.
Recognize protocol roles
RADIUS commonly supports Wi-Fi, VPN and remote access. Traditional RADIUS uses UDP 1812 for authentication and UDP 1813 for accounting; its traditional packet protection encrypts the password, not the whole packet. TACACS+ uses TCP 49, protects the message body and separates authentication, authorization and accounting; it mainly manages administrator access to routers and switches. Kerberos supplies tickets for Windows-domain sign-in. MFA can also be integrated with supported RADIUS access systems.
Key Takeaways
- Choose WPA3 when supported; retain AES when compatibility requires WPA2.
- WPA2-Personal permits offline guessing of captured handshakes; SAE improves this protection.
- Enterprise authentication gives each person revocable access.
- RADIUS, TACACS+ and Kerberos serve different sign-in roles.
- A guest network should remain separate from staff devices.
5.2 Router management and guest access
A router controls the boundary between local devices and the internet. Its administrator password protects the configuration; its Wi-Fi passphrase lets clients join. They are different secrets and should both be strong and unique.
Secure the management route first
Replace shared factory administrator credentials, including the username where supported. If setup asks you to create a password, create a unique one. Install current firmware and enable automatic updates where available. Replace routers that no longer receive fixes.
Use HTTPS for the administration page. Disable management from the internet (WAN) unless a specific approved need exists, and restrict management to wired LAN clients or designated addresses. A person who reaches the interface with valid credentials can change the network’s settings.
Configure wireless access
Change the factory SSID, the network name, to a neutral name that reveals neither the owner’s address nor the router model. Set WPA3, or AES-based WPA2/WPA3 transition mode for older clients. Disable Wi-Fi Protected Setup (WPS). Its PIN design checks two parts separately, reducing the theoretical search from the full eight-digit space to at most 11,000 combinations before considering lockout defenses.
Hiding the SSID removes it from casual lists, but connection traffic still reveals it. MAC address filtering also offers limited protection because an attacker can copy an authorized address. Neither replaces encryption and strong authentication.
Separate guests and exposed services
Create a guest SSID with its own passphrase. Confirm that guest clients have internet access but cannot reach office computers or printers. Client isolation can also stop guests reaching one another. Separate Internet of Things devices when supported, because they may have weaker update and management options.
Universal Plug and Play (UPnP) lets local devices request inbound mappings automatically. Disable it unless a supported need justifies it. Malware on a local device can misuse that convenience too.
Port forwarding sends an external port to a particular internal device. For an approved web server, forwarding TCP 443 to a reserved internal address exposes that web service. Record the purpose and remove the mapping when the service ends. The host still needs its own updates and firewall protection.
| Setting | Meaning |
|---|---|
| Screened subnet (DMZ) | A separated segment for internet-facing services |
| SOHO “DMZ host” | A device receiving broadly forwarded unsolicited inbound traffic |
The SOHO shortcut is not an isolated screened subnet. Use a specific port mapping when one service is needed; forwarding unrelated ports expands the exposure.
Finish the checks
Keep the router firewall enabled. IP filtering permits or blocks specified addresses, while content filtering blocks site categories or malicious domains. Disable unused firewall openings and unused physical ports where managed equipment allows it.
Place the router where visitors cannot press Reset or replace cables. A reset can restore default settings. Central placement and suitable transmit power can reduce signal outside the workspace, but encryption remains essential wherever the signal reaches.
Before closing the setup task, test staff access, guest isolation and any required service mapping from the correct network. Save the approved configuration and document credentials in the authorized secret store.
Key Takeaways
- Router administration and Wi-Fi joining use different credentials.
- Update firmware and restrict management access.
- Disable WPS; hidden SSIDs and MAC filters do not replace authentication.
- Test that guests cannot reach the internal network.
- Forward only needed services; a SOHO DMZ host exposes far more traffic.
- Protect the router from physical reset and retain the approved configuration.
5.3 Mobile locks, recovery and work profiles
Phones, tablets and laptops carry both stored files and active access to accounts. Combine a strong screen lock with encryption, updates and a recovery plan before the device goes missing.
Set a real lock
Swipe provides no protection. Patterns are easy to observe and may leave recognizable smudges. A PIN gains possibilities with length: four digits provide 10,000 combinations, while six digits provide one million. A long password provides a larger search space when chosen unpredictably.
Fingerprint and face unlock are convenient, but hardware quality matters. Camera-only face unlock can be weaker than a suitable PIN. The fallback PIN or password still needs to be strong. Set a short automatic lock, such as one minute, and enable the organization’s failed-attempt restrictions.
Delays slow repeated wrong guesses. On iPhone, the optional Erase Data setting removes device data after ten consecutive failed passcode attempts. Check backup arrangements before enabling an approved erasure policy. MDM can enforce passcode and attempt settings.
Keep platform protections intact
Modern iPhones and Android phones use storage encryption with passcode or screen-lock protection. Laptops use BitLocker or FileVault. Install operating-system and app updates promptly, and replace phones that no longer receive security updates for work use.
Install apps from official stores and avoid rooting Android or jailbreaking iOS, which removes important built-in restrictions. Review powerful app permissions. Android security apps can scan other installed apps within platform limits. On iOS and iPadOS, application sandboxing prevents third-party antivirus from scanning other apps or system files; security tools instead focus on functions such as malicious-site filtering and configuration checks.
Prepare and use recovery tools
Apple Find My and Google Find Hub can locate a supported lost device, play a sound, secure it and request erasure. Confirm locator enrollment in advance. A remote wipe requires the device to receive the command, so an offline device can leave the request pending. Encryption protects stored data while recovery actions are waiting.
Back up important data through the approved service, such as iCloud, Google backup or OneDrive. After a loss, lock or mark the device lost, follow policy for remote wipe, revoke exposed sessions or credentials, and record the event. Restore data to a replacement from a trusted backup.
Apply the right management scope
Mobile device management (MDM) enrolls devices for central controls. A configuration profile can deliver Wi-Fi, VPN and email settings or require encryption, a minimum OS version and a passcode. Non-compliant devices can be blocked from work services.
| Ownership | Typical management scope |
|---|---|
| Corporate-owned | Full device controls and an approved full wipe |
| Personal BYOD | A managed work profile or container and selective removal of work data |
A selective wipe removes organizational data while preserving the owner’s photos and personal apps within the supported management model. Explain that scope during enrollment. For a departing employee using a personal phone, verify the work profile is removed and account sessions are revoked; do not select full-device erasure when only work removal is authorized.
Key Takeaways
- Use a strong fallback lock, a short auto-lock time and failed-attempt controls.
- Keep mobile operating systems and apps updated; retain built-in platform restrictions.
- Prepare locator and backup tools before loss; an offline device may not receive a wipe immediately.
- MDM enforces settings and access requirements.
- Match full or selective wipe to ownership, management capabilities and authorization.
6Investigate, clean and prevent infections
Unexpected pop-ups, disabled protection or changed files need a structured investigation. Symptoms can also come from ordinary faults, so check the evidence before choosing a repair. When infection is likely, stop its spread, clean or rebuild the device, and restore protection before returning it. Prevention then connects the technical fix to safer downloads, current software and the user’s next decision, with clear records for the support team.
6.1 Symptoms and checks that narrow the cause
A symptom is a clue to investigate, not a malware name. Look for patterns, establish when they started and check ordinary explanations alongside security causes.
Identify the pattern
PC warning signs include inaccessible networks, unexpected alerts or notifications, altered files, update failures, disabled security software and heavy CPU, disk or network use while idle. Browser signs include repeated pop-ups, redirects, unknown toolbars or extensions, changed search settings, certificate warnings and poor performance.
On mobile devices, watch for unusually high data use, overheating, battery drain, slow response, unknown apps, excessive ads, fake warnings, leaked files and lost connectivity. Unofficial app sources, root access or jailbreak, and unnecessary developer settings increase risk. Application spoofing makes a fake app look like a trusted one.
A single hot phone may be updating or running a demanding app. Heat combined with an unknown app and unexplained network use gives a stronger reason to investigate that app.
Rule out common faults with useful checks
| Observation | Ordinary cause to check |
|---|---|
| Certificate warnings across familiar sites | Incorrect date, time or time zone |
| Failed updates | Full disk or broken connectivity |
| General slowness | Low memory, failing storage or legitimate background work |
| High battery or processor use | An active app, update or background task |
Ask what the user saw, when it started, and what they installed or opened shortly beforehand. Task Manager shows processes and startup items. Review installed apps, browser extensions and relevant Event Viewer entries. The hosts file at C:\Windows\System32\drivers\etc\hosts can redirect names if modified; compare unexpected entries with the approved configuration before changing them.
If the clock is wrong, correct it through the approved time settings and retest the website. Do not dismiss a certificate warning by bypassing it. If a drive is failing, a malware scan alone will not repair its hardware.
Respond to recognizable patterns
Changed search results, a new toolbar and ads across unrelated sites point toward adware or a browser hijacker. Follow the removal process and inspect extensions and installed applications. Files suddenly encrypted or renamed alongside ransom demands call for immediate network isolation, because shared storage can be affected too.
A browser page announcing “Your PC is infected! Call Microsoft Support now” is scareware. Genuine Microsoft error and warning messages do not provide a support phone number. Close the page; use Task Manager to close the browser if necessary. Do not call or install the offered tool. Run the appropriate checks afterward.
If the user already allowed a stranger to connect remotely, treat the device as compromised and change exposed passwords from a clean device. Record the remote access and follow the organization’s escalation process. A browser page claiming infection and a confirmed compromise require different conclusions, even when they started with the same warning.
Key Takeaways
- Investigate patterns across system, browser and mobile symptoms.
- Check time, storage, memory and legitimate activity as alternative causes.
- Use Task Manager, installed apps and extensions to connect symptoms to changes.
- Isolate promptly when ransomware signs appear.
- A scareware page is a fraudulent claim; granted remote access creates a real compromise risk.
6.2 A complete malware removal sequence
A structured removal process controls spread, cleans the device and checks that it is safe to return. Follow the organization’s security escalation rules on managed devices. The standard workstation sequence includes System Restore tasks on Windows PCs that use it.
Investigate, then quarantine
Record the symptoms, start time and recent user actions. Check obvious alternative causes such as the wrong clock or a full disk. With signs of active ransomware, disconnect promptly while continuing the investigation.
Quarantine means separating the affected device from the network: unplug Ethernet and disable Wi-Fi. Avoid connecting removable drives that may carry infection away. Mark any media used for transfers for scanning or sanitization afterward. Isolation limits spread and further data transfer; it does not remove malware already present.
Remove contaminated restore points
Before cleaning, disable System Restore on a Windows PC that uses it, according to policy. Existing restore points are deleted because they may retain malware. System Restore records selected system state; it is not the user’s separate data-backup service. Record this action so protection can be restored at the right time.
Remediate with current tools
- Update the anti-malware engine and definitions. For an isolated PC, use a trusted update package obtained on a clean device and approved transfer media.
- Scan and remove using an appropriate environment. Safe Mode starts a limited set of Windows components. A preinstallation environment, trusted boot media or Defender Offline operates away from the normal infected session.
- Inspect startup entries, scheduled tasks and browser extensions for persistence, the settings that relaunch unwanted code.
- Rescan and test the original symptoms. Investigate an infection that returns instead of treating each new alert as unrelated.
A rootkit can hide from tools inside ordinary Windows. A clean quick scan alone does not explain persistent signs.
Rebuild when trust cannot be restored
If a rootkit, ransomware or returning infection cannot be removed with confidence, wipe and reinstall from a clean operating-system source or approved company image. Restore user data from a backup checked for infection. Firmware compromise can also need manufacturer-approved firmware recovery; reinstalling Windows does not replace firmware.
Reimaging is a recovery method, but secure wiping remains necessary where old data must be sanitized. Keep clean backups separate from the infected system so the recovery copy is not encrypted or altered along with live files.
Restore protection and finish the handover
Schedule regular scans and install operating-system, application and definition updates. Re-enable System Restore and create a new clean restore point after cleanup. Creating it too early can preserve the infection again.
If spyware, a keylogger or credential theft was involved, change affected passwords from a clean device and address account access. Teach the user the relevant prevention step, such as obtaining updates from the real vendor page instead of a pop-up. Document findings, isolation, tools, results, recovery source and final checks in the ticket before handing the device back.
Key Takeaways
- Investigate and quarantine before cleanup; urgent spread requires prompt isolation.
- Disable System Restore before cleaning on Windows systems that use it.
- Update tools before scanning and inspect persistent startup routes.
- Rebuild from trusted media when reliable removal is not possible.
- Update and schedule protection before creating a new clean restore point.
- Finish with user guidance and a clear ticket record.
6.3 Prevention tools and safe browser settings
Prevention combines tools that catch different stages of an attack. Antivirus checks software, email filtering screens delivery, the host firewall limits connections, and users can recognize suspicious requests. Keep each control current so one missed threat meets another check.
Recognize the tools’ roles
Signature detection matches known threat patterns and needs definition updates. Heuristic or behavior-based detection looks for suspicious actions, such as rapid encryption of many documents, including threats without a known file signature.
Endpoint detection and response (EDR) records activity on devices, detects suspicious behavior and supports actions such as remote isolation. Managed detection and response (MDR) supplies an outside team to run detection and response. Extended detection and response (XDR) connects information from endpoints, email, networks and cloud identities. These are related capabilities and services, not three interchangeable names for antivirus.
An email security gateway checks spam, phishing, attachments and links before delivery, sometimes testing files in a sandbox. Filtering can miss convincing requests, especially link-free payment fraud. User training and prompt reporting remain useful.
Trust the download route and verify the file
Get software from its vendor or an official app store. A pop-up claiming a browser update is not a trusted distribution route. If a vendor publishes a SHA-256 hash, calculate the downloaded file’s hash in PowerShell:
Get-FileHash .\setup.exe -Algorithm SHA256
Alternatively, use certutil -hashfile setup.exe SHA256. Compare all 64 hexadecimal characters against the value obtained through the trusted vendor route. A mismatch means the file is different or damaged: do not run it. A matching hash from an attacker-controlled page would only confirm agreement with that page, so the reference’s origin matters.
Maintain the browser
Leave automatic updates enabled and restart when needed to finish them. Install only needed extensions from official stores and trusted publishers. Inspect requested permissions: “Read and change all your data on all websites” grants broad access. Remove unknown or unused extensions. Organizations can control extension and feature settings centrally.
Keep pop-up blocking enabled. An approved ad blocker can also reduce malicious-ad exposure. Clearing cache and browsing data can fix display problems and remove local stored data on shared computers. Check proxy settings when unexplained redirects suggest traffic is being rerouted.
Secure DNS, commonly DNS over HTTPS, encrypts name lookups. A filtering DNS provider can also block known harmful domains. Encryption of the lookup and filtering of its answer are separate functions.
Interpret privacy and connection indicators
HTTPS with a valid certificate secures a connection to the named domain; the owner can still operate a fraudulent site. A certificate warning can indicate a wrong name, expired certificate, untrusted issuer or interception. Investigate it, especially before sign-in or payment.
Private browsing limits the history, cookies and form data retained locally after the private session closes. Websites, employers, network operators and internet providers may still observe activity; downloads can remain on disk. It provides no malware protection.
Browser sync can copy passwords, bookmarks and history to other signed-in devices. Protect the sync account with MFA, and avoid personal sync on shared or public computers.
Key Takeaways
- Signatures find known patterns; behavior detection examines suspicious actions.
- EDR is an endpoint capability, MDR adds a service team, and XDR connects several data sources.
- Check downloads and published hashes through trusted vendor routes.
- Keep browsers updated and extension permissions limited.
- HTTPS protects a connection, while private browsing limits local retention; neither makes a site safe.
Endpoint Security for Support Technicians examples
1Investigate a convincing fake update
12 steps
- 1IntroductionStart with the report
A user installed a “required browser update” from a pop-up. Now unfamiliar programs appear and the computer is unusually busy. Begin by separating how the software arrived from what it does. Those questions explain why one incident can have several malware names. You will also check the message that delivered it and the weaknesses that helped it succeed.
- 2ExplanationName the delivery route
A trojan hides a harmful purpose behind useful-looking software. A virus instead inserts code into a host file and runs with it; a worm spreads independently across a network. The fake update persuaded a person to install it, so the delivery fits a trojan. That tells you about the disguise, but you still need evidence about its activity.
- 3ExampleRead the activity
Task Manager shows sustained processor use while the user is idle. This could fit a cryptominer, which consumes processing power for someone else. It can also have an ordinary cause, so identify the process and investigate. If a fake installer delivered a miner, “trojan” describes its entry and “cryptominer” describes its purpose.
- 4ChallengeClassify a changed outcome
Suppose the fake utility instead encrypts documents and displays a payment demand. How would you describe its entry and its effect?
---reveal---
Its entry is a trojan, because it disguised its purpose to gain installation. Its effect is ransomware, because it locks files for a demand. Disconnect promptly to limit harm to shares and synced folders, then follow recovery procedures.
- 5Key InsightA clean result can need follow-up
A rootkit can hide activity by changing the system interfaces or components that report it. Fileless malware may run mainly in memory and use tasks or registry settings to return. A normal scan is useful, but a clean result does not settle persistent symptoms. An offline view and behavior-based detection answer different parts of that problem.
- 6ExampleInspect the update message
The user also received an email saying “Update now or lose access.” The sender’s display name looks like the help desk, but the destination is
https://signin.oakdesk.example/upgrade, while the employer usesoak.example. Read the actual hostname and compare it with the known service address. Familiar words and urgent wording do not establish identity. - 7ExplanationChoose an independent check
Do not open the link to test whether the message is real. Report it through the approved route and open the service from a known bookmark if you need to check account status. For a payment change, call an established contact number. A callback number supplied by the same suspicious request cannot independently verify who sent it.
- 8ChallengeHandle an urgent caller
A caller claiming to be the operations director asks for an immediate password reset and says there is no time for verification. What should support do first?
---reveal---
Use the approved identity-verification process, such as a directory callback. Authority and urgency can be imitated. Do not ask for the current password or accept caller ID as sufficient proof.
- 9ExplanationConnect access to the weakness
An outdated browser offers a software vulnerability; a deceptive update prompt offers a social-engineering route. An attacker can use both. Install available fixes and remove unsupported software. For a zero-day without a fix, restricted user rights, firewalls and behavior detection still help limit exposure while a vendor update is prepared.
- 10ChallengeDistinguish the password attack
The attacker next tries an email/password pair leaked from an unrelated forum at the employer’s sign-in. What technique is this, and what habit makes it succeed?
---reveal---
It is credential stuffing. Reusing the forum password for work lets an already known pair work again. Unique passwords prevent that reuse route; MFA adds another check if a password is exposed.
- 11ChallengeExplain why the warning still matters
The user says the fake update page had HTTPS and appeared after joining a familiar public Wi-Fi name. Why do those details fail to establish trust?
---reveal---
HTTPS secures the connection to the named domain, including an attacker’s domain. An evil twin can copy a legitimate SSID. Check the domain and network through trusted routes and investigate certificate warnings; those two familiar indicators do not validate the update request.
- 12RecapCarry forward the useful distinctions
Identify the delivery mechanism, then the behavior and damage. Inspect suspicious requests through independent routes and preserve the normal identity checks under pressure. Relate the attack to exposed software, reused credentials or a false network identity so the response addresses the cause as well as the visible symptom.
2Prepare a new employee’s sign-in
13 steps
Save this lesson to follow every Walkthrough step by step.
- 1IntroductionBuild access around the job
- 2ExplanationChoose a secret that survives one breach
- 3ExampleExplain the policy
- 4ChallengeFix a reuse problem
- 5ExplanationAdd an independent factor
- 6ExampleEnroll a practical backup
- 7ChallengeRespond to the lost phone
- 8ExampleKeep everyday rights limited
- 9ExplanationElevate the installation
- 10ChallengeInterpret a Hello PIN
- 11TipCheck the managing policy
- 12ChallengeClose two access gaps
- 13RecapCheck access and recovery together
3Repair access without opening the whole PC
14 steps
Save this lesson to follow every Walkthrough step by step.
- 1IntroductionKeep protection during the repair
- 2ExplanationCheck the security provider
- 3ExampleChoose a scan with purpose
- 4ExampleFind the narrow firewall rule
- 5ChallengeAvoid a public-network exposure
- 6ExampleSeparate local from network access
- 7ExampleChange the blocking layer
- 8ChallengeResolve the file-move surprise
- 9Key InsightRead precedence accurately
- 10ExplanationRemove unnecessary access
- 11ChallengeProtect the boot route
- 12TipFinish security updates
- 13ChallengeExplain two different outcomes
- 14RecapVerify the repaired behavior
4Recover an encrypted laptop and prepare its old drive
12 steps
Save this lesson to follow every Walkthrough step by step.
- 1IntroductionFollow data through two decisions
- 2ExplanationRead both status fields
- 3ExamplePrepare for firmware maintenance
- 4ExampleUse the recovery screen
- 5ChallengeProtect an EFS file before profile removal
- 6Key InsightEncryption does not lock a live session
- 7ExplanationDefine the disposal result
- 8ExampleAccount for the SSD controller
- 9ChallengeCheck the erase claim
- 10TipPlan for a failed sanitization
- 11ChallengeJudge the handover record
- 12RecapKeep the right access at each stage
5Secure a small workplace and its mobile users
15 steps
Save this lesson to follow every Walkthrough step by step.
- 1IntroductionPlan two networks and mobile access
- 2ExplanationCheck compatibility before choosing a mode
- 3ExampleFit access to the staff pattern
- 4ChallengeRevoke one user cleanly
- 5ExplanationSecure router administration
- 6ExampleSet guest access and test it
- 7TipRemove convenience openings
- 8ChallengeExplain a remaining guest risk
- 9ExplanationPrepare the phone’s local protection
- 10ExampleEnroll the work configuration
- 11TipPrepare locator and backup access
- 12ExampleHandle the missing phone
- 13ChallengeRespect personal ownership
- 14ChallengeFind two independent configuration gaps
- 15RecapVerify each boundary
6Return an infected workstation safely
14 steps
Save this lesson to follow every Walkthrough step by step.
- 1IntroductionTurn a symptom report into a repair
- 2ExampleVerify the pattern
- 3ChallengeCheck an ordinary explanation
- 4ExplanationQuarantine the affected workstation
- 5ExampleRemove old restore points
- 6ExampleUpdate the scanning tools
- 7ExampleClean away from the normal session
- 8ChallengeChoose a dependable recovery route
- 9ExampleRestore protection in order
- 10ExplanationClose the route that delivered it
- 11ChallengeCheck a changed download
- 12Key InsightUse each prevention tool for its job
- 13ChallengeDecide whether handover is complete
- 14RecapCheck the result against the report
Endpoint Security for Support Technicians practice questions
Set 1: Threats, passwords and identity checks10 Practice Questions
Question 1 of 10
Show answerHide answer
Question 2 of 10
Show answerHide answer
Question 3 of 10
Show answerHide answer
Question 4 of 10
Show answerHide answer
Question 5 of 10
Show answerHide answer
Question 6 of 10
Show answerHide answer
Question 7 of 10
Show answerHide answer
Question 8 of 10
Show answerHide answer
Question 9 of 10
Show answerHide answer
Question 10 of 10
Show answerHide answer
Set 2: Windows protection and effective access10 Practice Questions
Save this lesson to see every answer and practice every set.
Question 1 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 2 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 3 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 4 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 5 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 6 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 7 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 8 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 9 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 10 of 10
Show answerHide answer
Save this lesson to see this answer.
Set 3: Encryption, disposal and wireless choices10 Practice Questions
Save this lesson to see every answer and practice every set.
Question 1 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 2 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 3 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 4 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 5 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 6 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 7 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 8 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 9 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 10 of 10
Show answerHide answer
Save this lesson to see this answer.
Set 4: Mobile devices and reliable malware recovery10 Practice Questions
Save this lesson to see every answer and practice every set.
Question 1 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 2 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 3 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 4 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 5 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 6 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 7 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 8 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 9 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 10 of 10
Show answerHide answer
Save this lesson to see this answer.
Set 5: Connected decisions across support tasks10 Practice Questions
Save this lesson to see every answer and practice every set.
Question 1 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 2 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 3 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 4 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 5 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 6 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 7 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 8 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 9 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 10 of 10
Show answerHide answer
Save this lesson to see this answer.
Set 6: Diagnose failures and justify the next action10 Practice Questions
Save this lesson to see every answer and practice every set.
Question 1 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 2 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 3 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 4 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 5 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 6 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 7 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 8 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 9 of 10
Show answerHide answer
Save this lesson to see this answer.
Question 10 of 10
Show answerHide answer
Save this lesson to see this answer.
Stuck on your own question? Homework Help
Key Terms
A
Account lockout
Administrator
Antivirus exclusion
Application spoofing
Attack surface
Authentication
AutoPlay
B
Behavior-based detection
BitLocker
BitLocker recovery key
BitLocker To Go
Bring your own device (BYOD)
Browser hijacker
Brute-force attack
Business email compromise (BEC)
C
Chain of custody
Clear
Client isolation
Configuration profile
Credential stuffing
Cryptographic erase
Cryptominer
D
Data at rest
Defender Offline
Degaussing
Destroy
Dictionary attack
Distributed denial of service (DDoS)
DNS over HTTPS
Dumpster diving
E
Effective access
Email security gateway
Encrypting File System (EFS)
End of life (EOL)
Endpoint detection and response (EDR)
Evil twin
Explicit permission
Extended detection and response (XDR)
F
File attribute
Fileless malware
FileVault
Firewall profile
G
Group Policy
Guest network
H
Hardening
Hash
Host firewall
Hosts file
I
Inheritance
J
Jailbreaking
K
Kerberos
Keylogger
L
Local account
M
MAC address filtering
Malware
Managed detection and response (MDR)
Media sanitization
MFA fatigue
Microsoft Defender Antivirus
Microsoft Entra ID
Mobile device management (MDM)
Multifactor authentication (MFA)
N
NTFS permissions
O
On-path attack
P
Passphrase
Password expiration
Password history
Password manager
Patch management
Persistence
Personally identifiable information (PII)
Phishing
Port forwarding
Potentially unwanted program (PUP)
Preinstallation environment
Purge
Q
Quarantine
R
RADIUS
Ransomware
Reimaging
Remote wipe
Rooting
Rootkit
S
Safe Mode
Scareware
Screened subnet
Secure Boot
Selective wipe
Share permissions
Shoulder surfing
Signature detection
SIM swapping
Simultaneous Authentication of Equals (SAE)
Single sign-on (SSO)
Smishing
Social engineering
Spear phishing
Spoofing
Spyware
SSID
Stalkerware
Standard user
System Restore
T
TACACS+
Tailgating
Tamper protection
Task Manager
Time-based one-time password (TOTP)
TKIP
Trojan
Trusted Platform Module (TPM)
U
Universal Plug and Play (UPnP)
User Account Control (UAC)
V
Virus
Vishing
Vulnerability
W
Wear leveling
WEP
Whaling
Wi-Fi Protected Setup (WPS)
Windows Hello
Worm
WPA2
WPA3
Z
Zero-day attack
#
802.1X
About this lesson
Make your own Study Materials
Turn your notes, slides and documents into Study Guides, Practice Questions, Flashcards and 6 more tools.