Today there was an interesting VISA BlackPOS informational webinar today.
What I got out of it is some more information to make sure and keep in mind these items when looking for Indicators of Compromise(IOC).
VISA¹ has a great program to help small businesses protect themselves against cyber attacks
There were a lot of good cybersecurity information tidbits, and I want to focus on Logging and indicators of compromise(IOC).
The Attack characteristics are similar to other malware like cryptowall.
The Initial attack vectors need to be reviewed to check our logs for IOC’s
- remote access scenarios
- Internet facing systems with weak authentication
- Botnet infection
- exfiltration occurs via ports/services commonly associated with data transfers.
- ICMP — TLS/HTTPS — NetBIOS — SSH — FTP/SFTP
We have to create a baseline and then do checks on the traffic.
One more slide was most interesting:
During the verbal Q&A there was an interesting item that kept coming up – It is outgoing ftp traffic is most used by the malware industry to send information to their control servers (also called command and control).
So we need to review and check ftp outgoing traffic.
How many times are you really going to upload ftp files for your job in all positions?
If you answer that in the single digits then it is easy to set up an analysis log point.
We must have new methods of finding the IOCs.
Of course the initial method of compromise is also improtant
VISA finds that a lot of their merchants that get compromised have the following problems:
- remote Access applications use singlefactor authentication
- Passwords either use default settings or are easily guessed
- Attackers are not restricted from known attackers in east Europe or elsewhere
- Security controls or encryption is not used
Yesterday’s blogpost discussed the Log analysis review and scripting
So the first thing we need to do is create a baseline with ftp outgoing and then add all ftp outgoing as alerts. Review all outgoing ftp alerts weekly.
Contact US Tony Zafiropoulos 314-504-3974
1 thought on “What To Look For In Logs: Hackers Being Successful”