CIT 380: Securing Computer Systems

1. CIT 380: Securing Computer Systems Forensics CIT 380: Securing Computer Systems

2. Computer Forensics • Forensic Toolkit • Live Data Collection • Forensic Duplication • Network Data Collection • Evidence Handling • Disk Data Analysis • UNIX Forensics • Network Data Analysis CIT 380: Securing Computer Systems

3. Forensic Toolkit Forensic investigation required trusted set of tools to collect and analyze data. Hardware/Media: • CD-ROM containing tools. • USB drive or portable hard drive saving collected data. • Laptop for network data collection and/or saving larger quantities of data. • Secure data analysis workstation • Hard drive space for analyzing drive images. • Drive bays and controllers for analyzing multiple types of hard disks. CIT 380: Securing Computer Systems

4. Forensic Toolkit Software bash: known good copy of shell (cmd.exe for Win) dd: create bit level images of disks find and ls: examine directory listings ifconfig: network configuration (ipconfig for Win) lsmod: list loaded kernel modules (modinfo for Sun) lsof: list open files (and network connections) md5sum: generate/validate file checksums netcat or cryptcat: save collected data via network netstat: collect status of network connections ps: collect process data (pslist for Win) script: records terminal session strace: system call tracer (truss for Sun) strings: list text strings in binaries vim: edit and/or view binary/text files CIT 380: Securing Computer Systems

