NewAI Content Creation is now live in Early Access
Turning Point Training Instituteby Training Center
Skip to content
0%
Module 10 — Operating System, Software and Account TroubleshootingLesson 3 of 4
Video lesson

Passwords, Permissions, Malware and Escalation

BeginnerVideo lesson
10 min readBeginner

Where you are: Module 10 — Operating System, Software and Account Troubleshooting · Lesson 10.3 · Based on Chapter 10 (§10.4–10.5) of Dr. Tahseen Al Doori's Troubleshooting Essentials.

What you'll be able to do

  • Diagnose the common login, password and account problems from their symptoms.
  • Handle "access denied" messages through the right people and processes.
  • Explain and follow the rule that passwords are never requested or shared during troubleshooting.
  • Recognise the symptoms of malware and respond correctly to a ransom message: isolate, do not pay or interact, escalate.

Watch: Passwords, Permissions, Malware and Escalation

The video follows a fictional new starter whose correct password keeps being rejected, and who offers to tell the technician what it is. It works through the book's account table, solves the case without any password being shared, and then covers malware symptoms and the response to a ransom message. While watching, consider:

  • Why is "I'll just tell you my password" an offer a professional always declines?
  • How can a correct password be rejected?
  • What are the three things you do, and the things you must not do, when a ransom message appears?

Login, password and account problems

Most account faults have ordinary causes. The book's table matches symptoms to their likely causes and actions:

SymptomLikely causeAction
"Incorrect password"Caps Lock, keyboard layout, old passwordCheck Caps Lock and layout; type the password in a visible field to test
Account lockedToo many failed attemptsWait for the lockout period or ask an administrator
Password expiredPassword policyReset through the approved process
Login fails on one device onlySaved old credentials, clock wrongUpdate saved credentials; correct the date and time
"Access denied" to a file or folderPermissionsVerify group membership with the administrator

Some notes on applying it:

  • The visible-field test is done by the user, privately: they type the password somewhere they can see it, such as a blank document, to check whether Caps Lock or the keyboard layout is changing the characters, then delete it. You do not look, and it is never typed into a ticket, chat or email.
  • Keyboard layout matters because some symbols sit on different keys in different layouts. A password containing one of those symbols is typed wrongly every time, even though the user is pressing the "right" keys.
  • Lockouts exist to stop password-guessing attacks. Repeated attempts make it worse; stop and wait, or contact an administrator.
  • "Fails on one device only" usually means an old password saved in that device or application, as in the email example from Module 3, or a wrong clock. Incorrect date and time break logins and secure websites (Module 5).
  • "Access denied" is the system working as designed. Permissions are granted through group membership, so the administrator, not the troubleshooter, decides whether the user should have access.

The security reminder

Never share passwords during troubleshooting, and never ask users to tell you theirs. Use approved reset processes and remote-support tools that do not expose credentials.

There are three reasons this rule is absolute. First, a password known to two people no longer proves who did what. Second, a help desk that asks for passwords trains users to give them to anyone who claims to be from IT, which is exactly what attackers rely on. Third, you never need it: every legitimate task can be done with an approved reset, an administrator's own account, or a remote-support tool where the user signs in themselves.

The same reasoning applies to permissions. Never work around "access denied" by borrowing another person's account, copying files to a location the user can reach, or using your own elevated access on someone else's behalf. Verify the need with the administrator, and let the approved process grant it.

Malware symptoms

Malware (malicious software) includes viruses, spyware and ransomware. The book lists the symptoms to watch for:

  • Pop-ups, especially ones that keep returning.
  • Unknown programs that nobody remembers installing.
  • Browser redirects, where one address leads somewhere else.
  • Security software that has been disabled.
  • Unusual network activity, such as heavy traffic when nothing should be running.
  • Sudden slowness.

Any one of these can have an innocent explanation, but several together, or any sign that security software has been turned off, should be treated as a possible security incident rather than an ordinary fault.

Ransomware: isolate, do not interact, escalate

Ransomware encrypts files and demands payment to release them. The book is clear that a ransom message demands immediate escalation.

