Exclusive Interview from our Author Kaustubh Dhondge

In this interview, we talk to Kaustubh Dhondge, author of the book Lifecycle IoT Security for Engineers. We discuss the motivation behind writing the book, the target audience, the most useful aspects of the book, the challenges of writing the book, and advice for other engineers who are considering writing a book. 

Dr. Kaustubh Dhondge is the Founder of Glaukes Labs – a technology company focusing on crafting extraordinary digital experiences. Glaukes Labs designs, develops, and publishes mobile apps, games, and online services.

His research interests, publications, and patents lie in the areas of mobile systems and applications which involve the Internet of Things (IoT), Smart Wearable Systems, Visible Light Communication, Authentication & Security for Smart Devices, Vehicular Communication with Smart Devices, and Positioning & Localization for Smart Devices. He’s the author of the book titled “Lifecycle IoT Security for Engineers”.

He has served as a Researcher and Research & Development Intern at TCS Innovation Labs – Cincinnati under the guidance of Dr. Rajeev Shorey. Their research focused on improving the energy-efficiency of the Industrial Internet of Things (IoT). He received his Ph.D. in Telecommunications and Computer Networking, and Computer Science from the University of Missouri – Kansas City, under the guidance of Dr. Baek-Young Choi. His doctoral dissertation proposed and developed diverse direct communication techniques for IoT applications.”

  1. What was your main motivation behind writing your book?  

In my professional career, I have worked on IoT and its related technologies in various capacities – as a Ph.D. Student, Researcher, and Business Owner. During this course, I identified a gap in the existing literature. While there were some good books on IoT security, none offered a global view of the security concerns and solutions as an IoT product traversed through various stages of its lifecycle.  

My main motivation behind writing this book was to offer the readers a holistic view of the security considerations for an IoT product/service throughout its lifecycle. Additionally, the book also has an emphasis on the following topics: 

Regulatory guidance for the IoT industry – which is important to tackle from a business perspective. 

Social impacts of IoT security failures – it is important to appreciate how security failures can harm the humans using these technologies.      

As underscored in the Foreword of my book, these topics had yet to receive the attention they deserve in recent years. 

  1. Who is the main target audience for your book and what will they appreciate the most about the book? 

I have written this book intending to target diverse audiences in industry and academia. That includes researchers, engineers, architects, managers, members of the C-suite, students, professors, and even artists building innovative IoT products. IoT is an interdisciplinary field, and securing it is our collective responsibility – and yes, that includes the end users!  

The readers will appreciate that the book is easy to read but offers a comprehensive coverage of the unique factors in IoT security. Also, I have tried my best to make this book engaging for everyone interested in keeping IoT secure, irrespective of their technical backgrounds, with appropriate technical depth and coverage for advanced and novice readers. 

  1. What do you see your book being most useful for? 

The comprehensive nature of my book makes it a one-stop for readers attempting to advance their knowledge in IoT security. It is most useful for readers to gain a fundamental understanding of security vulnerabilities, attack vectors, pre-emptive measures, and recovery mechanisms in a fast and ever-evolving field.       

  1. How did you find the writing of the book? Do you have a specific process or are you quite methodical in your writing approach? 

Writing the book was difficult! Even for those of us with extensive experience in technical writing in the form of research papers, technical reports, white papers, or patents – writing a book can quickly get overwhelming due to its sheer size. Additionally, writing the book as a solo author or with co-authors can present unique challenges in managing such a vast project. 

For me, the best way to approach writing was to start with a thorough Table of Contents based on the gaps I noticed in existing literature and topics I wanted to cover. From there, I treated each of the chapters as an individual and self-contained project while keeping an eye on the big picture to keep the narrative of the book cohesive. I also feel that to write a book, one must read a lot of books. Technical writing, and book writing in particular, is a lifelong work in progress. Reading good literature can improve it in the long run.      

  1. What challenges did you face when writing the book and how did you overcome them? 

I had a fair share of challenges while writing this book. Primarily, it was hard to stay on track to finish each of the chapters on time. For most of us, writing a book is in conjunction with our primary job role(s), and other professional and/or personal responsibilities. In my case, I was also writing this book at the peak of the COVID-19 pandemic, which had caused severe disruptions to regular business. 

Surrounding yourself with those who can act as a coach can go a long way in keeping you on track. The team at Artech is exceptionally good at this! In my case, it was Natalie McGregor and Dr. David Michelson. They were instrumental in keeping me motivated with their encouragement and the right amount of push to finish this project. 

Ultimately, it is our responsibility as the author to get down and write. I found that daily, incremental progress in writing, however small, is critical to finishing the book on time.    

  1. What advice would you give to other engineers who are considering writing a book? 

Go for it!  

Having a thorough understanding and knowledge of your chosen book topic is a must, and given. Spend quality time on background research, and understanding recent advancements in the field. From there, identify the shortcomings that your book can bridge in current literature. Once you draw up a solid Table of Contents based on this information, you will have a strong backbone for your book to work with. The acquisitions process at Artech is quite adept in gleaning this information from you. Be open to critical feedback from the reviewer(s). Incorporating the changes/inputs from the reviewer(s) will improve the quality of the book. The same goes for copy editing as well to keep a consistent tone, and correctness throughout the manuscript. 

Also, be mindful that writing a book is a huge endeavor. It can put immense stress on not only you but also your family if you do not factor in other time commitments correctly. If possible, get inputs from your mentors who have previously written a book. In particular ask them about their motivations, challenges, and outcomes of writing a book. You can benefit from their experience, and avoid the mistakes they might have made early on. 

  1. What are you working on next? 

On the business front, my company Glaukes Labs continues to craft exceptional digital experiences for our users in the form of mobile apps, games, and software services.  

On the writing front, I am working on finishing up my manuscript for a book on the fundamentals of passwordless authentication for Artech House. 

Learn more about the book on our websites

ARTECH HOUSE USA : Lifecycle IoT Security for Engineers

ARTECH HOUSE U.K.: Lifecycle IoT Security for Engineers

More Mobile Security content here Security and Privacy – Artech House Insider