Ready to Start Your Career?
April 3, 2017
A Penetration Testing Checklist For Linux Machine – Intrusion Discovery
April 3, 2017
April 3, 2017
Since we already discussed A Penetration Testing Cheat Sheet For Windows Machine – Intrusion Detection, here we will see the most important Linux machine pen testing checklist on an occasional premise (day by day, week by week, or each time you log on to a framework you oversee) gone through these anomalous behaviours to search for strange conduct that may be caused by a computer intrusion. Each of these commands runs locally on a system.
• Unusual Accounts
• Unusual Log Entries
• Unusual Processes and Services
• Unusual Files
• Unusual Network Usage
• Unusual Scheduled Tasks
• Other Unusual Items
1.Unusual Accounts:Look in /etc/passwd for new accounts in sorted list by UID: # sort –nk3 –t: /etc/passwd | less Normal accounts will be there, but look for new, unexpected accounts, especially with UID < 500.Also, look for unexpected UID 0 accounts:# egrep ‘:0+:’ /etc/passwd On systems that use multiple authentication methods:# getent passwd | egrep ‘:0+:’Look for orphaned files, which could be a sign of an attacker’s temporary account that has been deleted.# find / -nouser -print
2.Unusual Log Entries:Look through your system log files for suspicious events, including:
- “entered promiscuous mode”
- Large number of authentication or login failures from either local or remote access tools (e.g., telnetd, sshd, etc.)
- Remote Procedure Call (rpc) programs with a log entry that includes a large number (> 20) strange characters (such as ^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM)
- For systems running web servers: Larger than normal number of Apache logs saying “error”
- Reboots and/or application restarts
3.Unusual Processes and Services:Look at all running processes:# ps –auxGet familiar with “normal” processes for the machine. Look for unusual processes. Focus on processes with root (UID 0) privileges.If you spot a process that is unfamiliar, investigate in more detail using:# lsof –p [pid]This command shows all files and ports used by the running process.If your machine has it installed, run chkconfig to see which services are enabled at various run levels:# chkconfig – -list
4.Unusual Files:Look for unusual SUID root files:# find / -uid 0 –perm -4000 –printThis requires knowledge of normal SUID files.Look for unusual large files (greater than 10 MegaBytes):# find / -size +10000k –printThis requires knowledge of normal large files. Look for files named with dots and spaces (“…”, “.. “,“. “, and ” “) used to camouflage files:# find / -name ” ” –print# find / -name “.. ” –print# find / -name “. ” –print# find / -name ” ” –printLook for processes running out of or accessing files that have been unlinked (i.e., link count is zero). An attacker may be hiding data in or running a backdoor from such files:# lsof +L1On a Linux machine with RPM installed (RedHat, Mandrake, etc.), run the RPM tool to verify packages:# rpm –Va | sortThis checks size, MD5 sum, permissions, type, owner, and group of each file with information from RPM database to look for changes. Output includes:S – File size differsM – Mode differs (permissions)5 – MD5 sum differsD – Device number mismatchL – readLink path mismatchU – user ownership differsG – group ownership differsT – modification time differsPay special attention to changes associated with items in /sbin, /bin, /usr/sbin, and /usr/bin.In some versions of Linux, this analysis is automated by the built-in check-packages script.
5.Unusual Network Usage:Look for promiscuous mode, which might indicate a sniffer:# ip link | grep PROMISCNote that the ifconfig doesn’t work reliably for detecting promiscuous mode on Linux kernel 2.4, so please use “ip link” for detecting it.Look for unusual port listeners:# netstat –napGet more details about running processes listening on ports:# lsof –iThese commands require knowledge of which TCP and UDP ports are normally listening on your system. Look for deviations from the norm.Look for unusual ARP entries, mapping IP address to MAC addresses that aren’t correct for the LAN:# arp –aThis analysis requires detailed knowledge of which addresses are supposed to be on the LAN. On a small and/or specialized LAN (such as a DMZ), look for unexpected IP addresses.
6.Unusual Scheduled Tasks:Look for cron jobs scheduled by root and any other UID 0 accounts:# crontab –u root –lLook for unusual system-wide cron jobs:# cat /etc/crontab# ls /etc/cron.*
7.Other Unusual Items:Sluggish system performance:$ uptime – Look at “load average”Excessive memory use:$ freeSudden decreases in available disk space:$ dfIf you spot anomalous behavior: DO NOT PANIC!Your system may or may not have come under attack. Please contact the Incident Handling Team immediately to report the activities and get further assistance.
Build your Cybersecurity or IT Career
Accelerate in your role, earn new certifications, and develop cutting-edge skills using the fastest growing catalog in the industry