Malware: Fighting Malicious Code 95
Malware: Fighting Malicious Code | |
author | Ed Skoudis with Lenny Zeltser |
pages | 647 (paperback) |
publisher | Prentice Hall PTR |
rating | 9 |
reviewer | Adam Jenkins |
ISBN | 0131014056 |
summary | very comprehensive guide to malware |
The blurb on the back cover states that the book is "intended for system administrators, network personnel, security personnel, savvy home computer users, and anyone else interested in keeping their systems safe from attackers." It may seem a minor point, but that is a very broad range of people! However, the book is comprehensive enough to merit the claim. For example, the chapter on "malicious mobile code" (or "active content") includes tips on how to configure Internet Explorer's security settings (great for savvy home users), while the information presented on using group policies, Internet Explorer 6 Administration Kit and incorporating changes into Ghost SOE images would be more appropriate for system administrators. One can argue that system/network administrators already know all this, but let's face it; there are many who don't, or who need prompting. The book is particularly strong in explaining theory, like how different types of malware work, and it reminds me of a lot of university text books in layout. Each chapter has a Conclusions section, a summary and a list of references -- great for retention of knowledge, or to help if you are studying for an exam on the chapter. There is a reasonable amount of redundant information in the book; particularly in the "defence" section of each chapter, where file integrity checkers, bootable CDs with static binaries and the like are discussed.
"Malware" is a deliberately broad term, but it suits this book, which covers not just viruses, Trojan horses and worms, but also rootkits and BIOS microcode. The scope extends a bit beyond just fighting malicious code, Skoudis goes so far as analyzing how it works, how it has developed (from other malware) and speculated on the future of malicious code.
Malware is very readable, while still being technically accurate. It does not cover everything, but Skoudis has lots of great analogies, and quotes that range from such diverse sources as Stephen Hawking, Lord of the Rings, The Matrix, Wargames, Milli Vanilli and Styx. The book is written in a conversational and at times humourous style, and I am assuming a lot of the content has been presented in Skoudis's lectures.
Despite the practical approach of the book, the content is not exactly what you might expect. Skoudis's introduction says the book will focus on practicality: "we'll discuss time-tested, real-world actions you can take to secure your systems from attack." Why then in 700 pages is there barely a mention of how to configure a firewall? I think because there are so many applications covered, and because there is so much emphasis on all the fun and cute tools (like the sysinternals ones, and netcat) that some of the less exotic and useful ones suffer in omission.
The Introduction also says the book is operating-system agnostic. Both Windows and Linux are covered, true, but that's not a very broad slice: Solaris, HPUX, BSD, Tru64 and OS X barely get a mention. Even if the book is mostly aimed at home users, there are many using OS X, and in fact many using Mac OS, Windows 98 and even non-Intel platforms.
The illustrations are limited to diagrams, tables and screenshots, and while they are nothing fancy, most are quite clear and helpful.
There is no accompanying CD with the book, but there are so many tools covered in the text, chances are that many of would be quite out-of-date by now anyhow, so you are better off downloading them yourself. Skoudis has a web-site at counterhack.net/, and co-author Lenny Zeltser has one at zeltser.com/. The web sites are not limited to discussing this book, but are more about what Ed and Lenny have written lately, and the "Crack the Hacker Challenges" on Ed's site look fun. There's a list of references at the end of each chapter, and many sources refered to in the text (especially in the last 2 chapters), though I am surprised antivirus company web sites like f-secure, Sophos and CA weren't included; I have found the analyses there at least equal in accuracy and depth to those of McAfee, Trend and Symantec.
As far as bootable CDs for forensics and network security tasks, I'm surprised Trinux and Knoppix STD didn't score a mention, though normal Knoppix and FIRE are mentioned.
The chapter on malicious mobile code covers Java and ActiveX fairly evenly, but I think more emphasis on current threats is the way to go. (Particularly as there is so much FUD surrounding adware and how to remove it.)
One very general flaw with the book is that it tends to focus on the fancier stuff not just in its selection and description of security tooks, but in the actual malware discussed. The information on Code Red II and Bugbear.B is a noticeable exception to this, but many of the other viruses that are discussed -- like Kallisti, Tristate, PHP.Pirus, and Win2k.Stream -- are anything but common.
All that said, I haven't seen any other books that provide such great explanations of rootkits, malicious mobile code or adware, but also hint at things to come like Flash/Warhol worms and microcode malware. This book fills a void in that it covers current malware (with some historical perspective) with enough analogies, scenarios and "detective work" to hold the reader's interest. Hopefully readers will be inspired by the enthusiasm that Skoudis and Zeltser obviously have for fighting malware, and will use this book as a stepping stone to learn more and beat the malware that seems all too prevalent on today's Internet.
You can purchase Malware: Fighting Malicious Code from bn.com. Slashdot welcomes readers' book reviews. To see your own review here, carefully read the book review guidelines, then visit the submission page.
Tru64? (Score:5, Funny)
Re:Tru64? (Score:2)
Re:I've never had IE malware (Score:1)
yeah, that's about the only way to keep IE safe from malware. But hell, just download Kazaa, and make sure you get XXX-Porno.jpg.exe and look at the pretty picture.
Re:I've never had IE malware (Score:2)
Do you mean you never used your computer since Win95? That makes sense then
Because otherwise, considering that 90% of browsers are IE, this would mean 90% of the world CANNOT see most web pages. So 90% of internet users actuall *fake* viewing web pages, order stuff, play games, get worms, etc.
Sounds weird doesn't it?
Re:I've never had IE malware (Score:2)
In case you didn't notice it, my post was a would-be humourous duplication of my parent post [slashdot.org], my point being that using Proxomitron/Privoxy and surfing with IE security set to high prevents many pages from loading properly and is not well-suited for the casual user.
That humourous duplication obviously went belly-up. No offense, I'll try again next year
Re:I've never had IE malware (Score:2)
Re:I've never had IE malware (Score:2, Redundant)
Of course, this negates one obvious threat: the LAN. If a
Re:I've never had IE malware (Score:2, Interesting)
Re:I've never had IE malware (Score:1)
You know...
Scientific Method
Repeatability of results.
Also please include what your internet provider is, and if you have any proxy setting, personal firewalls, home network router....EVERYTHING.
I don't care to repeat the experiment, I am learning Slackware now, but I may find this infor help
Re:I've never had IE malware (Score:1)
Why not just use Firefox????
Is there something I'm missing here?
Re:I've never had IE malware (Score:2)
Re:I've never had IE malware (Score:2)
The girl looks fine in Netscape though.
Re:I've never had IE malware (Score:2)
All you need is common sense. (Score:5, Insightful)
Re:All you need is common sense. (Score:1)
Something which doesnt let things install by themselves, and as Administrator a-la-exploit ( and theres plenty already, and probably more to come, before you "get sp2" fanboys start shouting )
Re:All you need is common sense. (Score:5, Insightful)
So when the computer brings up an IE dialog box that says, "Choose yes to block pop ups", these users say yes.
Should these users know better? I think so. Do they ever learn? I think eventually. In the meanwhile, the IT guy or the local computer shop has to deal with it. It's a sad fact, but spyware is probably the number one money maker for comptuer shops.
Re:All you need is common sense. (Score:2, Interesting)
Re:All you need is common sense. (Score:3, Interesting)
Re:All you need is common sense. (Score:1)
That's like saying "If there were no accidents there'd be no job for the Ambulance driver."
Or the lawyer, chasing close behind it
...and a more intuitive configuration UI (Score:3, Insightful)
Note the word "Internet" rather than "websites." Like I said: lowest common denominator.
Re:All you need is common sense. (Score:2, Interesting)
Re:All you need is common sense. (Score:2, Informative)
Re:All you need is common sense. (Score:2, Interesting)
I can't remember the number of times I've been dragged out to a friends house because their computer has gone pear-shaped due to malware (on windows systems admittedly as the only other OS I know about is Solaris and you don't see many of those on home PCs!).
Then installing Firefox, ZoneAlarm, Ad-Aware, Stinger, an anti-virus and a reg-clean
Re:Malware is a Windows problem (Score:1)
on a good connection, arachne on a 386 is actually not bad
Re:Malware is a Windows problem (Score:1)
Reminds me of a sysadmin at a place where I used to work.
Me: My CD drive is broken.
admin: Why do you need a CD drive?
Me: My space bar doesn't work.
admin: Why do you need a spacebar?
And so on....
Re:Malware is a Windows problem (Score:5, Insightful)
MOD PARENT UP. (Score:1, Insightful)
Re:Malware is a Windows problem (Score:1)
Gentoo isn't exactly easy to get installed the first time.
But it's a damn sight easier than it has any right to be. The instruction guide is exemplary. I wouldn't be pushing a Windows (L)user at Gentoo. Let them play with Mandrake, SUSE or someting similarly automated & quick to install.
Particularly if you've been a Windows user for life, watching pages of compiler messages fly by isn't exactly an inviting experience.
I installed Gentoo
Re:Malware is a Windows problem (Score:2)
Gotta have something to keep it all coming during the holidays, so I figured, why not continue making my life hell? For the next week, I compiled it, having to repeat often, because the power kept going out.
The documentation made it easy though, and after recompiling the kernel a few times, to get my config perfect, I had it running.
But yes, it taught me a huge amount about Linux....6 months
Re:Malware is a Windows problem (Score:2)
Re:Malware is a Windows problem (Score:2)
But it doesn't with spyware on it. They dont care how to remove spyware or how it works, simply that it doesn't work on their system.
GENTOO FOR THEM!
Re:Malware is a Windows problem - Today (Score:2)
Sure, *nix may be a bit more secure by nature, but it wont stop users from hosing up their home directory by clicking 'yes'...
Re:Malware is a Windows problem (Score:2, Insightful)
Re:Malware is a Windows problem (Score:5, Insightful)
"Hmm... I didn't know anything about my magical beige box before, but now with Gentoo I suddenly know exactly what a partition scheme and compiling are, and I haven't even popped the disk into the music slot on my computer yet!"
Being a jerk helps nothing.
Re:Malware is a Windows problem (Score:1)
And you know what? Suprisingly, most people don't want to forced to learn how their computer works. Most people are quite contented to have a magical beige box that periodically brings forth web pages and music.
My Dad couldn't care less that
Re:Malware is a Windows problem (Score:3, Interesting)
I used to use a linux distribution called RedHat Linux, but sadly it is no more. I was going to switch to Suse but it longer is with us either except as an unsupported box of disks.
So far as I can tell, the only supported Linux distributions out there for consumer-level users are Mandrake, the silly Lindows things, and community-supported ones like Gentoo, Debian, and Slack. Fedora and Suse are now cruel jokes so that mega corps (RH and Novell, respecti
mod parent troll (Score:1)
parent is a troll, don't even bother.
Re:Malware is a Windows problem (Score:5, Insightful)
Gentoo? For general, non-geek, Windows users? Maybe something easier, such as Mandrake or Ubuntu, but if they cannot keep malware off their computers, there is probably no way they're able to install Gentoo, let alone any other Linux distribution. Rather, you should give them a suite of the following:
There. That should solve nearly all of their malware problems without having to move to another OS.
*nix may be immune to Windows worms, viruses, and other scum, but it surely isn't immune from clueless lusers. Now, I'm not a MS apologist; I am a FreeBSD user. However, if *nix gets a clueless user base and starts doing stupid things (such as running as root), then all they have to do to get thier computers hozed is for someone to download "Free Britney Spears screensavers for Linux," which turns out to be nothing more than a script that has "rm -r /*" in it. *nix may be more secure than Windows, but it isn't "foolproof," either.
Re:Malware is a Windows problem (Score:1)
Nice Review (Score:5, Interesting)
It's good to see a seemingly well thought out book on the topic of detection and removal of "malware".
The majority of tech calls I get from family and friends involve something malicious or just downright irritating landing on someone's computer (strangely, usually a Win32 box...well, not that strange, considering...), which I end up having to track down and de-couple...which can sometimes be a rather lengthy process, especially where the offending piece has been based on some of the older, smarter virii which spread themselves all over the place just to make sure it takes you a clean floppy or about 4 reboots to remove (re-deleting each re-replaced thing each time). *remember to breath, gazz*
I've longed for a return to the days when I used to only find a blown PSU.....like, 1996....
Good to see chapters on general system "hardening" as well as some more in-depth stuff.
Saying all that, it can be great fun cleaning out a "scr00d" system.
Re:Nice Review (Score:1)
s/(breath)/$1e/;
Re:Nice Review (Score:2)
Re:Nice Review (Score:1)
s/breath/$&e/
?
Re:Nice Review (Score:1)
Re:Nice Review (Score:2)
$ echo breath | sed 's/breath/&e/'
breathe
Re:Nice Review (Score:1)
There's a reason... (Score:3, Funny)
There's no point in wasting time developing worms for Solaris, HPUX, Tru64, etc. The work to reward ratio is too low. Not to say writing a worm, etc. is rewarding, but that's like developing anthrax that only kills people with webbed feet.
Re:There's a reason... (Score:3, Funny)
Fighting Malicious Code? (Score:1)
Re:Fighting Malicious Code? (Score:1)
Re:Fighting Malicious Code? (Score:1)
Re:Fighting Malicious Code? (Score:4, Funny)
Re:Fighting Malicious Code? (Score:1)
I used to tech support (Score:5, Interesting)
The university then started a newsletter that all tech support staff, department heads and administrative staff were supposed to subscribe to. This newsletter would detail technology happenings on campus, planned outages, maintence, a short security blurb, calls open/closed/pending, a blurb about not opening attachments unless you know the source, and much else.
There were always some warnings about attachments and security on the internet.
Several one-shot free classes were set up for all people at the university. Show up, learn about WHY you don't surf porn. Learn why all these things that were "bad" are considered such.
After about 2 years of this the major problems with viruses and infected attachments started noticabling dropping off to the point of very few calls were about a virus type issue..only a few a week instead of a few a day. Then I graduated.
I understand that most tech staff cannot schedule resources like a university can, but having a tech newsletter for an organization is good, as well as having tech instruction to the low level usere who don't see anything other than a magic box of fun!
Having books like this is an obvious good thing, and I may consider going and getting a copy even though I am not doing tech support anymore.
Phil
Most security related books (Score:1)
It's not common finding books that really cover a particular subject in depth.
Worms aren't the half of it.... (Score:3, Interesting)
As everybody else has a clean-out-a-friends-system tale, heres mine:
The aforementioned friend/work colleague asked me to pop round and have a look at his WinXP system. It had been 'running slowly' and he 'couldn't get the internet to work'. Armed with the usual clutch of CD's in case of "bad things"(tm) I took a look. Nothing worked. Control Panel and the Device Manager being the most obivous. I check the services and discover that nearly all of the services had been disabled. After putting things as they should be, I interrogated said friend and found out that he'd followed some instructions from 'another guy' to make his system run quicker.
Sometimes I wonder if you should have a test to operate/own a PC...
Re:Worms aren't the half of it.... (Score:1)
From your description it appears that the test was practical-based and your friend failed. The result being he effectively revoked his own privileges as a user - usable speed, 'net connection etc.
Sounds like the test worked just fine. Would that this self-policing outcome be the default for all ignorant people using computers and the clueless simply disconnect themselves from the Internet.
Re:Worms aren't the half of it.... (Score:1)
I found this book interesting and useful... (Score:3, Informative)
The reviewer mentioned the lack of detailed instructions for firewalling. I don't see that as a drawback at all, there are plenty of books that cover that subject in detail.
The part I liked the most was malware analysis section. If you're the type of home user who wants to know exactly what a spyware app like Gator (or whatever they renamed it) does, this is exactly the info you need.
SANS Track (Score:1)
One thing the review d
Virus Source Code (Score:3, Informative)
why no firewall? that should be obvious. (Score:4, Informative)
Probably because a firewall has fuckall to do with with malware? Malware is an Application layer issue, and while Network/Transport layer security may help mitigate damage, it's not going to keep Clicky McFucktwit from opening GOODTIMES.EXE attached to his e-mail.
Nathan
Re:why no firewall? that should be obvious. (Score:2)
I am amazed that you would choose my family name as some sort of pseudonym for stupidity. I mean, nobody in my family would ever, in their right minds, even use EMAIL let alone click on some file called "GOODTIMES.EXE" We all know that it's "goodtimes.EXE" - next time get the case right, you pompous, self-serv
Malware Prevention Is Simple (Score:3, Insightful)
Stop visiting porn sites
It's true, the majority of people who have malware infected pc's are those who frequent porn sites. Even more malware can be avoided by using common sence and not rushing software installations. Custom installs and skimming the EULA's can spare alot of headaches (and cpu cycles).
I'm not knocking the book. It sounds like a hardcore read for geeks, but Malware wouldn't be such a huge problem today if morality and common sence weren't in such short supply.
Re:Malware Prevention Is Simple (Score:3, Funny)
What would happen to the internet?
Re:Malware Prevention Is Simple (Score:1)
it's not quite so cut an dry. search for ANYTHING of 'questionable' nature (cracks, walkthroughs, mp3s, etc) on the web and you are likely to encounter a site that has a pop up that takes you to a pron site that when you close the window it opens three more; repeat; exponential growth. one of those sites is likely to have malware sneak in while you are busy clicking x's. granted, stop visiting porn sites intentionally would cut a lot out, but avoid porn on the interenet is no easy
How I handled malware in a challenging environment (Score:2, Informative)
Here's what I had set up:
1. Set the machines to power themselves off in the afternoons and on in the morning.
2. Set up a reasonable security policy; enough to prevent the lesser script kiddies from installing anything.
3. Here's the key: Ghost the labs on a regular basis. Since it uses multicast, if you've got a box of floppies and a couple of monkeys to