Rather than just commenting out of the blue, I just picked up my copy and skimmed back through it and I have to say most of the information is still relevant (I can't say all of it as certain architectural changes have been made). I would be surprised if a DBA couldn't put the book to good use as-is, and would question one who couldn't anyway.
I have to ask what you find odd about the book? Doing so might give a better insight.
But to stay on topic, the best documents to read are the best practice documents for your respective vendor. Even SQL Sewer can be locked down fairly tightly just by following these practices without (bonus of bonuses) having to change much code on the front end (disable exec..xp_ and so on).
A theory I'm pretty sure I've broached here before: There is no such thing as bad information - I've pointed kids at Meinel's work before despite her being a complete moron (in my views). There is truth in the data, so you sift it all, even the crap stuff.