Focus on IAM (Identity and Access Management): CSFs, metrics, checklists, best practices, and guidelines for defining IAM processes and implementing IAM solutions

This book is very poor. It's more of a dictionary of terms if anything.

Not a serious technical text. Poorly edited, loosely organized, not for the serious student of IAM. Evidently self-published, lacking even an ISBN or Library of Congress catalog number.

Not well written, not as much information or technical processes included. Seems very simple

Formatting is dreadfully sloppy. So poor that it's almost indistinguishable from most of the self-published ebooks that have been flooding the market over the last year or so.I hate to say it, but I'm learning to avoid the self-published stuff, unless the circumstances are truly unusual. Most of it is complete trash. Books that purport to offer you a grasp of a fairly technical area, where detail really matters, inside of a few dozen pages. Books that are so poorly formatted that the body text is a trackless wasteland. That sort of thing.The only exceptions to this trend I can recall offhand are Michael Lucas, Ivan Ristić, and Daniel Dieterle. Michael Lucas is no stranger to publishing: he already had more than a decade's worth of experience before he started self-publishing, and a history of really first-rate work. The first edition of his book about OpenBSD is *still* useful, even after the second edition was released. Ivan Ristić is less generally well known, but the quality of his book on SSL/TLS is simply stunning: it's the best reference that I know of on that subject, period. And Dieterle's books on Kali Linux are well worth reading.Kiran Pabbathi, OTOH, has some learning still to do. That's really too bad, because there isn't much published on access management beyond certification prep books. It's a curst hard area of information security, which could use more good roadmaps than it's got right now.

I suggest for the author to go back and work in IT for at least 19 more years. book reflects lack of depth understanding. not sure how can someone starts writing with only 11 years of IT experience.