Stopping an Attack
Part of the Security Fundamentals section of Coddy's Cybersecurity journey. Lesson 2 of 43.
When someone connects to Lumen, the connection comes from an IP address, such as 192.0.2.7. An alert lists each address the sign-in attempts come from, with how many of them failed. The console beside the terminal shows that list. On a phone, it is in the Console tab.
For example, suppose the alert shows hundreds of failed sign-ins from 192.0.2.7. You can stop new connections from that address with:
seclab block 192.0.2.7You should see:
Blocked 192.0.2.7 at the company's edge.192.0.2.7 is only the example. In the ticket, the attacker's real address is in the console's alert, under Where the attempts come from. Click it to put it in your command.
During an attack, each change you make takes one minute of company time. Below the result, seclab lists what happened in that minute, under a line such as Then, from 09:12 to 09:13. Read it to see whether the attempts stopped.
The block stops new attempts from that address. It does not block everyone else. Before blocking an address, check how it was used: a coworker who mistyped their password once should still be able to sign in. If you block a coworker by mistake, seclab unblock followed by their address removes the block.
Challenge
EasyTicket from Sam, IT lead
Someone is guessing passwords on our mail server right now. Find the address in the alert and block it, and only that one.
Try it yourself