Certified Network Defender v3 (CND) — Lesson 1: Network Architecture, Assets, Protocols, Trust Zones, Baselines, and Risk

Learning Objectives

• Explain the structures, services, data, settings, roles, and dependencies governing Network Architecture and Asset Inventory.
• Implement and validate Protocols, Trust Zones, and Traffic Baselines and Risk Assessment using reviewable evidence.
• Evaluate the condition where the observed result differs from the approved Network Architecture baseline because Asset Inventory scope, permissions, or prerequisites were missed and select a proportionate corrective response.

Detailed Topics

• Network Architecture applied to the course scenario, expected behavior, dependencies, controls, and evidence.
• Asset Inventory applied to the course scenario, expected behavior, dependencies, controls, and evidence.
• Protocols applied to the course scenario, expected behavior, dependencies, controls, and evidence.
• Trust Zones applied to the course scenario, expected behavior, dependencies, controls, and evidence.
• Traffic Baselines and Risk Assessment applied to the course scenario, expected behavior, dependencies, controls, and evidence.

Instructor Demonstration

The instructor traces a network defense team must protect hybrid connectivity, identify abnormal traffic, validate controls, and maintain service availability during response. The walkthrough connects tools, configuration or analysis logic, system messages, decisions, and evidence captured in the network-defense architecture, hardening checklist, monitoring cases, and response runbook. It also tests the exception where the observed result differs from the approved Network Architecture baseline because Asset Inventory scope, permissions, or prerequisites were missed.

Hands-On Exercise

Complete a controlled, authorized EC-Council exercise covering Network Architecture, Assets, Protocols, Trust Zones, Baselines, and Risk and preserve the verified result in the network-defense architecture, hardening checklist, monitoring cases, and response runbook.

1. Confirm scope, authorization, prerequisites, versions, identities, dependencies, and acceptance criteria.
2. Execute the workflow while recording settings, outputs, events, decisions, and system messages.
3. Test normal behavior, one boundary condition, and the stated exception without targeting real third-party systems.
4. Document corrections, evidence, ownership, retest criteria, rollback or recovery, and handover actions.

Scenario Analysis

• Identify which object, service, policy, setting, or sequence most strongly influences Network Architecture.
• Compare two defensible responses and explain technical, security, operational, legal, and support trade-offs.
• Determine how the network-defense architecture, hardening checklist, monitoring cases, and response runbook should be approved, retained, retested, and updated.

Troubleshooting Guidance

Start where expected behavior first differs from the observed result. Check authorization, prerequisites, identity, configuration order, data quality, version compatibility, connectivity, status, resource limits, and evidence separately. Treat “the observed result differs from the approved Network Architecture baseline because Asset Inventory scope, permissions, or prerequisites were missed” as a hypothesis until logs, settings, captured outputs, and retest outcomes confirm the cause.

Validation Checklist

• Required components, identities, permissions, settings, safety controls, and dependencies are present.
• The network-defense architecture, hardening checklist, monitoring cases, and response runbook connects each conclusion to objective, reviewable evidence.
• Normal processing, a boundary condition, dependency behavior, and the stated exception were tested.
• Corrections, ownership, retest criteria, rollback or recovery, documentation, and operational handover are complete.

Lesson Outcome

Learners can apply Network Architecture, Assets, Protocols, Trust Zones, Baselines, and Risk, explain the resulting security or operational behavior, and defend the outcome through the network-defense architecture, hardening checklist, monitoring cases, and response runbook.