No Hacking Back
Part of the Security Fundamentals section of Coddy's Cybersecurity journey. Lesson 36 of 43.
Suppose an attack comes from an outside server. It might be tempting to break into that server and shut it down. This is called hacking back. The server may actually belong to another victim whose system the attacker took over.
Lumen's permission to defend its own systems does not give you permission to break into someone else's. If a coworker requests that action, deny it:
seclab request retaliate denyYou should see:
Denied request retaliate.You can still protect Lumen, save the logs and report what happened. If the owner has approved a separate request to save the evidence, approve that work:
seclab request keep-evidence approveYou should see:
Approved request keep-evidence.Judge each request by the permission it has. Refusing to attack the outside server does not mean refusing the legitimate work needed to investigate.
Challenge
EasyTicket from Dana, CEO
Lee wants to take the outside server offline. Sam has a separate request to save the logs and report the attack. Read both requests and my approval notes. Deny the work we have no permission to do and approve the allowed work. Keep the earlier decisions and leave Lee's account active.
Try it yourself
All lessons in Security Fundamentals
1The First Alert
What Is CybersecurityStopping an AttackLog LinesStolen PasswordsMulti-Factor AuthenticationThe CIA TriadBack for More