5. Forensic Toolkit Software Live CD toolkits • FIRE: Forensic & Incident Response Environment • Helix Forensics CD: Contains Sleuthkit. Specialized Forensics Tools • Sleuthkit (http://www.sleuthkit.org/) • Includes Autoposy Forensic Browser. • The Coroner’s Toolkit • http://www.porcupine.org/forensics/tct.html • Encase, FTK • Commercial MS Windows toolkit. CIT 380: Securing Computer Systems

6. Live Data Collection • In-memory system state is volatile and must be collected before system is shutdown. • These types of data will be lost on shutdown: • Running processes. • Open network connections. • Deleted binaries whose programs are still executing. • Deleted files in use by a running program. • Caveat: Even using tools from CD-ROM will modify system state, both memory (perhaps including swap) and disk files. CIT 380: Securing Computer Systems

7. Saving Live Data Floppy drive • small but ubiquitous. USB drive • larger but not on older systems. Network storage • Use netcat listener on remote host. • nc –l –p 2222 >output • Pipe to netcat on machine you’re investigating: • /mnt/cdrom/bin/date | /mnt/cdrom/bin/nc –w 3 destIP 2222 • Use cryptcat or pipe through DES for security. CIT 380: Securing Computer Systems

8. Live Data Procedure • Mount forensic toolkit media • mount –n /mnt/cdrom • Start trusted shell • /mnt/cdrom/bin/bash • export PATH=/mnt/cdrom/bin • Record current date • date • ARP and route cache tables • arp –an • route -Cn CIT 380: Securing Computer Systems

9. Live Data Procedure • Logged-in users • w • File-modification times • atime: ls –alRu / • ctime: ls –clRu / • mtime: ls –alR • Open network connections/sniffers • ifconfig -a • netstat –anp • Physical memory image • dd if=/proc/kcore | nc remoteIP port CIT 380: Securing Computer Systems

10. Live Data Procedure • Kernel modules and symbols • cat /proc/modules • cat /proc/ksyms • For detecting hidden kernel modules, • insmod –f /mnt/cdrom/hunter.o • cat /proc/showmodules • Process list • ps aux • Memory image of suspicious processes: • pcat PID or • kill –STOP PID && gcore –o PID.img PID CIT 380: Securing Computer Systems

11. Live Data Procedure • Record system logs • utmp: current user access/accounting data • wtmp: historical user access/accounting data • lastlog: last access/login data • syslog files: • /etc/syslog.conf • /var/adm/messages or /var/log/messages • Application logs • Shell history files • Apache access_log • FTP xferlog CIT 380: Securing Computer Systems

12. Live Data Procedure • Save configuration files Authentication: /etc/passwd, /etc/shadow Scope of access: /etc/group Local machines: /etc/hosts Trust relationships: /etc/hosts.equiv,~/.rhosts TCP wrapper rules: /etc/hosts.allow, /etc/hosts.deny Syslog configuration: /etc/syslog.conf inetd/xinetd: /etc/inetd.conf, /etc/xinetd.conf, /etc/xinetd.d Startup files: /etc/inittab, /etc/rc* Scheduled events: /var/spool/cron/* CIT 380: Securing Computer Systems

13. Live Data Procedure • Find deleted files lsof: list open files Look for files named only by disk partition. Investigate /proc entries for processes # ls –al /proc/1403 dr-xr-xr-x 3 root root 0 Apr 22 04:09 . dr-xr-xr-x 78 root root 0 Apr 17 13:33 .. dr-xr-xr-x 2 root root 0 Apr 26 19:25 attr -r-------- 1 root root 0 Apr 26 19:25 auxv -r--r--r-- 1 root root 0 Apr 26 19:24 cmdline lrwxrwxrwx 1 root root 0 Apr 26 19:25 cwd -> / -r-------- 1 root root 0 Apr 26 19:25 environ lrwxrwxrwx 1 root root 0 Apr 26 19:25 exe -> /sbin/syslogd dr-x------ 2 root root 0 Apr 26 19:25 fd -r-------- 1 root root 0 Apr 26 19:25 maps -rw------- 1 root root 0 Apr 26 19:25 mem -r--r--r-- 1 root root 0 Apr 26 19:25 mounts lrwxrwxrwx 1 root root 0 Apr 26 19:25 root -> / -r--r--r-- 1 root root 0 Apr 26 19:24 stat -r--r--r-- 1 root root 0 Apr 26 19:25 statm -r--r--r-- 1 root root 0 Apr 26 19:24 status dr-xr-xr-x 3 root root 0 Apr 26 19:25 task -r--r--r-- 1 root root 0 Apr 26 19:25 wchan CIT 380: Securing Computer Systems

14. Live Data Procedure • Find deleted files (continued) exe link points to binary image file for process Can access binary via link even if file deleted cmdline file contains command line args cat cmdline fd directory lists all open files by file descriptor > ls -al fd total 7 dr-x------ 2 root root 0 Apr 26 19:25 . dr-xr-xr-x 3 root root 0 Apr 22 04:09 .. lrwx------ 1 root root 64 Apr 26 19:25 0 -> socket:[2715] l-wx------ 1 root root 64 Apr 26 19:25 2 -> /var/log/messages l-wx------ 1 root root 64 Apr 26 19:25 3 -> /var/log/secure l-wx------ 1 root root 64 Apr 26 19:25 4 -> /var/log/maillog l-wx------ 1 root root 64 Apr 26 19:25 5 -> /var/log/cron l-wx------ 1 root root 64 Apr 26 19:25 6 -> /var/log/spooler l-wx------ 1 root root 64 Apr 26 19:25 7 -> /var/log/boot.log CIT 380: Securing Computer Systems

15. Live Data Procedure • Record completion date. • Record your actions. history will list all of your commands script command will record all keystrokes and output of commands script /mnt/floppy/log.txt • Record secure checksums on files md5sum * >md5sums.txt CIT 380: Securing Computer Systems

16. Forensic Duplication Forensic Duplicate: File that contains every bit of information from source. Qualified Forensic Duplicate: A file or set of files that contains every bit of information in source, but which may be stored in altered format. • checksums • compression CIT 380: Securing Computer Systems

17. Forensic Duplication Restored Image: The result of restoring a qualified forensic duplicate to another medium. • Problems: Different drive geometries, partition tables. CIT 380: Securing Computer Systems

18. Forensic Duplication • Compare and record data checksum • md5sum /dev/hda == md5sum hda.img • Duplicating a drive to local media • dd if=/dev/hda of=/mnt/disk/hda.img conv=noerror,notrunc bs=16384 • Duplicating a drive across the network • dd if=/dev/had conv=noerror,sync | des –e –c –k password | nc –w 3 targetIP 2222 • nc –l –p 2222 | des –d –c –k password | dd of=hda.img CIT 380: Securing Computer Systems

19. Forensic Duplication Duplicating a drive to multiple files #!/bin/bash blocksz=20480k let count=1 while(dd if=/dev/hda of=/mnt/disk/hda.$count.img bs=$blocksz skip=($($count-1)) conv=noerror,notrunc) do echo “Block $count output.” count=$((count+1)) done CIT 380: Securing Computer Systems

20. Evidence Handling Original Evidence: original copy of evidence provided for client/victim. Best Evidence: duplication of evidence most closely linked to original evidence. Authentication of Evidence: testimony of evidence collector in court that evidence is what the proponent claims. CIT 380: Securing Computer Systems

21. Evidence Handling Chain of Custody • Evidence must be stored in tamperproof manner, where it cannot be accessed by unauthorized people. • Requirements: • Know location of evidence at all times. • Maintain custody of keys/passwords for access. • Document all receipts and transfers of evidence. • Provide testimony to defend evidence handling. • Secure checksums of all files to validate that best evidence matches original evidence. CIT 380: Securing Computer Systems

22. Evidence Handling Procedures • Record information about original system. • Include photographs of system and media. • Create evidence tag for evidence stored. • Label all media with evidence label. • Case number and evidence tag number. • Timestamp and description of contents. • Store best evidence copy in evidence safe. • Evidence custodian records entry in log. • All examinations performed on forensic copy of best evidence. • Evidence custodian responsible for backups and audits of contents of evidence safe. CIT 380: Securing Computer Systems

23. Evidence Tags • Description of place and/or persons from whom evidence was received. • Description of item and data contained. • Timestamp of when evidence received. • Full name and signature of individual receiving evidence. • Case and tag number related to evidence. • Record of all people who have possessed the evidence, including names, timestamps, and reasons why evidence was transferred. CIT 380: Securing Computer Systems

24. Disk Data Analysis Use Linux analysis system • Support for wide range of filesystems: FAT12, FAT16, FAT32, NTFS, HFS+, FFS, UFS Mount read-only partition image via loopback device: • mount –r –t ntfs –o loop /mnt/evi hda1.img Examine mounted image with standard UNIX tools. CIT 380: Securing Computer Systems

25. Recovering Deleted Files Linux Tools • fatback • FAT/VFAT filesystem undelete by name. • foremost • Recovers files based on header/footer tags. • Sleuthkit TASK • http://www.sleuthkit.org/ • FAT/BSD/Linux/UFS filesystems. • Autopsy GUI forensic browser. CIT 380: Securing Computer Systems

26. Recovering Unused Space Types of Unused Space • Unallocated space • Disk blocks not currently allocated to any files. • Slack space • Portions of disk blocks currently used by file. • Free space • Portion of disk unused by any current partition. CIT 380: Securing Computer Systems

27. File Lists Create list of all files • Full path • All timestamps (atime, ctime, mtime on UNIX) • Logical file size • Cryptographic checksum of file Tool: CATALOG –p /mnt/loopa1 Compare checksums against known good checksums of OS distribution to find altered files. CIT 380: Securing Computer Systems

28. Identify suspicious files New SUID files find /mnt/evi \(–perm –0400 –o – perm –0200 \) –print Files with no owner find /mnt/evi –nouser –o –nogroup Core files may reveal attacker programs find /mnt/evi –name core –print CIT 380: Securing Computer Systems

29. String Searches Preparations • Recover deleted files. • Recursively uncompress/decrypt files as needed. CIT 380: Securing Computer Systems

30. String Searches Using GNU grep grep –a –i -# –f search /dev/hda >results -a: search binary files -i: case insensitive -#: lines of context before/after match -f: search file contains list of regular expressions CIT 380: Securing Computer Systems

31. UNIX Forensics • Review log files • Keyword searches of disk image • Review configuration files • Identify unauthorized users/groups • Identify suspicious files • Identify suspicious processes • Check for backdoors • Analyze trust relationships • Check for kernel rootkits CIT 380: Securing Computer Systems

32. Network Data Collection Goals • Monitor specific host/network. • Monitor specific protocol. • Monitor specific person’s actions. • Check for known attack signatures. Process • Deploy sniffing hardware on appropriate network. • Deploy software to collect packet or session data. • Use data analysis software. CIT 380: Securing Computer Systems

33. Deploying a Sniffer Hub • Hubs flood packets to all interfaces. • Insert a hub between source and destination. • Disadvantages: half-duplex, collisions. SPAN Port • Switched Port ANalyzer, aka mirror port. • Supported by most enterprise class managed switches. • Configure switch to mirror traffic to one port. • Switch may drop SPAN packets when load is heavy. CIT 380: Securing Computer Systems

34. Deploying a Sniffer TAP • Insert between source and destination of traffic. • 4-ports: input, output, outbound mirror, inbound mirror CIT 380: Securing Computer Systems

35. Hardware Issues Fast networks require high resources to monitor. • High quality network card (PCIe card for gigabit) • RAID striped disk for heavily used 100+Mbps network. • Modern dual-core CPU. CIT 380: Securing Computer Systems

36. Hardware Issues Silent Sniffers • Use SPAN port or TAP to avoid sending traffic. • Configure interface without IP address to monitor while not being scannable. • Turn off ARP responses (ifconfig –arp eth0 up) • Unbind NetBIOS and IPX protocols on MSWindows. • Construct a read-only ethernet tap cable by cutting transmit wires on cable for maximum stealth. CIT 380: Securing Computer Systems

37. Wireshark • Based on libpcap like tcpdump. • Convenient graphical interface. • Slows down data collection, may lose packets. • Useful for analysis. • View filters for colorizing packet display. • “Follow TCP Stream” • Select one packet from a TCP session. • Display and/or save single TCP session. • Reconstruct files transferred via TCP file transfer protocols. • Formerly known as Ethereal. CIT 380: Securing Computer Systems

38. Key Points • Don’t trust the system being investigated. • Document all of your actions. • Collect as much data as possible without modifying system state. • Cryptographically sign all digital data so copies can be verified to match originals. • Forensic duplication and restoration process. • Network capture and analysis tools. • Hardware for network captures. • Full content data: tcpdump, ngrep • Session data: argus, tcpflow CIT 380: Securing Computer Systems

39. References • Matt Bishop, Introduction to Computer Security, Addison-Wesley, 2005. • Richard Bejtlich, The Tao of Network Security Monitoring, Addison-Wesley, 2005. • N. Brownlee and E. Guttman, , “RFC 2350 - Expectations for Computer Security Incident Response,” http://www.faqs.org/rfcs/rfc2350.html, 1998. • Mariusz Burdach, “Forensic Analysis of a Live Linux System, Part One,”http://www.securityfocus.com/infocus/1769, March 2004. • Mariusz Burdach, “Forensic Analysis of a Live Linux System, Part Two,”http://www.securityfocus.com/infocus/1773, April 2004. • Brian Carrier, Sleuthkit Informer #11, http://sleuthkit.sourceforge.net/informer/sleuthkit-informer-11.html, December 2003. • CERT, “Computer Security Incident Response Team (CSIRT) FAQ,” http://www.cert.org/csirts/csirt_faq.html • William Cheswick, Steven Bellovin, Steven, and Avriel Rubin, Firewalls and Internet Security, 2nd edition, Addison-Wesley, 2003. • Dan Farmer and Wietse Venema, Forensic Discovery, Addison-Wesley, 2004. • Fraser (ed.), “RFC 2196 - Site Security Handbook,” http://www.faqs.org/rfcs/rfc2196.html, 1997. • Garfinkel, Simson, Spafford, Gene, and Schartz, Alan, Practical UNIX and Internet Security, 3rd edition, O’Reilly & Associates, 2003. • Kevin Mandia, Chris Prosise, and Matt Pepe, Incident Response & Computer Forensics, 2nd edition, McGraw-Hill, 2003. CIT 380: Securing Computer Systems