Incident Response -- Investigating Computer Crime

    Date26 Jul 2001
    3471
    Posted ByAnthony Pell
    "I particularly recommend the book for less advanced admins and those who don't have a lot of hands-on experience. If you've never been through an "incident," this is a very good book to have. If you've been through one or two, . . . "I particularly recommend the book for less advanced admins and those who don't have a lot of hands-on experience. If you've never been through an "incident," this is a very good book to have. If you've been through one or two, you might find a few things you've done wrong (or right) and some extra ways to prepare for the next time."

    "The book covers a wide range of topics. The first part of the book introduces the reader to incident response. Chapter 1 walks through an incident response case study. The authors provide a step-by-step account of tracking down a cracker who broke into a server and deleted a database. The case study includes information on tracking down the cracker in question and gathering evidence to have him prosecuted (at the time of the book's printing, the cracker had been prosecuted successfully and was awaiting sentencing). If only 5% of the people who buy this book manage to prosecute a cracker who has tampered with other people's systems, the world will be a better place. "

    You are not authorised to post comments.

    LinuxSecurity Poll

    Which Linux distribution(s) do you use?

    Message!

    Poll results are hidden from public viewing.

    You are not authorized to vote on this poll.

    No answer selected. Please try again.
    Please select either existing option or enter your own, however not both.
    Please select minimum 0 answer(s) and maximum 5 answer(s).
    /component/communitypolls/?task=poll.vote
    7
    radio
    bottom200

    We use cookies to provide and improve our services. By using our site, you consent to our Cookie Policy.