Slashdot Mirror
Special Ops
In order to get the most out of Special Ops, I suggest that you brush up on your system administration skills, particularly Microsoft technologies. The book is aimed primarily at security and systems administrators, but several of the chapters are either aimed specifically at management (Chaps 17 & 18), or could easily be understood by them (chaps 1-3).
The authors write in a conversational, matter-of-fact style, including personal anecdotes and experiences where appropriate. The editors did a great job of "smoothing out" the styles of the different authors to give Special Ops a consistent feel.
One of the best features of Special Ops is the end-of-chapter content. These summaries include a "Security Checklist" which creates a nice list for admins to take into the field, a one-page summary of the chapter, links to relevant web pages, relevant mailing lists, other books to read for more in-depth information, a "Solutions Fast Track," and a FAQ. Some chapters list all of the freeware and commercial tools used/mentioned in that chapter. The Solutions Fast Track is a great section to hand to your slightly more technical manager explaining why you should secure a specific service. These chapter extras make Special Ops a great reference book, even if you never bother to read the rest of it.
Another great feature is the "Notes from the Underground ..." sections scattered throughout the book. All of the authors have worked in security for several years, and they share specific examples of attacks or other interesting tidbits they've seen over the years.
I had trouble giving Special Ops a rating of 9 or 10 for a few reasons. Even though the book is an easy read, it's a lot of information to digest. The subtitle makes it sound as if Microsoft, UNIX, and Oracle would receive equal treatment: not so. While there are 7 chapters on Microsoft specific technologies, UNIX and Oracle rate one chapter each. I would have preferred to see Special Ops split into 2 or 3 books, giving equal attention to all of the technologies.
The authors' bias towards certain commercial tools shows through as well. Granted, the majority of the authors are also Foundstone employees, but they should have given equal treatment to all tools. Explain the strengths and weaknesses of each tool and allow the reader to decide on the "best" tool.
All in all, Special Ops is a great book. It will definitely reside on my reference shelf for years to come.
Table of Contents- Assessing Internal Network Security
- Inventory and Exposure of Corporate Assets
- Hunting for High Severity Vulnerabilities (HSV)
- Attacking and Defending Windows XP Professional
- Attacking and Defending Windows 2000
- Securing Active Directory
- Securing Exchange and Outlook Web Access
- Attacking and Defending DNS
- Attacking and Defending Microsoft Terminal Services
- Securing IIS
- Hacking Custom Web Applications
- Attacking and Defending Microsoft SQL Server
- Attacking and Defending Oracle
- Attacking and Defending Unix
- Wireless LANs: Discovery and Defense
- Network Architecture
- Architecting the Human Factor
- Creating Effective Corporate Security Policies
You can purchase the Special Ops from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
He means, Uninstalling Windows 2000, doesn't he?
Is this truly the only Earth I can live on?
I f I can get my emplotyer to buy this for me?
It is certainly the kind of problem I often end up facing at work, far too many people know just enough to majorly fuck things up nowadays.
Personally, I would prefer not to have to use M$ware at all, but all too often legacy systems in the workplace are a lock in, so I expect to see things like this continue to be published and be popular for a good while.
An infinite number of monkeys will eventually come up with the complete works of
While there are 7 chapters on Microsoft specific technologies, UNIX and Oracle rate one chapter each.
:)
Well, this is a security guide, isn't it?
The coolest voice ever.
I'd rate it somewhere around 6 or 7 out of 10, certainly no where near 9. My major complaints are similar to those of the author of the article:
- Gives no mention of its focus on Microsoft OS's, but it concentrates on them nearly entirely.
- Simple, simple, simple. If you know your basics, most of this book is redundant and a review. There's a lengthy discussion on how a traceroute works. That's a little too simple for my tastes.
- Though not required, the author seems excessively biased towards Microsoft OS's. He even goes so far to suggest (in mild language) that it's easier to track invaders using Microsoft products than using freely available tools. C'mon, I think we all know the pile of open source tools available for these applications outnumber and outwork anything out of Redmond.
It's something I think newbie MS admins should read, but it doesn't hold much new content for anyone who's been admining for a year+.
+ Donald Gunth
+ Email: dgunth@quicktek.net
"Caffeine is the greatest lubricant ever created." -ESR
Compentant admins have systems that are harder to hack - a distinction that is important to make.
That is all.
Your major complaints about this book is true, yet, one point, however, is quite arguable to me, that is the microsoft point.
Microsoft products (i.e. windows 95/98/NT/2k/2k3) does have its place (and a large market share...) on corporate markets (on clients), therefore it should be considered as a large portion of corporate administration. I spend most of my time administrating windows even though i'm a linux admin. (Well, the good debian box does not require much administration, honestly.)
As soon as I read that there are 7 chapters on M$, I knew the M$ flames would be abundant in this thread of comments. I'd like to take a different approach to this; rather than adamently bash microsoft, I'll be more subtle about it. I see securing MS products as a challenge. Yes, they're buggy (release early / often,) and I love my Unixees more, but this could be a fun game. Anyone can RTFM and secure *nix boxen, but someone who can make a windows box truely secure... now they've done something!!
"The best laid plans of mice and men gang oft agley..." - ROBERT BURNS
Competant admins simply do not get hacked.
This is a ridiculous statement to say the least, and an obvious sign of ignorance. If all you're doing is patching servers and paying attention to vulnerability reports, then you wouldn't even know if you DID get hacked. Real security requires a layered approach, one of those layers being intrusion detection. This alone can be a full-time job. It is this simplistic-style thinking that continues to make the Internet such a dangerous place, and contributes to my inability to get any significant amount of funding for security-related projects. If all I have to do is patch servers and watch vuln reports, then why should I spend money on a firewall, IDS, training, a security policy, etc, etc, etc. I could write an entire book just on why that statement was dumb...but this post will have to suffice.
Social Engineering Expert: Because there is no patch for stupidity.
3) Put bricks around cinderblocks
Congratulations. Your Windows installation is now secure.
I strongly disagree with this sentiment. Some of the most knowledgable security gurus I know are "hackers" who started by administering systems. And many administrators I know can apply patches with the best of 'em, but are unable to recognize potential attack signatures in their logs. Simply knowing how to apply a patch does not give one the insight required to recognize attacks that aren't widely publicized. Do you want an admin who only knows he/she is being attacked because Microsoft says so? Or would you rather have one who knows what to look for because he/she has studied hacking techniques and has ethically hacked, and therefore can cut off suspicious behavior before a patch is even issued? I know which one I'd pick.
http://www.cgisecurity.com/lib/
...If maintaining the security of networked machines running Microsoft Windows is part of your job...
I had a nightmare about that last week. wierd.
In response to the large numbers of complaints that the book focuses too narrowly on Micro$oft Products, I propose the following changes to make it more universal.
Please remove pages 1 - 1040 and replace with the following sheet of paper:
- - - - - - - -
1.) Educate your users.
Failing that:
2.) Execute your users.
I assert that my comment is only my opinion, not that of any employer, past, present or future.
That's not always true. Sometimes patches are the problem.
Almost without fail, hacking incidents at major companies are found to be due to security holes that have been known about and fixed for months, if not years.
Tell that to the victims of the latest BugBear worm. Admins who patched for the first worm were not protected against the latest variant.
Well, there's spam egg sausage and spam, that's not got much spam in it.
I urge your to read the hole thing, one verse pr. line.
There's a hole in the bucket, dear Liza, dear Liza, There's a hole in the bucket, dear Liza, a hole.
So fix it dear Henry, dear Henry, dear Henry, So fix it dear Henry, dear Henry, fix it.
With what should I fix it, dear Liza, dear Liza, With what should I fix it, dear Liza, with what?
With straw, dear Henry, dear Henry, dear Henry, With straw, dear Henry, dear Henry, with straw.
But the straw is too long, dear Liza, dear Liza, The straw is too long, dear Liza, too long.
So cut it dear Henry, dear Henry, dear Henry, So cut it dear Henry, dear Henry, cut it!
With what should I cut it, dear Liza, dear Liza, With what should I cut it, dear Liza, with what?
Use the hatchet, dear Henry, dear Henry, dear Henry, Use the hatchet, dear Henry, the hatchet.
But the hatchet's too dull, dear Liza, dear Liza, The hatchet's too dull, dear Liza, too dull.
So, sharpen it, dear Henry, dear Henry, dear Henry, So sharpen it dear Henry, dear Henry, sharpen it!
With what should I sharpen it, dear Liza, dear Liza, With what should I sharpen, dear Liza, with what?
Use the stone, dear Henry, dear Henry, dear Henry, Use the stone, dear Henry, dear Henry, the stone.
But the stone is too dry, dear Liza, dear Liza, The stone is too dry, dear Liza, too dry.
So wet it, dear Henry, dear Henry, dear Henry, So wet it dear Henry, dear Henry, wet it.
With what should I wet it, dear Liza, dear Liza, With what should I wet it, dear Liza, with what?
With water, dear Henry, dear Henry, dear Henry, With water, dear Henry, dear Henry, water.
With what should I carry it, dear Liza, dear Liza, With what should I carry it dear Liza, with what?
Use the bucket dear Henry, dear Henry, dear Henry, Use the bucket, dear Henry, dear Henry, the bucket!
There's a hole in the bucket, dear Liza, dear Liza, There's a hole in the bucket, dear Liza, a hole.
Step 1: Place Windows system in a lead safe
Step 2: Take wire cutters and cut ethernet cable to said computer
Step 3: Close door
Step 4: Dump the safe into closest body of water
Now you have a windows system no one can touch.
Slashdot.. Land of nerds, trolls, and FlameBait..
I believe that
A truly secure system must be able to withstand open review at all levels (e.g. protocol, source code, etc).
The details of security vulnerabilities should be available to everyone. (source: Bugtraq)
It won't get a chance to turn me away. One glance at the website, and I was hammering the Back button.
--
"Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
That's very impressive. Most *nix books address the topic as if DNS == BIND. Personally, I prefer DJBDNS not only because it's more secure, but also because of the way it is configured (small, modular, partitioned) and, er, the way it is configured (configuration files). I also use daemontools to run liveice (when the program first came out, it refused to go into the background and would not stay up for more than several hours at a time).
WMBC freeform/independent online radio.