Isolate the deviceDo not pay or interactReport to IT securitySpecialist remediation
  1. Disconnect the affected device from the network to prevent the infection spreading: unplug the network cable and turn off Wi-Fi.
  2. Do not pay or interact with the message. Do not click links, reply, or follow its instructions.
  3. Report it to IT security immediately, with the time you first saw the message and what you have done since.
  4. Leave remediation to specialists. The book notes that a full scan with up-to-date security software should be run only where policy allows, and that serious infections require specialist remediation.

Ransomware also appears in the book's escalation triggers (Module 13): it is a data-loss risk and a security incident. Your role is to contain it and hand it over, not to fix it alone.

Beyond the book (2026 note): The UK's National Cyber Security Centre states that law enforcement do not encourage, endorse or condone the payment of ransom demands, and warns that paying gives no guarantee you will regain access to your data or computer, that the computer will still be infected, and that payment funds criminal groups. It also advises keeping backups that are not permanently connected to the network, and connecting them only to known clean devices before recovery (Mitigating malware and ransomware attacks, NCSC).

Worked example

(Fictional scenario.) A new starter in the sales team reports that the system keeps saying their password is incorrect, although they are certain it is right. They are using a keyboard borrowed from another desk, and they offer to tell the technician the password.

  1. Identify. The technician declines the offer politely and explains that the support desk never needs it. Message: "The password is incorrect". Scope: this laptop only; the user signed in successfully on their phone's email that morning.
  2. Theory. From the book's table: Caps Lock, keyboard layout or an old password. The borrowed keyboard makes layout a strong candidate.
  3. Test. Caps Lock is off. The language bar shows a US keyboard layout instead of the UK layout the user expects. The user privately performs the visible-field test in a blank document and sees that one symbol in their password comes out as a different character. They delete the text.
  4. Plan and implement. Switch the input layout back to UK. One change.
  5. Verify. The user signs in successfully. No password was shared, reset or written down.
  6. Document. The ticket records the cause (keyboard layout changed when the borrowed keyboard was connected) and the fix, so the next technician can spot it faster.

Try it

A paper triage exercise; no real accounts are involved.

For each fictional report, write the most likely cause from the book's table, your first action, and whether it needs escalation:

  1. "It says my account is locked. I've tried my password about ten times."
  2. "I can log in on my desktop, but my laptop says my password is wrong. I changed it on Friday."
  3. "I get 'Access denied' when I open the Finance shared folder. Can you give me your login so I can finish my report?"
  4. "Lots of pop-ups appeared and my antivirus has turned itself off."
  5. "My screen says all my files are encrypted and I must pay within 48 hours."

You have finished when all five reports have a cause, a first action and an escalation decision, and your answers to reports 3 and 5 explicitly follow the security reminder and the ransomware response.

Knowledge check

A user offers to tell you their password so you can test their login. What should you do?

A user can sign in on their desktop but not on their laptop, a few days after changing their password. What is the most likely cause?

A user gets 'Access denied' when opening a shared folder. What is the correct action?

A user's screen shows a ransom demand. What should you do first?

Which combination of symptoms should most clearly be treated as a possible malware incident?

Answers explained

  1. b — passwords are never requested or shared, with or without deleting notes, emailing or a manager's approval; approved processes make it unnecessary.
  2. a — "fails on one device only" after a password change points to old saved credentials (or a wrong clock); a deleted account would fail everywhere, and a switch or ransomware would show other symptoms.
  3. d — permissions are decided through group membership by the administrator; copying files, using your own access or lending accounts all bypass the control and break the security reminder.
  4. c — isolate to stop the spread and escalate to IT security; paying, restarting and asking for passwords are all explicitly wrong.
  5. a — these are three of the book's malware symptoms together, including disabled security software; the other options are account, driver and Wi-Fi faults with ordinary causes.

Key takeaways

  • Most login faults come from Caps Lock, keyboard layout, lockouts, expiry, saved old credentials or a wrong clock.
  • "Access denied" is resolved by the administrator through group membership, never by workarounds.
  • Never ask for a password and never share one; use approved reset processes.
  • Treat malware symptoms as a security incident; for ransomware, isolate, do not pay or interact, and escalate to IT security.

Sources