Everyday Guidebooks
Cover of Security+ Network Defense by Traffic Flow

Cybersecurity & IT

Security+ Network Defense by Traffic Flow

An Unofficial Guide to Firewalls, Proxies, Intrusion Detection, and Network Segmentation

by Todd Michael

Available now

What can a firewall actually see when a user visits an encrypted website? Where does a proxy fit, and why might an intrusion detection system miss the same threat another control catches?

Security+ Network Defense by Traffic Flow turns network security concepts into a series of traceable journeys. Follow example connections from client to server through firewalls, proxies, intrusion detection systems, and segmented networks. At each checkpoint, discover what the control can observe, what decisions it can make, and where its visibility ends.

Original questions and explained answers help you practice interpreting traffic paths, comparing controls, and recognizing security trade-offs. Plain-English walkthroughs connect ports, protocols, encryption, and network architecture to the decisions defenders make.

If your search for a comptia security+ guide to network security fundamentals has left you wanting more than definitions, this unofficial guide offers a focused way to build understanding. It is not affiliated with or endorsed by CompTIA.

Contents
  1. 1. Think Like a Packet
  2. Meet Northstar Design
  3. A Flow Is More Than a Destination
  4. Separate the Path, the Decision, and the Evidence
  5. Trace Maya’s Outbound Connection
  6. Trace a Different Destination
  7. Practice Marking a Diagram
  8. What a Diagram Cannot Tell You
  9. Build the Habit
  10. 2. From Application Request to Network Conversation
  11. 3. Firewalls at the Boundary
  12. The Boundary in Our Example
  13. Rules Are Decisions, Not Descriptions
  14. Stateless Filtering: Each Packet Stands Alone
  15. Stateful Filtering: Packets in Context
  16. Inbound and Outbound Are Different Policy Questions
  17. What the Firewall Can—and Cannot—Infer
  18. A Worked Trace: Allowed Outbound, Blocked Inbound
  19. Practice: Follow the Decision
  20. 4. Address Translation and the Return Path
  21. 5. Proxies Between Users and Services
  22. 6. Encryption and Inspection Boundaries
  23. 7. Intrusion Detection and Prevention in the Path
  24. 8. Segmenting the Internal Network
  25. 9. Publishing a Service Safely
  26. 10. Remote Access and Trust Boundaries
  27. 11. Cloud and Hybrid Traffic Paths
  28. 12. Reading the Evidence Across Controls
  29. 13. Integrated Traffic-Flow Scenarios
  30. 14. Practice Questions and Explained Answers
  31. Questions
  32. Explained Answers
  33. Other Books by Todd Michael

Read a sample: Meet Northstar Design

Northstar Design is a fictional company with an office network, an internal application server, and employees who use internet services. Its environment is deliberately small enough to draw, but it contains the boundaries that matter in larger networks.

Imagine a simple diagram arranged from left to right:

Employee laptop → office network → internal router → boundary firewall → internet → customer portal

The employee laptop belongs to a user named Maya. The internal application server is connected to a separate server network reachable through the internal router. The boundary firewall sits between Northstar’s internal networks and its internet connection.

For the examples in this chapter, Maya’s laptop has the private IPv4 address 10.20.10.25, and the internal application server has 10.20.20.40. A fictional customer portal is reachable at the public IPv4 address 198.51.100.40. These addresses are labels for the exercise; they are not values to configure on a real network.

The diagram is a starting model, not a claim that every packet takes the same path or that every organization uses this design. Northstar could also have switches, wireless access points, DNS servers, proxies, intrusion detection sensors, and additional routing devices. We will add details when they help answer a question. A useful diagram includes enough of the environment to reason accurately without pretending to show everything.

Notice one important distinction immediately: Maya’s path to the internal application server and her path to the customer portal share part of the network but diverge at the internal router. Traffic destined for the internal server does not necessarily cross the internet boundary firewall. If Maya cannot reach that server, beginning with the boundary firewall may send the investigation in the wrong direction.

More Cybersecurity & IT

Cover of The White Hat Bible, Volume 1The White Hat Bible, Volume 1Available nowCover of The White Hat Bible, Volume 2The White Hat Bible, Volume 2Available nowCover of The White Hat Bible, Volume 3The White Hat Bible, Volume 3Available nowCover of The White Hat Bible, Volume 4The White Hat Bible, Volume 4Available nowThe White Hat Bible, Volume 5Available nowCover of The White Hat Pocket GuideThe White Hat Pocket GuideAvailable now

About Todd Michael

Todd Michael is an American author and the founder of ToddMichael.tv. He writes practical, plain-English books on money, health, preparedness, technology, games, humor and more.

About the author Todd Michael · Todd Michael’s author site

Part of the ToddMichael.tv network.