Torrent details for "Bonifield J. Data Engineering for Cybersecurity.Build Secure Dat…" Log in to bookmark
Controls:
×
Report Torrent
Please select a reason for reporting this torrent:
Your report will be reviewed by our moderation team.
×
Report Information
Loading report information...
This torrent has been reported 0 times.
Report Summary:
| User | Reason | Date |
|---|
Failed to load report information.
×
Success
Your report has been submitted successfully.
Checked by:
Category:
Language:
None
Total Size:
55.9 MB
Info Hash:
6291674DDAA36A3C4961AB143D7837F85A49F698
Added By:
Added:
Aug. 23, 2025, 9:57 a.m.
Stats:
|
(Last updated: Aug. 23, 2025, 10:03 a.m.)
| File | Size |
|---|---|
| Code.zip | 161.9 KB |
| Bonifield J. Data Engineering for Cybersecurity.Build Secure Data Pipelines 2025.pdf | 55.8 MB |
NOTE
SOURCE: Bonifield J. Data Engineering for Cybersecurity.Build Secure Data Pipelines 2025
-----------------------------------------------------------------------------------
COVER
-----------------------------------------------------------------------------------
MEDIAINFO
Textbook in PDF format Turn raw logs into real intelligence. Security teams rely on telemetry—the continuous stream of logs, events, metrics, and signals that reveal what’s happening across systems, endpoints, and cloud services. But that data doesn’t organize itself. It has to be collected, normalized, enriched, and secured before it becomes useful. That’s where data engineering comes in. In this hands-on guide, cybersecurity engineer James Bonifield teaches you how to design and build scalable, secure data pipelines using free, open source tools such as Filebeat, Logstash, Redis, Kafka, and Elasticsearch and more. You’ll learn how to collect telemetry from Windows including Sysmon and PowerShell events, Linux files and syslog, and streaming data from network and security appliances. You’ll then transform it into structured formats, secure it in transit, and automate your deployments using Ansible. You’ll also learn how to: Encrypt and secure data in transit using TLS and SSH Centrally manage code and configuration files using Git Transform messy logs into structured events Enrich data with threat intelligence using Redis and Memcached Stream and centralize data at scale with Kafka Automate with Ansible for repeatable deployments Whether you’re building a pipeline on a tight budget or deploying an enterprise-scale system, this book shows you how to centralize your security data, support real-time detection, and lay the groundwork for incident response and long-term forensics. Prerequisites: This book assumes a basic familiarity with the Linux operating system and its command line. We’ll walk through all configuration steps and commands to run, but you’ll find it easiest to follow along if you’re used to working in the terminal. Here are some other topics you might want to familiarize yourself with before moving on: - Virtual machines Virtual machines are virtualized computers running inside of other computers. For example, you might run a Linux virtual machine on your Windows desktop or laptop. The computer that hosts the virtual machine is called a hypervisor. Virtual machines are helpful for practicing new tools and concepts, as you can take a snapshot of their current state and then return the machine to that state if anything goes wrong. - TCP and UDP The tools covered throughout this book make network connections using the Transmission Control Protocol (TCP) and User Datagram Protocol (UDP). TCP is a protocol that requires systems to acknowledge receipt of the data they exchange, making it resilient to connectivity issues. TCP is useful for tasks like file transfers and email delivery, where it’s important not to lose any data. UDP doesn’t require an acknowledgment from a recipient, and it’s useful for tasks like watching videos or listening to audio without constantly being interrupted. If some of the bytes drop while traveling from the server to your screen, the show goes on without a hiccup. - HTTP and TLS You’ll use the Hypertext Transfer Protocol (HTTP) to request and receive data from the web. HTTP is an unencrypted protocol, meaning an overly curious or malicious actor on the same network could position themselves to inspect the content of your communications with a web server. Today, most websites use HTTPS, which encrypts traffic with Transport Layer Security (TLS), the “S” in “HTTPS.” We’ll cover TLS further in Chapter 2 and use it to encrypt all network traffic when able, including for data fetched from the web and communications between tools. - SSH Secure Shell (SSH) is a technology that creates an encrypted tunnel, or network connection, from one computer to another. It’s often used to remotely control a computer as if you’re using its local keyboard. You’ll configure several virtual machines in this book and then make extensive use of SSH to interact with them. You’ll also explore an automation tool, Ansible, that uses SSH to orchestrate actions on many hosts at once. Chapter 2 discusses SSH in more detail. - Scripting languages In this book, you’ll write a few scripts using the Python programming language and use the Ruby programming language to transform data. We’ll walk through these scripts’ contents in detail. That said, you could also automate many of the commands we’ll cover using shell scripts that execute Linux commands. Some experience creating shell, Python, or Ruby scripts is recommended, but not necessary, to follow along. Who This Book Is For: This book is for anyone tasked with creating a cybersecurity monitoring system or centralizing a business’s logs. It may be particularly useful for those operating with constrained budgets, but it is relevant to those operating with enterprise-level funding as well. Network defenders can use this book to transform events taken from a multitude of systems and tools into a standard format before storing them. Administrators and engineers can also use this book to manage the many device health logs flowing through the network. Offensive testers can also use it to read and transform the variety of outputs from hacking tools to store them for client reports, automate the comparison of results, and dispatch additional tool actions. Those seeking to automate defensive or offensive actions may find centralizing and standardizing logs useful as well
×