Prof. Dr. Larry AdamsAcademic, Author & Researcher
Cybersecurity & Digital Risk Management · Book 3

Network Security, Threat Detection and Defence

Secure Network Architecture, Monitoring and Defensive Operations

Dr. Lance Adams and Prof. Dr. Larry Adams

Free to read online. For a copy of this book, or to quote, highlight or reproduce any part of it, please request permission through the contact page beforehand.

Publication and use note

This document is an educational manuscript draft prepared for development, teaching and professional discussion. It is not legal advice, a guarantee of security, or a substitute for a qualified assessment of a specific environment. Technical configurations, product features, standards editions and legal obligations change. Before publication or operational use, verify all claims against current authoritative documentation and the relevant jurisdiction. Practical activities must be conducted only in authorised, controlled environments.

Preface

This volume forms part of the Cybersecurity & Digital Risk Management collection. It is designed to connect clear conceptual explanations with practical decisions, professional judgement and reflective learning. The aim is to help readers understand not only which controls may be useful, but why they matter, where they can fail and how their effectiveness can be evaluated.

Develop practical knowledge of network protection, segmentation, defensive monitoring and evidence-led response.

Intended readership

The material is intended for students, educators, IT and security practitioners, managers, auditors, entrepreneurs and interested readers. Readers should adapt examples to their own context and seek specialist advice where technical, contractual or legal consequences are significant.

Learning outcomes

  • Explain core TCP/IP and common network services.
  • Choose proportionate firewall, VPN, segmentation and remote-access controls.
  • Interpret sanitised logs and network indicators in context.
  • Design layered monitoring and vulnerability-management processes.
  • Document and communicate network-security decisions.

How to use this book

Read the chapters in sequence for a structured introduction, or use individual chapters as workshop material. Complete the practical tasks in a lab or with fictional data. For group learning, ask participants to state assumptions, compare alternative controls and explain the trade-offs between security, usability, cost, privacy and availability.

Contents

  • Chapter 1: Network Fundamentals for Defenders
  • Chapter 2: Firewalls and Access Rules
  • Chapter 3: VPNs, Wireless and Remote Access
  • Chapter 4: Segmentation and Secure Network Architecture
  • Chapter 5: Intrusion Detection and Endpoint Telemetry
  • Chapter 6: Vulnerability Management and Secure Services
  • Chapter 7: Network Logs and Traffic Analysis
  • Chapter 8: Operational Defence and Continuous Improvement
  • Applied case study
  • Practical activities and assessment
  • Glossary
  • Selected references and further reading

Chapter 1: Network Fundamentals for Defenders

Networks move data between endpoints through addressing, routing, switching and protocols. Defenders need enough understanding of normal communication to recognise deviations. TCP provides reliable, ordered delivery; UDP supports connectionless communication used by many real-time and query-based services. DNS maps names to records, DHCP assists address configuration and TLS protects many application connections in transit.

A protocol's normal purpose does not make every use benign. An unusual destination, volume or timing may deserve review, but context is essential. Network telemetry should be interpreted alongside identity, endpoint and application records. Avoid treating a single indicator as proof of compromise without corroborating evidence.

Chapter application

Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.

Reflection questions

  • What are the three most important ideas from this chapter on network fundamentals for defenders?
  • Which assumptions would need to be verified before applying this guidance in a real environment?
  • What evidence would demonstrate that the proposed controls are operating effectively?

Chapter 2: Firewalls and Access Rules

Firewalls enforce traffic policy at network boundaries or between workloads. A well-managed rule should state its business purpose, owner, source, destination, service, expiry or review date, and approval. Broad rules are easier to create but harder to justify and can increase the blast radius of a compromised device. Default-deny principles can reduce exposure when paired with a reliable process for allowing required traffic.

Rule reviews should identify shadowed rules, obsolete access, overly broad ranges and temporary exceptions that became permanent. Changes should be tested and recorded. Emergency changes need retrospective review so that speed does not become a route around governance.

Chapter application

Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.

Reflection questions

  • What are the three most important ideas from this chapter on firewalls and access rules?
  • Which assumptions would need to be verified before applying this guidance in a real environment?
  • What evidence would demonstrate that the proposed controls are operating effectively?

