The Network Security Test Lab: A Step-by-Step Guide 1st Edition

Good book and very interesting. Should be able to set up lab by following book, but software could be expensive. Some "free" stuff is no longer free.

Very informative about how to get a test lab up and running.

The Network Security Test Lab by Michael Gregg was a pretty good read. I found the writer’s style to be very easy to follow and he explained things in a way that was reasonable to understand for a non-expert. When I read the first 2 chapters, I was really anticipating the rest of the book being more about the minutiae of an actual “test lab” and the nuances of trying to maintain one. That was not the actual aim of the book, which was more of a general overview of cybersecurity, with some discussion of setting up a lab. I have read the other material of malware, IDS and IPS, and pen tools in other textbooks, and am not complaining of Mr. Gregg’s writing. It was done well. It is only that I was hoping for more of a hard-core physical lab detail and problems/solutions inherent. I will say that there were some typos/errors found in some of the problems and exercises that could have been corrected via editing. That was a disappointment. And, some of the links were not up to date. (That may not be anyone’s fault necessarily, but tough to have happen when using for a class.) I would like the author to have a webpage with up to date links!

As a student in an ethical hacking class, I found this book a great asset as a supplement to the hands-on labs. It's clear, concise, and easy to understand how to setup, and use a test lab.

In the introduction on page xxiv, the author states " . . . please let me know how it helps you advance in the field of cyber security". On page 40, he gives information regarding his company. Went to their website several days ago, they had a contact page, so I sent them information regarding technical errors or typos and asked a couple of questions. So far, not a reply - not that I really expected THE author to see my input. Still, he should not have made that statement. I have other books and when I contacted the authors or their companies, I received personal replies.Now about the technical errors . . . and so far I am only up to chapter 4 . . .On page 111, he states that the TTL for a Linux is 64. On page 130, he says it is 65. Probably a typo . . .The other error I found appears to be MY mistake. He references Figure 3-26 on page 110. I could not find that figure but when writing this review, I did find it - just that the "Figure 3-26" is inside the figure instead of below it, no big deal.Anyhow, my disappointment so far is no real way to get assistance with the material presented. On page 67, he suggests using a Perl script. Well, that is fine if you know how to use a Perl script . . . . which I have no idea . . .I will keep reading the book and maybe his company will take the time to answer my questions. Like is nslookup considered "scanning" and can it cause me 'problems' if I use it to scan networks.DavidMobile, AL

This book is a great resource for better understanding the technical details of network security. The labs at the end of each chapter separate this book from many others that just present the concepts. I just passed the Security+ exam and this has been a great next step.

In general, I like this book. We use it for a class that I teach. From an organization and content standpoint, the material is fine. The examples, unfortunately, are very out of date. They reference websites that don't exist, FTP servers that are long gone, and software that has had no maintainer for years. I pretty much have to write an addendum for most of the exercises so the students can find what they're looking for, or use new commands and features not shown in the book.It's not really the author's fault - things in this business move at a rapid pace. A second edition with updates would be greatly appreciated!

Lots of great scenarios. Weighs a ton.