Books

This book gives you a framework to practice, to troubleshoot, and to walk into the exam room ready for anything. Every topic is designed to simulate what you'll encounter as a pentester in the field. Whether you're going through MCQs, performance scenarios, or flipping through the cheat sheet on the night before the exam, this book helps you build habits, not just answers.

By the time you finish this book, you should be able to make your systems observable across microservices, AI workloads, security monitoring, and hybrid cloud infrastructure. This book will help you learn how to effectively instrument, generate, collect, and export telemetry data (metrics, logs, and traces) to analyze your software’s performance and behavior.

A practical, operator-grade guide to Active Directory credential abuse.Explains how NTLM, Kerberos, and certificate-based attacks form real-world credential pipelines—from capture to use.

The Digital Battlefield Has Changed. Is Your Defense Ready? 🛡️ Manual checks are no longer enough. To secure modern infrastructure, you must move from reactive to proactive. Defensive Cybersecurity with Python is your field manual for building automated, intelligent defenses. From real-time system monitoring to building your own lightweight SIEM, learn to turn Python into your ultimate security weapon. Stop reacting to threats—start automating your defense.

Want to write a technical book? Approach it the same way you build software!

A practical cybersecurity guide for boards and non-technical leaders, written in plain language. Learn how to ask better questions, understand real risk, and support stronger readiness without getting lost in technical detail.

The content has been organised around five operational domains that mirror the SY0-701 objectives and everyday security responsibilities. Each domain contains key references, crosswalks and short scenarios to facilitate rehearsal of connections rather than isolated facts. In order to assist you with finding terms quickly during last-minute revision, To facilitate this process, practice items are designed to pair acronyms with their respective appearances in multiple-choice questions, thereby training recognition in context.

Embedded security is an architecture problem, not a checklist.This book shows how to build a coherent security design for real devices: what embedded cybersecurity means, why it’s different in embedded systems (constraints, lifecycle, physical access, limited patching), and how to turn that into practical design decisions. You’ll learn threat modeling and trust boundaries, then the core mechanisms that must work together: secure boot and root of trust, key management, secure communication, and robust firmware updates. Early access: updated regularly as new chapters and examples are added. Purchasers receive updates.

Nun sind wir beim Kernel angekommen. Nehmen wir an, Sie haben einen Chip, irgendeinen Chip, von den Anbietern, die wir gerade besprochen haben. Sie könnten sich dafür entscheiden, manuell einen Kernel auf diesen Chip zu laden, wobei Sie einen GRand Unified Bootloader (GRUB) verwenden, um den Kernel zu laden (oder zu bootstrappen) und alle Berechtigungen an ihn zu übergeben. Er ist die Seele in der Maschine. Es gibt viele verschiedene Kernel, aber sie teilen eine interessante Eigenschaft in Bezug auf Sicherheit: Sie laufen mit der höchsten Zugriffsebene und vermitteln die Interaktionen zwischen Benutzeranwendungen und den physischen Chips. Ein guter Kernel übernimmt niedrige Aufgaben wie CPU-Scheduling, Speicherverwaltung, Geräteeingabe/-ausgabe und Systemaufrufe. Er ist die Brücke zwischen Software und Hardware: Wenn der Kernel nicht geladen werden kann oder abstürzt, kommt das gesamte System zum Stillstand.

Nu zijn we aangekomen bij de kernel. Laten we aannemen dat je een chip hebt, willekeurig welke chip, van de leveranciers die we net hebben besproken. Je zou ervoor kunnen kiezen om handmatig een kernel op die chip te laden, met behulp van een GRand Unified Bootloader (GRUB) om de kernel te laden (of te bootstrappen), en alle rechten daaraan over te dragen. Het is de animus in de machine. Er zijn veel verschillende kernels, maar ze delen één interessante eigenschap met betrekking tot beveiliging: ze draaien met het hoogste toegangsniveau en bemiddelen in interacties tussen gebruikersapplicaties en de fysieke chips. Een goede kernel behandelt taken op laag niveau zoals CPU-scheduling, geheugentoewijzing, apparaat-in/uitvoer en systeemaanroepen. Het is de brug tussen software en hardware: als de kernel niet laadt of crasht, komt het hele systeem tot stilstand.

Nous voici maintenant arrivés au noyau. Supposons que vous ayez une puce, n'importe laquelle, provenant des fournisseurs dont nous venons de parler. Vous pourriez choisir de charger manuellement un noyau sur cette puce, en utilisant un GRand Unified Bootloader (GRUB) pour charger (ou amorcer) le noyau, et lui transférer toutes les permissions. C'est l'âme dans la machine. Il existe de nombreux noyaux différents, mais ils partagent une caractéristique intéressante en matière de sécurité : ils s'exécutent avec le plus haut niveau d'accès, servant d'intermédiaire entre les applications utilisateur et les puces physiques. Un bon noyau gère les tâches de bas niveau comme l'ordonnancement du CPU, l'allocation de mémoire, les entrées/sorties des périphériques et les appels système. C'est le pont entre le logiciel et le matériel : si le noyau ne se charge pas ou plante, l'ensemble du système s'arrête. Pour rendre ce niveau d'accès un peu plus sûr, le noyau est conçu pour être toujours résident en mémoire et s'exécuter dans un mode protégé qui est isolé des applications. Cela empêche l'endommagement des données système essentielles. Tout accès au matériel doit être...

Cybersecurity Architecture 101 (For Beginners) is a practical, beginner friendly guide to how modern security is actually designed. Starting from CIA, risk, and threat modeling, it walks you through identity, networks, endpoints, cloud, applications, data, Zero Trust, DevSecOps, governance, and real world roadmaps you can apply in your own environment.

This reference volume consists of revised, edited, cross-referenced, and thematically organized articles from the Software Diagnostics and Observability Institute and the Software Diagnostics Library (former Crash Dump Analysis blog) about software diagnostics, root cause analysis, debugging, crash and hang dump analysis, and software trace and log analysis written from 15 April 2024 to 14 November 2025.

This isn't a book to put on a shelf. It's meant to be used, tested, and adapted as you build your networking skills. In this new edition, I've been working on making the teaching flow better and making technical stuff clearer without overwhelming you. You'll get the basics down, like how C++ works well with TCP/IP and how sockets are the foundation for communication. Then, I'll show you how to build real client-server apps, set up IP addressing, and use protocols like HTTP, FTP, SMTP, IMAP, and DNS directly through C++ code. Each example is practical and you can actually implement it. It shows you not just how something works, but why it matters in real networking scenarios.

This second edition is for Python programmers who want to get into networking but don't want to feel overwhelmed. My goal is to make you comfortable with reading code and using it to solve real-world networking problems. A lot of people wrote to me saying that it helped them automate tasks that they had been doing manually for years, while others shared how it gave them the confidence to switch careers or take on more advanced responsibilities in their roles.