I'm five chapters through this, so far (out of 21), and am writing this because Amazon prompted me to.The business and organizational portions of this seem strong. The authors warn their readers to consult attorneys in matters of law.They should have followed their own advice. The legal portions are wrong. They conflate criminal and civil law, say that the Federal Sentencing Guidelines are mandatory and set definitions for things in civil law that are governed by the states in finding liability, claim there are three burdens of proof for negligence, and imply that the EU's claims of universal jurisdiction in the GDPR might make it international law. None of that is right. Some of it doesn't even make sense.Criminal and civil law are completely different. The FSG only apply in criminal cases, post-judgment. They have nothing to do with civil liability or with state law. There are four *elements* to negligence, not three "burdens of proof." And it takes way, WAY more to incorporate something into an accepted principle of international law than a collection of legislators declaring the whole universe is subject to their whims.There's more, but I'm not going to go fetch my books to see what I wrote in the margins every time. Just know that the legal portions of this book are, at *best*, wrong. Sometimes, they're "not even wrong" (meaning the premises are SO f'd up they don't even make sense).UPDATE: I'm now >400 pages in and I'm deleting a star. The reason is that the number of definitional and technical mistakes (not just legal) are now accumulating. For instance, mis-using the terms 1st-, 2nd-, and 3rd-party (p. 415), "eavesdropping" (p. 410), and even "screen saver" (p. 410); incorrectly implying that Arduinos are limited to 8-bit operations (p. 387); saying "see the section "Edge and Fog Computing," earlier in this chapter" when the section not only had not yet appeared, it was the *next* section (p. 385); saying that "SCADA is often referred to as a human-machine interface (HMI) since it enables people to better..." which is not correct--an HMI is a point in an ICS system where a person can control the otherwise automated control systems, as per NIST and Idaho National Labs ICS course, whereas SCADA is the entire geographically spread-out system (p. 379); and incorrectly stating that a Faraday cage can be designed to allow longer radio waves but deny shorter ones (p. 368). [Note that all these listed errors are in ONE chapter (Chapter 9).] On p. 254, the authors got mathematical variables confused.Another legal point, because it's really bad. On p. 198, they say that a company can delete evidence after they know an incident has happened, but before a lawsuit is filed. That's almost universally wrong, and doing so can result in (depending on jurisdiction and spoliation rules) criminal sanctions or the "civil death penalty" of automatically losing any resulting lawsuit on the grounds that you destroyed evidence favorable to the other party."The unanimous view of the federal courts is that federal law imposes upon a party a duty to preserve relevant evidence from the time that the party can reasonably anticipate litigation." That is the opening sentence of FEDERAL COMMON LAW AND THE COURTSā REGULATION OF PRE-LITIGATION PRESERVATION, a law article by a judicial clerk named John Koppel.Doing what the authors tell you to do here will screw you and your organization.I'm also irritated by the authors' PC censorship streak, where they rename existing, well-understood technical terms because their pansy sensibilities are offended. This is supposed to be a technical study manual. Keep your propaganda to yourself.Examples? They've decided that the generations-old and universally understood terms "blacklist" and "whitelist" aren't allowed anymore. Likewise with the term Chinese Wall (p. 335). I wonder what kind of fit they throw about the 'Great Firewall of China,' a term used by the same millions of Chinese who are subject to its censorship and social controls, or about master and slave systems, or male and female connectors? Do gender-benders (adapters that reverse connection types from male to female or vice versa) make them faint? Man-in-the-Middle attacks are renamed, because the term is "gendered."On the up side, the cryptography sections seem correct.UPDATE 2: I'm now through chapter 20 of 21. It is obvious this book was the product of multiple authors writing multiple sections separately and then having them shoved together. Portions are uselessly redundant (like the Service-Level Agreements [SLA] section in Chapter 20 and the SLA section in Chapter 16). Some parts disagree with other parts. Some chapters are organized well to apply to the exam callouts they are supposed to cover; others are *not*. On p. 842, a paragraph in one section is obviously supposed to be part of the preceding section; someone screwed up their cut/paste.They routinely f-up the concept of "third party." Guys, you cannot have a "third party" unless you already have a "second party." If I sign a contract with with a company and no one else is involved, they are not a "third party." Seriously, this is not complicated. But it's wrong virtually everywhere throughout this book.There are still serious technical mistakes. On p. 566, they try to sell the idea that digital signals are more reliable than analog signals over long distances but don't know the difference between attenuation and interference, seem to think "direct current voltage" is a thing, imply that direct current signals are immune to attenuation (lol), and don't seem to understand that the '1s and 0s' they always hear about are actually 'voltage highs and voltage lows' and if their digital signal fails to cross the requisite threshold cleanly the signal becomes corrupted.Oh, this one drives me f'ing crazy. One of these authors (see Chapter 11) is absolutely, utterly convinced that TCP/IP is a single protocol; a special 'multi-layer protocol.' No. Just no. TCP is a layer 4 transport protocol, like UDP is. IP is a layer 3 network protocol. 'TCP/IP' was the term the DOD applied to their network model in the 1980s, that is slowly supplanting the OSI model because the OSI one is needlessly complicated. This is so ridiculously stupid I can't believe the three technical editors let it fly. But there're a lot of editing problems in this book, so...On p. 503, there is a sidebar about routing protocols that says "interior routing protocols... make next hop decisions based solely on information related to that next immediate hop." This is wrong. Even RIP (the oldest, most primitive routing protocol in use) makes routing decisions based off the whole topology; that's the entire point, it operates by number of hops between source and destination without regard to things like throughput, reliability, and congestion.One of the practice questions on p. 493 asks "what type of motion detector senses changes in the electrical or magnetic field surrounding a monitored object." Answer: capacitance. Uh, no. Magnetic flux is a function of inductors, not capacitors. Some touch screens are capacitance based, because the physical changes cause capacitive changes. They don't work by waving your hands around. There are a lot of electrical mistakes in this book... see their butchered explanation of noise on p. 467, where they misused the term 'transverse mode' as 'traverse mode,' misused the term power (there's no electrical power without a load, guys), and gave the almost-definition of voltage (the difference in electrical potential between the ground and 'hot' wire) as the definition for noise.They conflate rooting and jailbreaking on p.417, and then try to discuss the legality of it. They fail.Some parts are just dumb, like saying it's "hardly fair" to hold software engineering to the same standards as other engineering disciplines "that are centuries old," like civil engineering (without any mention of nuclear, aerospace, or electrical engineering, which are vastly younger), or addressing the merits of the matter at all. This is just whining that most engineers think 'software engineering' is an appropriation of their discipline name to try to lend a veneer of credibility to something that is manifestly not engineering (think 'custodial engineer' instead of 'janitor' and you have the idea).They like to make reference to government and military practices, but don't know that SCIF is pronounced "skiff," instead of "ess see eye eff," so they write "an SCIF" over and over.They insist that gait analysis is a reliable biological way of identifying people, even though emulating gaits has been used in disguise for centuries and every half-decent actor can pull it off.Crappy legal descriptions continue. They make fun of the idea of getting legal information from television shows, but then do the same thing: on p. 921, "If investigators fail to comply with even the smallest detail of these provisions, they may find their warrant invalidated and the results of the search deemed inadmissible." Uh, no. See Doctrine of Inevitable Discovery. Also, minor errors in warrant executions are routinely held inconsequential in court challenges. They try to describe hearsay rules and blow it. This not surprising; law students screw this up all the time. But the statement that "a witness... cannot testify about what someone else told them outside of court..." is fundamentally wrong. "He said he would kill her" is not hearsay. Saying he killed her because you heard someone else say he would is hearsay.They rename physical evidence as "real evidence," for no reason. They also say there is such a thing as "conclusive evidence... that is incontrovertible" and give DNA as an example... even though it controvertible in the case of multiple birth siblings, flawed evidence collection, planted evidence, and so on. They confuse evidentiary standards and burdens of proof. They try really hard to explain how MOUs and MOAs are different from binding contracts and fail, because they don't actually understand contracts. They do, however, use the term parol evidence rule correctly.On p. 829, they warn that you cannot entrap people with honeypots, because it's illegal. This is completely wrong. Entrapment applies specifically to law enforcement, and prevents them from enticing people to commit crimes they wouldn't have otherwise committed. It has nothing to do with civil behavior in any jurisdiction I've ever heard of.Another element of PC stupidity: Mantraps are now "access control vestibules." Because gendered. FFS.WHY LISTEN TO ME? I'm a lawyer, electrical engineer, and certified network engineer who has about 9 years experience working for a military with meaningful (but not extensive) security training (CEH, Sec+, some other stuff).FINAL JUDGMENT: I can't recommend other specific books because this is the only one I've read for CISSP. But if there is another comprehensive book out there that purports to cover the test, go read it. This one misleads you. It doesn't mislead you on everything (the cryptography, technical security, and certain other sections seem to be correct, and the business/organization sections comport with what I already knew [though I'm not a business guy]), but someone who doesn't know better will 'learn' a lot of stupid BS about the law, electrical devices and behavior, and think that capacitors measure magnetic fields and no internal routing protocols make topology-based routing decisions, and might also think that stupid made-up politically correct horse-crap terminology is, in fact, normal and established.They play loose and easy with law, electromagnetism and other technical details, but are *totally on top of* their post-modern Newspeak. They never missed an opportunity to remind you that "Man-in-the-Middle" is totally uncool, guys. That indicates the priorities of this book.The About the Authors section says they have 'written or contributed' to (collectively) >140 books. They hold all these certifications and have all these awards. I've worked as a legal editor, technical editor, and been published in my own right. They should be embarrassed by this product. I would be.Deleted another star. I can't justify three for an annoying, untrustworthy book I don't recommend.UPDATE 3: Moved onto the practice tests. Other reviewers' comments about bad questions are on target. Not all of them or even most, but some are just... wrong. Example: Chapter 3, #30, the answers don't match the question. Also Chapter 3, # 44, it asks about a topic that is apparently not covered by this edition of the study guide but, according to my investigation, WAS covered in a previous edition, indicating that these questions are (at least partly) a copy-paste job.And be aware that, according to others who have taken the exam after using these products, these 'Practice Tests' are not actually 'Practice Tests.' They are study aids. The questions and explanations (when they're right...) are for studying, not as an honest measurement of your likely performance on the real exam, which is significantly harder.