// Comparison
Data Engineering for Cybersecurity vs Evading EDR: Which Should You Read?
Two cybersecurity books on Detection, compared honestly: who each is for, what each does best, and which to read first.
Build Secure Data Pipelines with Free and Open-Source Tools
James Bonifield
A decade-plus threat analyst teaches how to collect, normalize, enrich, and secure the telemetry (logs, events, metrics) that security teams depend on, using open-source tools like Filebeat, Logstash, Redis, Kafka, and Elasticsearch.
A component-by-component teardown of how modern EDR sensors actually collect telemetry, and where each data source can be starved, blinded, or bypassed.
Read this if
Skip this if
Key takeaways
- Treats telemetry as an engineering problem with its own lifecycle (collect, normalize, enrich, secure) rather than something a SIEM magically handles.
- Built entirely on free, open-source tooling (Filebeat, Logstash, Redis, Kafka, Elasticsearch), so the pipeline design is reproducible without a vendor contract.
- Automating deployment with Ansible is treated as part of the job, not an afterthought — the pipeline has to be maintainable, not just functional once.
- EDR is a collection of telemetry sources, not a monolith; evasion means knowing which source sees what.
- Most durable bypasses attack the sensor's data collection, not its detection logic.
- Vendor-agnostic understanding outlives any specific bypass, which vendors patch fast.
How they compare
Data Engineering for Cybersecurity and Evading EDR are both rated 4/5 in our catalog. Pick by topic preference and reading style rather than by rating.
Both books target advanced-level readers, so the choice is about topic, not difficulty.
Data Engineering for Cybersecurity and Evading EDR both cover Detection, so reading them in sequence reinforces the same material from different angles.
Keep reading
Data Engineering for Cybersecurity
→ Alternatives to Data Engineering for Cybersecurity→ What to read after Data Engineering for Cybersecurity