Chapter 3: VPNs, Wireless and Remote Access

Remote access connects users and devices to services outside a traditional office boundary. Use strong authentication, supported clients, device posture checks where available and access limited to the resources needed. A VPN can protect traffic over an untrusted network, but a compromised endpoint can still expose data and credentials. Zero-trust approaches evaluate identity, device, context and requested resource rather than trusting a connection merely because it originates inside a network.

Wireless security requires modern encryption, strong administrative credentials, firmware updates and separation of guest devices from internal services. Public Wi-Fi should be treated as an untrusted network. Organisations should provide clear guidance for travel, lost devices, suspicious captive portals and remote-work emergencies.

Chapter application

Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.

Reflection questions

  • What are the three most important ideas from this chapter on vpns, wireless and remote access?
  • Which assumptions would need to be verified before applying this guidance in a real environment?
  • What evidence would demonstrate that the proposed controls are operating effectively?

Chapter 4: Segmentation and Secure Network Architecture

Segmentation divides an environment into zones with controlled communication. Typical zones include user devices, servers, management systems, guest wireless, development environments and critical services. The design should follow business flows and trust boundaries, not simply organisational charts. Sensitive administrative interfaces should be reachable only through approved paths.

A network diagram is useful only when maintained. Document key assets, trust boundaries, external connections, dependencies and owners. Validate the design with controlled tests and configuration reviews. Segmentation reduces lateral movement opportunities but cannot eliminate risk if credentials, endpoint controls or inter-zone policies are weak.

Chapter application

Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.

Reflection questions

  • What are the three most important ideas from this chapter on segmentation and secure network architecture?
  • Which assumptions would need to be verified before applying this guidance in a real environment?
  • What evidence would demonstrate that the proposed controls are operating effectively?

Chapter 5: Intrusion Detection and Endpoint Telemetry

Intrusion detection systems identify patterns associated with suspicious activity; prevention systems may also block selected traffic. Endpoint detection tools provide additional visibility into process behaviour, file activity and account use. Each source has blind spots, so layered detection is more reliable than relying on one product. Detection rules should be tested against expected normal activity and known safe scenarios.

A useful alert explains what occurred, why it matters, which assets are involved and what action is expected. Analysts should record evidence, confidence, scope and next steps. Detection logic should be reviewed after incidents and after major changes to applications or network design.

Chapter application

Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.

Reflection questions

  • What are the three most important ideas from this chapter on intrusion detection and endpoint telemetry?
  • Which assumptions would need to be verified before applying this guidance in a real environment?
  • What evidence would demonstrate that the proposed controls are operating effectively?

Chapter 6: Vulnerability Management and Secure Services

Vulnerability management includes asset discovery, scanning, validation, prioritisation, remediation and verification. A severity score is useful but not sufficient: exploitability, internet exposure, asset criticality, compensating controls and business impact also matter. Unsupported devices and forgotten services can be especially risky because teams may not know they exist or may be unable to patch them.

Scanning must be authorised and scoped. Production systems can be disrupted by poorly planned testing, so coordinate timing, rate limits and emergency contacts. After remediation, verify that the change addressed the issue and did not introduce a new weakness. Exceptions should have owners, expiry dates and compensating controls.

Chapter application

Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.

Reflection questions

  • What are the three most important ideas from this chapter on vulnerability management and secure services?
  • Which assumptions would need to be verified before applying this guidance in a real environment?
  • What evidence would demonstrate that the proposed controls are operating effectively?

Chapter 7: Network Logs and Traffic Analysis

Network logs may include connection metadata, DNS queries, firewall decisions, authentication events and proxy activity. Start with a defined hypothesis and a relevant time window. Establish normal behaviour, compare multiple data sources and account for clock differences, NAT, shared infrastructure and incomplete collection. Data minimisation matters because telemetry can reveal personal habits and sensitive business activity.

A defensible investigation records the question, data source, query or filter, time range, observations and limitations. Do not infer intent from a single connection. Escalate suspicious patterns through approved procedures and protect collected logs from unauthorised access.

