Contain, Don't Destroy
Part of the Security Fundamentals section of Coddy's Cybersecurity journey. Lesson 39 of 43.
Stopping an attack from causing more damage is called containment. For an affected employee account, you can temporarily disable it while you investigate what happened. For example, if an attacker is using Ava's account, run:
seclab disable avaYou should see:
Disabled ava. They can no longer log in.Now check whether any sessions remain open:
seclab sessions avaYou should see:
ava is not signed in anywhere.Nobody is signed in as Ava anymore. Her account and group memberships still exist, so you can investigate and later restore her access. Deleting the account would remove those memberships too.
Only stop access for the affected account. Other employees should be able to keep working. In the next lesson, you will deal with accounts that the attacker created for themselves.
Challenge
EasyTicket from Sam, IT lead
The laptop checks found a second employee whose browser session was copied before the alarm. Find the account in the new evidence and disable it, keeping its record and groups. Leave the first affected account disabled. Keep unaffected staff and the approved backup service working.
Try it yourself
All lessons in Security Fundamentals
1The First Alert
What Is CybersecurityStopping an AttackLog LinesStolen PasswordsMulti-Factor AuthenticationThe CIA TriadBack for More4Passwords
Long PasswordsCommon PasswordsPassword SprayingMorning CleanupCredential StuffingMFA FatigueThe Password Review7Incident Response
Incident ResponseContain, Don't DestroyWhat They Left BehindRecoveryThe Incident ReportThe Night Alert