Hacker's Challenge 3: 20 Brand New Forensic Scenarios &amp; Solutions (v. 3)
The stories about phishing attacks against banks are so true-to-life, it&#8217;s chilling.&#8221; --Joel Dubin, CISSP, Microsoft MVP in SecurityEvery day, hackers are devising new ways to break into your network. Do you have what it takes to stop them? Find out inHacker&#8217;s Challenge 3. Inside, top-tier security experts offer 20 brand-new, real-world network security incidents to test your computer forensics and response skills. All the latest hot-button topics are covered, including phishing and pharming scams, internal corporate hacking, Cisco IOS, wireless, iSCSI storage, VoIP, Windows, Mac OS X, and UNIX/Linux hacks, and much more. Each challenge includes a detailed explanation of the incident--how the break-in was detected, evidence and clues, technical background such as log files and network maps, and a series of questions for you to solve. In Part II, you&#8217;ll get a detailed analysis of how the experts solved each incident.Exerpt from &#8220;Big Bait, Big Phish&#8221;:The Challenge:&#8220;Could you find out what&#8217;s going on with the gobi web server? Customer order e-mails aren&#8217;t being sent out, and the thing&#8217;s chugging under a big load&#8230;&#8221; Rob e-mailed the development team reminding them not to send marketing e-mails from the gobi web server&#8230;. &#8220;Customer service is worried about some issue with tons of disputed false orders&#8230;.&#8221; Rob noticed a suspicious pattern with the &#8220;false&#8221; orders: they were all being delivered to the same P.O. box&#8230;He decided to investigate the access logs. An external JavaScript file being referenced seemed especially strange, so he tested to see if he could access it himself&#8230;. The attacker was manipulating the link parameter of the login.pl application. Rob needed to see the server side script that generated the login.pl page to determine the purpose&#8230;.The Solution:After reviewing the log files included in the challenge, propose your assessment: What is the significance of the attacker&#8217;s JavaScript file? What was an early clue that Rob missed that might have alerted him to something being amiss? What are some different ways the attacker could have delivered the payload? Who is this attack ultimately targeted against? Then, turn to the experts' answers to find out what really happened.