Chapter application

Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.

Reflection questions

  • What are the three most important ideas from this chapter on network logs and traffic analysis?
  • Which assumptions would need to be verified before applying this guidance in a real environment?
  • What evidence would demonstrate that the proposed controls are operating effectively?

Chapter 8: Operational Defence and Continuous Improvement

Network defence depends on people and process as much as devices. Define who monitors alerts, approves changes, manages exceptions and communicates incidents. Track metrics that support decisions—such as time to triage, overdue critical vulnerabilities, coverage of important assets and successful recovery tests—rather than metrics that merely count activity.

After an incident or exercise, identify root causes without reducing the review to individual blame. Improvements may include clearer ownership, safer defaults, better logging, staff training or a simpler change process. Assign each action an owner and deadline, then verify completion.

Chapter application

Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.

Reflection questions

  • What are the three most important ideas from this chapter on operational defence and continuous improvement?
  • Which assumptions would need to be verified before applying this guidance in a real environment?
  • What evidence would demonstrate that the proposed controls are operating effectively?

Integrated case study

An organisation sees repeated authentication failures followed by a successful login from an unfamiliar location and a change to a firewall rule. Analysts should correlate identity and administrative logs, confirm whether the activity matches an approved change, preserve relevant records and follow the incident process rather than immediately assuming either maliciousness or legitimacy.

Case study analysis

  • Identify the important assets, stakeholders and business objectives.
  • Describe the likely threat scenarios and the evidence needed to assess them.
  • Recommend immediate actions and longer-term preventive improvements.
  • Explain how the organisation should document decisions and measure effectiveness.
  • Identify privacy, legal, ethical or operational considerations that require specialist review.

Practical activities and assessment

  • Create a segmented office-network diagram and explain each trust boundary.
  • Review a fictional firewall rule set and propose least-privilege changes.
  • Analyse sanitised authentication and DNS logs using a written hypothesis.
  • Draft a vulnerability remediation policy with severity, business context and exception handling.

Suggested assessment rubric

Glossary of key terms

Asset: Something of value to an individual or organisation, including data, services, identities and systems.

Authentication: A process used to establish that a user, device or service is the entity it claims to be.

Confidentiality: Protection against unauthorised disclosure of information.

Control: A safeguard or process intended to modify risk.

Incident: An event that compromises or threatens the security or operation of systems, services or information.

Least privilege: The principle of granting only the access and permissions needed for a defined task.

Residual risk: Risk remaining after controls and treatment decisions are considered.

Resilience: The ability to anticipate, withstand, recover from and adapt to disruption.

Threat: A potential cause of unwanted harm.

Vulnerability: A weakness that could be exploited or otherwise contribute to harm.

Selected standards and further reading

The following are starting points for verification and further study. Confirm the current edition, applicability and licensing conditions before quoting or relying on a standard.

  • National Institute of Standards and Technology (NIST). Cybersecurity Framework (CSF) 2.0. NIST, 2024.
  • International Organization for Standardization. ISO/IEC 27001, Information security management systems — Requirements. Consult the current edition.
  • International Organization for Standardization. ISO/IEC 27002, Information security controls. Consult the current edition.
  • International Organization for Standardization. ISO 31000, Risk management — Guidelines. Consult the current edition.
  • Center for Internet Security. CIS Critical Security Controls. Consult the current version.
  • National Institute of Standards and Technology. NIST Privacy Framework. Consult the current version.
  • OWASP Foundation. OWASP Top 10 and other relevant application-security guidance. Consult the current version.
  • National Institute of Standards and Technology. Relevant SP 800-series publications on security, privacy, incident response and contingency planning; verify the publication status and current revision.

Editorial development checklist

  • Verify every technical claim and update examples to reflect current practice.
  • Add properly sourced APA 7 in-text citations throughout the manuscript before publication.
  • Review jurisdiction-specific legal and regulatory sections with qualified advisers.
  • Add diagrams, figures and accessible alt text where they materially aid understanding.
  • Conduct technical peer review and copy-editing; validate all exercises in authorised lab settings.
  • Add index, acknowledgements, final copyright details and publisher information when known.