Certified Cybersecurity Technician - Module 04 - Identification, Authentication and Authorization - Lab (EC-Council) (Z-Library)

【One-Line Pitch】 A hands-on lab companion for EC-Council's Certified Cybersecurity Technician Module 04, walking you step-by-step through Windows and Linux access control, role-based access in Windows Admin Center, and centralized RADIUS authentication. Best for certification candidates and junior admins who learn by doing in a virtualized lab. 【Book Arc】 - **Opening (~0%–8%)**: Frames the core problem — unauthorized access to sensitive data — and defines the three pillars (identification, authentication, authorization) before any tooling begins. - **Early (~8%–33%)**: Exercise 1 builds Windows access control: creating users, groups, and computer objects in Active Directory, then enforcing password policy through Group Policy and verifying it with `gpresult`. - **Early–Middle (~33%–50%)**: Exercise 2 shifts to Linux, covering local account and group creation, ownership, and permission bits via `chmod`, `usermod`, and `su` to test real access boundaries. - **Middle–Late (~50%–75%)**: Exercise 3 introduces Windows Admin Center, installing it, connecting a server, and applying role-based access control so a user like John gets read-only visibility instead of full control. - **Late (~75%–83%)**: Exercise 4 moves to centralized authentication, configuring a Network Policy Server as a RADIUS client/server and defining network policies tied to Windows groups. - **Ending (~83%+)**: The excerpts do not cover the closing steps of Exercise 4 or any summary/assessment material. 【Key Takeaways】 - **Identification, authentication, and authorization are distinct stages** (Opening): identification confirms who is requesting access, authentication verifies credentials, and authorization grants permissions — the book treats them as a pipeline, not synonyms. - **Windows identities are numeric under the hood** (Early): accounts map to Security Identifiers (SIDs), just as Linux uses UIDs, which matters when troubleshooting permission mismatches. - **Group Policy is the enforcement layer for password rules** (Early): editing the Default Domain Policy and exporting results with `gpresult` shows how policy becomes auditable configuration documentation. - **Linux access control is ownership plus permission bits** (Middle): creating users and groups, then setting `u/g/o` permissions with `chmod`, demonstrates least privilege at the filesystem level. - **RBAC in Windows Admin Center limits blast radius** (Late): assigning the "Windows Admin Center Readers" role lets a user view settings but blocks actions like adding storage — a practical least-privilege demonstration. - **Centralized authentication uses RADIUS and network policies** (Late): configuring NPS clients, shared secrets, and group-based conditions shows how many systems can trust one authentication authority. - **Every exercise is verification-driven** (throughout): commands like `whoami /user`, `id`, `ls -ld`, and `gpresult` are used to confirm that changes actually took effect. 【Reading Tips】 - Treat this as a lab manual, not prose: read each exercise's Objective and Lab Scenario first, then follow steps at the keyboard. - Deep-read the command syntax notes (e.g., `usermod -aG`, `chmod u=rwx,g=rwx,o=rx`) — these are the transferable skills; skim the repetitive screenshot-navigation steps. - Watch for the environment prerequisites (PfSense firewall running, specific VM credentials) since skipping them breaks later exercises. - Pay attention to the verification steps; reproducing them is the fastest way to confirm understanding before an exam. 【Coverage Limits】 This guide is based on stratified excerpts covering the module introduction and most of Exercises 1–4; the final steps of Exercise 4 and any concluding or assessment content are not covered.