C2M1 Reading: Device Setup and Configuration Overview

Asset Type: New reading
Target Length: 500–600 words
Lesson: C2M1 Lesson 1: Device Configuration Basics

Purpose

Introduce the device lifecycle, user lifecycle management, and IT asset management systems. Explain how these processes work together to support device setup, tracking, assignment, maintenance, and retirement in an organization.

Prior Knowledge

Learners have explored how devices, operating systems, applications, and users interact within technology systems in Course 1 and the introductory Course 2 video. They understand that changes or problems in one component can affect other parts of a system.

Reading Objective

Describe how device lifecycle management, user lifecycle management, and IT asset management systems support device setup and configuration in an organization.

Content Outline

1. Introduction

• Explain that IT support professionals help manage devices throughout their useful lives, not just during initial setup.
• Connect device management to the needs of employees and organizations.
• Introduce the relationship between device lifecycle management, user lifecycle management, and asset management.

2. The Device Lifecycle

Introduce the device lifecycle as the stages equipment moves through from acquisition to retirement.

Cover the following stages:

• Acquisition: Purchasing or obtaining devices based on organizational requirements.
• Preparation and deployment: Configuring and assigning devices for organizational use.
• Active use and maintenance: Supporting devices, applying updates, and addressing problems.
• Reassignment or replacement: Preparing devices for another user or replacing outdated equipment.
• Retirement and disposal: Removing devices from service, protecting organizational data, and following disposal policies.

Include a simple diagram illustrating the device lifecycle.

Emphasize that IT professionals may support different stages depending on their responsibilities.

3. User Lifecycle Management

Introduce user lifecycle management as the process of managing employee technology needs and access as their responsibilities change.

Explain three common stages:

• Onboarding: Providing devices, accounts, applications, and appropriate access to new employees.
• Role changes: Updating device assignments, software, or permissions when employees change responsibilities.
• Offboarding: Recovering devices, removing access, and preparing equipment for reassignment or retirement.

Provide a workplace example of an employee transferring to another department and requiring different software or device access.

Explain that IT professionals follow approved requests and organizational policies when making these changes.

4. IT Asset Management Systems

Introduce IT asset management (ITAM) and explain how organizations use asset management systems to track technology equipment.

Describe common information maintained in an asset record:

• Asset identification number
• Manufacturer, model, and serial number
• Assigned user or department
• Device location
• Purchase and warranty information
• Device status

Explain how asset management systems help organizations locate equipment, track assignments, schedule replacements, and maintain accurate inventory records.

Include a simplified example of an asset management record for an employee laptop.

5. How These Processes Work Together

Use a new employee onboarding scenario to demonstrate how the three processes connect.

• A new employee is hired, creating a need for equipment and access.
• IT identifies an available device or obtains a new one.
• The device moves into the preparation and deployment stage.
• IT updates the asset management system to record the assignment.

Explain that coordinating these processes helps organizations maintain accurate records and ensure employees receive appropriate technology.

6. Key Takeaways

• Device lifecycle management tracks equipment from acquisition through retirement.
• User lifecycle management addresses changing employee technology and access needs.
• IT asset management systems maintain records of organizational equipment.
• These processes work together to support organized, consistent device management.

Future Learning

In the next video, Preparing Devices for Deployment, learners will explore how IT professionals prepare new or repurposed devices for organizational use. The video introduces asset identification, device configuration, software installation, security protections, and automated deployment technologies.

Later in the module, learners will examine firmware settings, desktop and mobile device configuration, and device readiness checks.

Out of Scope

• Detailed device configuration procedures
• Asset tagging instructions
• MDM, EMM, and UEM platforms
• Zero-touch provisioning
• Operating system installation
• Security configuration
• Device readiness checks

Writer Guidance

Keep the reading introductory and focused on the organizational processes that support device management. Use a consistent workplace example to connect the three concepts. Include a device lifecycle diagram and a sample asset record where helpful.

Avoid duplicating the following video, Preparing Devices for Deployment, which explains the actual preparation workflow, including identification, configuration, software installation, security protections, and automated deployment.

C2M1 Reading: Firmware and Configuration

Asset Type: New reading
Target Length: 600–700 words
Lesson: C2M1 Lesson 1: Device Configuration Basics

Purpose

Introduce system firmware, BIOS/UEFI, and the boot process. Explain how firmware initializes hardware and transfers control to the operating system.

Prior Knowledge

Learners understand the relationship between hardware, operating systems, and applications. They have also explored how IT professionals prepare devices for deployment.

Reading Objective

Explain how system firmware and the boot process prepare hardware and load an operating system.

Content Outline

1. Introduction

• Explain why hardware must be initialized before an operating system can run.
• Introduce firmware as software that provides low-level instructions for hardware.

2. Understanding System Firmware

• Define system firmware and its purpose.
• Introduce BIOS (Basic Input/Output System) and UEFI (Unified Extensible Firmware Interface).
• Explain that UEFI is the modern successor to traditional BIOS.
• Briefly distinguish firmware from operating systems and applications.
• Explain how firmware initializes hardware and prepares the system to load an operating system.

3. The Computer Boot Process

Explain the startup sequence:

1. Power On and CPU Initialization: The processor begins executing firmware instructions.
2. Firmware Initialization and POST: Firmware initializes and checks essential hardware.
3. Boot Device Selection: Firmware identifies a bootable device. Introduce NVRAM as storage for persistent UEFI configuration information, including boot entries.
4. EFI System Partition (ESP): Introduce the partition that commonly stores UEFI boot files.
5. Bootloader Execution: The bootloader starts the operating system.
6. OS Kernel Initialization: The kernel begins managing hardware resources, memory, and processes.
7. System Services and User Space: Background services start, and the system prepares for user interaction.

Include a simplified boot process diagram.

4. Firmware and Startup Issues

• Explain how the startup sequence helps identify where problems occur.
• Provide examples: POST failure, missing boot device, operating system failing to load.
• Emphasize observing symptoms and following approved procedures before changing firmware settings.

5. Key Takeaways

• Firmware initializes hardware before the operating system loads.
• BIOS/UEFI manages the early startup process.
• The bootloader transfers the startup process to the operating system.
• Understanding the boot sequence helps identify potential startup issues.

Future Learning

The following reading, BIOS/UEFI Settings, introduces boot order, firmware passwords, TPM, and virtualization support. Later lessons apply startup knowledge to device configuration and troubleshooting.

Out of Scope

• Detailed BIOS/UEFI configuration
• Firmware update procedures
• TPM and Secure Boot configuration
• Virtualization setup
• Advanced bootloader configuration
• Operating system installation and recovery
• Detailed startup troubleshooting

Writer Guidance

Use a simple boot sequence diagram and explain technical terms at an introductory level. Focus on what happens during startup and why each stage matters. Avoid detailed configuration procedures, which are addressed in subsequent assets.

C2M1 Reading: BIOS/UEFI Settings

Asset Type: New reading
Target Length: 500–600 words
Lesson: C2M1 Lesson 1: Device Configuration Basics

Purpose

Introduce common BIOS/UEFI configuration settings and explain how they affect device startup, security, and hardware capabilities.

Prior Knowledge

Learners understand the role of system firmware and the boot process, including how BIOS/UEFI initializes hardware and transfers control to the operating system.

Reading Objective

Describe common BIOS/UEFI settings and explain their roles in device startup, security, and configuration.

Content Outline

1. Introduction

• Explain that BIOS/UEFI provides settings that influence device startup, security, and hardware capabilities.
• Describe why IT support professionals may need to inspect these settings when preparing or troubleshooting devices.

2. Accessing BIOS/UEFI Settings

• Explain how firmware settings are accessed during startup or through supported operating system options.
• Note that interfaces and available settings vary by manufacturer.
• Emphasize documenting existing settings before making changes.

3. Common BIOS/UEFI Settings

Boot Order

• Explain how boot priority determines which boot entries or devices are used during startup.
• Example: Internal storage versus USB installation media.

Supervisor/BIOS Passwords

• Explain how firmware passwords restrict unauthorized configuration changes.
• Distinguish firmware passwords from operating system login passwords.

Trusted Platform Module (TPM)

• Introduce TPM as a hardware-based security technology that protects cryptographic keys.
• Explain that TPM capabilities may be implemented through a dedicated chip or integrated firmware.
• Connect TPM to device encryption and security features.

Secure Boot

• Introduce Secure Boot as a UEFI security feature that helps prevent unauthorized boot software from loading.
• Explain its purpose without covering configuration procedures.

Virtualization Support

• Explain how BIOS/UEFI settings control processor virtualization capabilities.
• Connect virtualization to running virtual machines.

4. Safe Firmware Configuration Practices

• Explain how incorrect settings can affect startup, functionality, or security.
• Emphasize following organizational procedures and obtaining authorization before changing settings.
• Example: Checking whether virtualization is enabled without changing unrelated settings.

5. Key Takeaways

• BIOS/UEFI settings influence startup, security, and hardware capabilities.
• Boot order, firmware passwords, TPM, Secure Boot, and virtualization support serve different purposes.
• IT professionals should inspect and modify firmware settings carefully.

Future Learning

Learners will apply these concepts when exploring desktop device configuration, security features, and virtual machines later in Course 2.

Out of Scope

• Detailed manufacturer-specific BIOS/UEFI navigation
• Firmware updates and flashing procedures
• Password recovery or bypass techniques
• Advanced TPM administration
• Secure Boot configuration procedures
• Advanced virtualization configuration
• Operating system installation procedures

Writer Guidance

Use a labeled BIOS/UEFI settings interface to help learners recognize common configuration options. Focus on what each setting controls, why it matters, and when an IT professional might encounter it. Avoid repeating the boot process covered in the preceding reading. Keep examples introductory and emphasize safe, authorized configuration practices.

C2M1 Reading: Configuring Desktop Devices

Asset Type: New reading
Target Length: 700–800 words
Lesson: C2M1 Lesson 2: Device Readiness Workflows

Purpose

Explain common desktop deployment methods and initial configuration requirements across Windows, Linux, macOS, and ChromeOS. Introduce how hardware, firmware, security, and identity settings contribute to device readiness.

Prior Knowledge

Learners understand the device lifecycle, deployment preparation, firmware, and BIOS/UEFI settings. They have also been introduced to centralized device management and automated provisioning.

Reading Objective

Compare desktop deployment methods and identify common configuration steps across Windows, Linux, macOS, and ChromeOS.

Content Outline

1. Introduction

• Explain how desktop configuration prepares computers for organizational use.
• Introduce common configuration requirements across operating systems.
• Emphasize that configuration methods vary by organization, device, and operating system.

2. Desktop Deployment Methods

Imaging and Cloning

• Explain how imaging uses a prepared system image to deploy standardized configurations.
• Distinguish imaging from cloning an existing device or drive.
• Provide a common workplace use case.

Zero-Touch Provisioning

• Briefly reinforce automated provisioning introduced in the deployment video.
• Compare imaging and cloning with zero-touch provisioning.
• Explain why organizations may use different deployment approaches.

3. Hardware, Firmware, and Security Readiness

• Explain the importance of verifying hardware compatibility and firmware settings.
• Reinforce BIOS/UEFI, Secure Boot, and TPM as configuration requirements.
• Focus on verifying these features rather than redefining them.
• Connect hardware and security readiness to organizational requirements.

4. Identity and Organizational Enrollment

• Explain why devices must be associated with approved users and management systems.
• Introduce domain joining and centralized identity management.
• Explain cloud identity and cloud-based device enrollment.
• Distinguish local accounts from organizational accounts.

5. Initial Desktop Configuration Workflow

Introduce a common sequence used when preparing desktop devices:

1. Initial setup: Complete operating system setup and verify hardware recognition.
2. Identity: Establish appropriate user accounts or organizational enrollment.
3. Connectivity: Configure network connections and required device settings.
4. Updates and security: Apply required updates and verify security settings.
5. Readiness verification: Confirm that the device meets organizational requirements.

Explain that the specific tools and procedures vary by operating system.

6. Configuration Across Operating Systems

Briefly compare how the common configuration workflow applies to each platform.

Windows

• Initial setup and updates
• Local accounts, domain joining, and cloud identity
• Organizational management and security settings

Linux

• Distribution setup and updates
• Local users, permissions, and connectivity
• Organizational management where applicable

macOS

• Initial setup and updates
• Local and managed accounts
• Organizational enrollment, management profiles, and security settings

ChromeOS

• Initial setup and Google account authentication
• Organizational enrollment and managed policies
• Cloud-based management and updates

Include a comparison table highlighting differences in identity, enrollment, and management across the four operating systems.

7. Key Takeaways

• Imaging, cloning, and zero-touch provisioning support different deployment needs.
• Desktop configuration follows a common sequence across operating systems.
• Hardware, firmware, security, and identity settings contribute to device readiness.
• Windows, Linux, macOS, and ChromeOS use different tools to accomplish similar configuration tasks.

Future Learning

The following readings explore mobile device configuration, mobile device management, and device readiness checklists. Learners will apply these concepts when evaluating whether devices are prepared for organizational use.

Out of Scope

• Step-by-step operating system installation
• Detailed imaging, cloning, or zero-touch procedures
• Vendor-specific deployment platform instructions
• Advanced BIOS/UEFI, TPM, or Secure Boot configuration
• Active Directory administration
• Advanced identity and access management
• Enterprise infrastructure design
• Detailed troubleshooting procedures

Writer Guidance

Focus on the common desktop configuration workflow and how it differs across Windows, Linux, macOS, and ChromeOS. Include a concise comparison table and practical IT support examples.

Avoid repeating detailed explanations of firmware, BIOS/UEFI, TPM, and Secure Boot from previous readings. Emphasize how these features are verified during device preparation.

Keep the content appropriate for entry-level IT support professionals and avoid detailed enterprise administration procedures.

C2M1 Reading: Configuring Mobile Devices

Asset Type: New reading
Target Length: 700–800 words
Lesson: C2M1 Lesson 2: Device Readiness Workflows

Purpose

Introduce mobile device configuration in organizational environments, including device ownership models, enrollment, application provisioning, data separation, and security controls. Compare Android and iOS configuration considerations and explain how organizations balance security, management, employee privacy, and IT support responsibilities.

Prior Knowledge

Learners understand device deployment methods, organizational enrollment, identity management, and security requirements for desktop devices. They have also been introduced to centralized device management.

Reading Objective

Compare mobile device ownership models and identify common configuration, security, and management requirements for Android and iOS devices.

Content Outline

1. Introduction

• Explain how organizations configure smartphones and tablets for workplace use.
• Identify differences between mobile and desktop configuration, including portability, personal data, and remote management.
• Introduce the importance of device ownership and organizational policies.

2. Mobile Device Ownership Models

Corporate-Owned, Personally Enabled (COPE)

• Explain how organizations provide devices that employees may also use for approved personal activities.
• Introduce the need to separate personal and organizational data.

Corporate-Owned, Business-Only (COBO)

• Explain how organizations provide devices restricted to business use.
• Describe the security and management advantages of greater organizational control.

Bring Your Own Device (BYOD)

• Introduce employee-owned devices used for work.
• Explain why some organizations restrict BYOD support due to privacy, security, and management concerns.

Ownership and Support Trade-offs

• Compare the three models in terms of organizational control, employee privacy, and IT support responsibilities.
• Explain how ownership models affect IT’s ability to configure, troubleshoot, and support devices.
• Explain that personally owned devices may have more limited support options because of privacy and organizational policy restrictions.

Include a comparison table highlighting differences in organizational control, privacy, and support responsibilities.

3. Mobile Device Enrollment and Configuration

• Explain how enrollment connects a mobile device to organizational management.
• Introduce manual and automated enrollment methods.
• Describe common configuration requirements:
  • User authentication and organizational accounts
  • Network and connectivity settings
  • Required applications and app provisioning
  • Security policies and operating system updates
• Explain how enrollment and configuration differ depending on ownership model and organizational requirements.

4. Protecting Organizational Data

Containerization and Data Separation

• Explain how organizations separate work applications and data from personal information.
• Introduce managed applications and work profiles.
• Describe the benefits of separating organizational and personal data.

Remote and Selective Wipes

• Distinguish between removing organizational data and erasing an entire device.
• Explain when these capabilities may be used, such as lost devices or employee departures.
• Address privacy and legal considerations, particularly for personally owned devices.

5. Android and iOS Configuration Considerations

• Compare Android and iOS approaches to organizational enrollment and management.
• Introduce Android work profiles and managed device options.
• Introduce Apple device supervision and managed enrollment.
• Explain that available management capabilities depend on device ownership, enrollment method, and organizational policies.

Include a concise comparison table highlighting common enrollment and data separation approaches.

6. Mobile Device Support and Incident Response

• Explain common support considerations, including enrollment failures, application access issues, and lost devices.
• Explain how device ownership and enrollment determine which actions IT can take when a device is lost, stolen, or compromised.
• Distinguish reporting an incident from performing an authorized remote or selective wipe.
• Introduce the importance of following organizational incident response procedures.
• Emphasize documenting, reporting, and escalating security-related issues rather than independently performing unauthorized actions.

7. Key Takeaways

• Mobile device configuration depends on ownership, enrollment, and organizational requirements.
• COPE, COBO, and BYOD provide different levels of organizational control, privacy, and IT support responsibilities.
• Containerization, selective wipes, and remote wipes help protect organizational data.
• Android and iOS provide different management capabilities for workplace devices.
• Device ownership and enrollment influence the actions IT professionals can take when supporting devices or responding to incidents.

Future Learning

The following reading, Mobile Device Management (MDM), explores how organizations centrally configure, secure, monitor, and update mobile devices using management platforms.

Learners will then examine device readiness checklists used to verify that desktop and mobile devices meet organizational requirements.

Out of Scope

• Step-by-step Android or iOS enrollment procedures
• Detailed MDM platform configuration
• Vendor-specific management console instructions
• Advanced mobile security administration
• Mobile application development
• Detailed incident response procedures
• Legal analysis of employee privacy and device ownership

Writer Guidance

Focus on the practical differences between mobile device ownership models and how those differences affect configuration, security, privacy, and support.

Include a comparison of COPE, COBO, and BYOD, along with introductory Android and iOS examples. Emphasize how device ownership and enrollment influence the level of organizational control and the actions IT support professionals are authorized to perform.

Explain that BYOD policies vary by organization rather than suggesting that all organizations prohibit employee-owned devices.

Keep centralized management platform capabilities introductory, since the following reading covers MDM in greater detail. Use realistic workplace examples, particularly involving lost devices or employee departures, to illustrate the relationship between ownership, data protection, and authorized incident response.

C2M1 Reading: Mobile Device Management (MDM)

Asset Type: New reading
Target Length: 450–550 words
Lesson: C2M1 Lesson 2: Device Readiness Workflows

Purpose

Explain how organizations use mobile device management (MDM) platforms to centrally configure, secure, deploy applications to, and maintain devices across office, remote, and hybrid environments.

Prior Knowledge

Learners have been introduced to mobile device ownership models, enrollment, application provisioning, data separation, and security considerations for Android and iOS devices.

Reading Objective

Explain how MDM platforms support centralized device configuration, application deployment, security policies, and ongoing maintenance.

Content Outline

1. Introduction to MDM

• Define MDM and explain its role in centralized device management.
• Briefly distinguish MDM from broader enterprise mobility management (EMM) and unified endpoint management (UEM).
• Explain why centralized management is useful for organizations with remote and hybrid employees.

2. Centralized Configuration and Application Deployment

• Explain how configuration profiles apply consistent organizational settings to enrolled devices.
• Provide examples such as Wi-Fi, authentication, encryption, and screen lock settings.
• Explain how MDM platforms automate application installation, updates, and removal.
• Introduce Microsoft Intune as an example of a platform that supports these capabilities.

3. Security Policies and Compliance

• Explain how MDM platforms help protect organizational data through security policies.
• Distinguish configuration profiles, which apply settings, from compliance policies, which evaluate whether devices meet requirements.
• Introduce compliance monitoring, access restrictions, and authorized remote management actions.
• Reinforce that available controls depend on device ownership, enrollment, and platform capabilities.

4. Operating System Updates and Device Maintenance

• Explain how MDM platforms help IT teams distribute or coordinate operating system updates.
• Describe how centralized monitoring helps identify devices requiring updates or attention.
• Provide a brief example of an organization using Microsoft Intune to deploy applications, apply security policies, and monitor devices across multiple locations.

5. Key Takeaways

• MDM provides centralized management of organizational devices.
• Configuration profiles, application deployment, and security policies support consistent device readiness.
• Compliance monitoring and operating system updates help organizations maintain devices throughout their lifecycle.

Future Learning

The following reading, Using a Device-Readiness Checklist, explores how IT professionals verify operating system settings, user accounts, authentication, permissions, and network connectivity before devices are assigned to users.

Out of Scope

• Step-by-step Microsoft Intune configuration
• Detailed enrollment procedures
• Advanced EMM and UEM architecture
• Vendor-specific administration consoles
• Advanced compliance policy administration
• Detailed remote wipe procedures
• Enterprise identity and security administration

Writer Guidance

Keep the reading focused on the core capabilities of MDM platforms rather than detailed administrative procedures. Use Microsoft Intune as a practical example, not a tutorial.

Avoid repeating ownership models, enrollment procedures, containerization, and selective wipes from the previous reading. Briefly introduce EMM and UEM terminology without expanding into their architectures.

Include a simple diagram showing centralized management of devices across multiple locations.

C2M1 Reading: Using a Device-Readiness Checklist

Asset Type: New reading
Target Length: 500–600 words
Lesson: C2M1 Lesson 2: Device Readiness Workflows

Purpose

Explain how IT support professionals use device-readiness checklists to verify that computers and mobile devices meet organizational requirements before being assigned to users. Introduce common verification steps involving operating system settings, user accounts, authentication, permissions, and network connectivity.

Prior Knowledge

Learners have been introduced to desktop and mobile device configuration, organizational enrollment, and centralized device management. They understand that devices must meet organizational configuration and security requirements before deployment.

Reading Objective

Identify common device-readiness checks and explain how checklists support consistent device deployment and management.

Content Outline

1. Introduction to Device-Readiness Checklists

• Define a device-readiness checklist and explain its purpose.
• Explain why organizations verify device configurations before assigning equipment to users.
• Connect checklists to consistent deployment, security, documentation, and IT asset management.
• Explain how readiness checklists also support device reassignment, replacement, and routine maintenance.
• Emphasize that checklists vary depending on the device, operating system, and organizational requirements.

2. Common Device-Readiness Checks

Introduce the primary areas IT professionals verify before deployment.

Operating System Readiness

• Confirm the correct operating system is installed and functioning.
• Verify required updates and basic security settings.
• Confirm required applications are available.

User Accounts and Authentication

• Verify that the appropriate user accounts are configured.
• Confirm organizational enrollment or identity connections when required.
• Check that approved authentication methods are available.

Permissions and Access

• Verify that users have appropriate access to required resources.
• Reinforce the principle of least privilege.
• Confirm that administrative access is restricted according to organizational policies.

Network Connectivity

• Verify that the device connects to the required network.
• Confirm access to necessary organizational resources.
• Identify basic connectivity issues that could prevent device use.

3. Using a Checklist in a Workplace Scenario

• Present a scenario involving an IT support technician preparing a laptop for a new employee.
• Walk through a simplified readiness checklist:
  • Verify operating system and updates.
  • Confirm user account and authentication.
  • Check permissions and required applications.
  • Test network connectivity.
  • Record results and identify any outstanding issues.
• Introduce three possible outcomes for each checklist item:
  • Pass: The device meets the requirement.
  • Fail: The device does not meet the requirement and needs attention.
  • Not Applicable: The requirement does not apply to the device or its intended use.
• Explain what happens when a device fails a readiness check, including correcting approved configuration issues or escalating problems.
• Emphasize documenting verification results before releasing the device.

Include a sample device-readiness checklist showing the verification item, expected condition, result, and any notes or required follow-up.

4. Key Takeaways

• Device-readiness checklists support consistent and secure deployment and ongoing device management.
• Operating system settings, authentication, permissions, and connectivity are common verification areas.
• Pass, Fail, and Not Applicable results help IT professionals document device readiness.
• IT professionals address or escalate failed checks before assigning devices to users.
• Checklists also support device reassignment, replacement, and routine maintenance.

Future Learning

Learners will build on these device preparation and readiness concepts when exploring hardware safety, operating system tools, and practical device support activities later in Course 2.

Out of Scope

• Step-by-step operating system configuration
• Detailed account provisioning procedures
• Advanced permissions administration
• Detailed network troubleshooting
• Vendor-specific device management tools
• Advanced security configuration
• Enterprise deployment automation

Writer Guidance

Focus on how IT support professionals use checklists to verify device readiness rather than repeating configuration procedures covered in previous readings.

Include a realistic workplace scenario and a simple checklist demonstrating what technicians verify before releasing a device to a user. The checklist should include expected conditions, Pass/Fail/Not Applicable results, and space for notes or follow-up actions.

Emphasize that checklists are useful beyond initial deployment, including device reassignment, replacement, and routine maintenance.

Explain that failed readiness checks should be documented and resolved or escalated before deployment. Keep the examples appropriate for entry-level IT support professionals and avoid detailed technical procedures.

C2M1 Reading: Personal Safety

Asset Type: New reading
Target Length: 500–600 words
Lesson: C2M1 Lesson 3: Hardware Safety

Purpose

Explain how IT support professionals protect themselves from injury when working with computer hardware. Introduce personal safety precautions involving electrical hazards, proper equipment handling, lifting techniques, sharp edges, and cable safety.

Prior Knowledge

Learners have been introduced to hardware safety practices, including powering down equipment, electrostatic discharge (ESD) protection, safe component handling, cleaning, and electronic waste disposal in the preceding Hardware Safety video.

Reading Objective

Identify personal safety risks associated with IT hardware work and describe appropriate precautions to prevent injury.

Content Outline

1. Introduction to Personal Safety

• Explain why personal safety is a fundamental responsibility when working with IT equipment.
• Distinguish protecting technicians from injury from protecting electronic components against damage.
• Introduce the importance of following organizational safety policies and manufacturer instructions.

2. Electrical Safety

• Identify common electrical hazards associated with computer equipment, power cords, outlets, and internal components.
• Reinforce the importance of disconnecting equipment from power before performing authorized maintenance.
• Explain that some components retain electrical energy even after equipment is disconnected.
• Emphasize that technicians should never open power supplies or work on energized equipment without appropriate authorization and training.
• Clarify that ESD protection does not replace electrical shock protection.

3. Physical Safety and Equipment Handling

Lifting and Moving Equipment

• Explain how improper lifting or moving equipment can cause injury.
• Introduce safe lifting practices, including assessing equipment weight, using appropriate lifting techniques, and requesting assistance when necessary.

Sharp Edges and Exposed Components

• Identify risks from sharp metal edges, exposed components, and damaged equipment.
• Explain when appropriate personal protective equipment (PPE), such as safety glasses or protective gloves, may be required.

Cable Safety

• Explain safe cable handling practices, including disconnecting cables by their connectors rather than pulling on the cords.
• Identify risks associated with damaged, frayed, or improperly routed cables.
• Emphasize keeping cables organized to prevent accidental equipment damage and personal injury.

4. Basic Ergonomic Awareness

• Briefly define ergonomics and explain its relationship to preventing workplace injuries.
• Introduce the importance of maintaining comfortable working positions and avoiding unnecessary physical strain.
• Note that ergonomic hazards and repetitive strain injuries will be explored further in the following reading.

5. Recognizing Unsafe Conditions

• Explain the importance of recognizing when a task presents a personal safety risk.
• Provide examples such as damaged power cords, exposed wiring, unstable equipment, or unusually hot devices.
• Emphasize stopping work, securing the area when safe, and reporting hazards through organizational procedures.
• Reinforce that IT support professionals should not attempt repairs beyond their training or authorization.

6. Key Takeaways

• Personal safety protects IT professionals from electrical and physical injuries.
• Proper lifting techniques, safe cable handling, and awareness of sharp edges reduce the risk of injury.
• Appropriate PPE and safe work practices help protect technicians.
• Technicians should recognize unsafe conditions and follow organizational procedures.
• Safety takes priority over completing a maintenance or support task.

Future Learning

The following reading, Address Workplace Hazards, explores how IT professionals identify and respond to hazards in their work environments, including electrical, thermal, chemical, trip and fall, and ergonomic risks.

Out of Scope

• Detailed ESD prevention procedures covered in the preceding video
• Advanced electrical repair or testing procedures
• Electrical certification requirements
• Detailed occupational safety regulations
• Advanced ergonomic workstation assessments
• Detailed repetitive strain injury prevention
• Emergency medical treatment procedures
• Detailed hazardous material handling and disposal
• Workplace incident investigation procedures

Writer Guidance

Focus on protecting the technician rather than protecting hardware components. The preceding video already introduces ESD, grounding, component handling, and basic maintenance precautions.

Emphasize the four areas identified in the Skills and Knowledge document: electrical safety, lifting techniques, sharp edges, and cable safety.

Use practical examples involving desktop computers, laptops, monitors, cables, and other equipment commonly handled by entry-level IT support professionals.

Include a brief scenario in which a technician recognizes an unsafe condition and determines whether to proceed, stop work, or escalate.

Keep ergonomics introductory, since the following Address Workplace Hazards reading will explore ergonomic risks, repetitive strain injuries, and other environmental hazards in greater detail.

Emphasize safe decision-making, organizational procedures, and recognizing the limits of an IT support professional’s responsibilities.

C2M1 Reading: Address Workplace Hazards

Asset Type: New reading
Target Length: 500–600 words
Lesson: C2M1 Lesson 3: Hardware Safety

Purpose

Explain how IT support professionals identify and respond to common workplace hazards, including electrical, thermal, chemical, physical, and ergonomic risks. Emphasize safe decision-making, hazard reporting, and organizational safety procedures.

Prior Knowledge

Learners have been introduced to hardware safety, ESD protection, safe equipment handling, electrical safety, lifting techniques, sharp edges, and cable safety.

Reading Objective

Identify common workplace hazards in IT environments and describe appropriate actions to reduce risks and report unsafe conditions.

Content Outline

1. Introduction to Workplace Hazards

• Define workplace hazards and explain their importance in IT environments.
• Explain why technicians should assess their surroundings before beginning work.
• Emphasize following organizational safety policies and recognizing tasks that require specialized personnel.

2. Common Workplace Hazards

Electrical Hazards

• Identify damaged components, exposed wiring, overloaded outlets, and unsafe electrical practices.
• Include examples such as damaged extension cords, bypassing electrical protections, and failing to follow approved power isolation procedures.

Thermal Hazards

• Identify hot components, including CPUs, GPUs, and printer rollers.
• Explain precautions such as allowing equipment to cool and following manufacturer guidance.

Chemical Hazards

• Introduce risks associated with batteries, printer chemicals, and cleaning supplies.
• Explain why swollen or leaking batteries require specialized handling and reporting.

Trip and Fall Hazards

• Identify loose cables, cluttered workspaces, and improperly stored equipment.
• Explain how organized workspaces and clear walkways reduce risks.

Ergonomic Hazards

• Introduce repetitive strain injuries, awkward working positions, and lifting risks.
• Describe basic prevention strategies, including workstation adjustments, position changes, and lifting assistance.

Include a concise table identifying each hazard type, a workplace example, and an appropriate response.

3. Responding to and Reporting Hazards

Introduce a simple workplace response process:

1. Recognize: Identify the unsafe condition.
2. Stop: Avoid or discontinue unsafe work.
3. Protect: Keep yourself and others safe without creating additional risks.
4. Report: Follow organizational reporting and escalation procedures.
5. Resume: Continue only when the hazard has been addressed and work is authorized.

• Explain what to include in a hazard report: location, observed condition, potential risk, and actions already taken.
• Reinforce the importance of documenting concerns and following organizational safety policies.
• Include a brief scenario involving a swollen laptop battery or damaged electrical equipment.

4. Key Takeaways

• IT workplaces contain electrical, thermal, chemical, physical, and ergonomic hazards.
• Recognizing hazards and taking appropriate precautions reduces risks.
• Technicians should stop unsafe work and report concerns through approved channels.
• Safety procedures and authorization take priority over completing a task.

Future Learning

Learners will apply workplace safety principles when working with operating systems, hardware tools, and troubleshooting activities throughout Course 2 and later IT support courses.

Out of Scope

• Detailed electrical safety procedures covered in the preceding reading
• Advanced electrical testing and repairs
• Hazardous material handling and disposal procedures
• Specialized battery repairs
• Advanced thermal management
• Detailed ergonomic assessments
• Occupational safety regulations
• Emergency medical response and incident investigations

Writer Guidance

Focus on recognizing workplace hazards and selecting appropriate responses rather than detailed repair procedures.

Avoid repeating electrical safety, lifting techniques, and cable handling from the preceding Personal Safety reading. Use practical examples from offices, repair workspaces, and equipment storage areas.

Include a simple hazard identification table and one brief workplace scenario. Emphasize stopping unsafe work, documenting observations, and reporting hazards according to organizational procedures.

Keep the content practical and appropriate for entry-level IT support professionals.

C2M1 Reading: Module 1 Review

Asset Type: New reading
Target Length: 200–300 words
Lesson: C2M1 Module 1 Review

Purpose

Reinforce the foundational concepts of device configuration, device readiness workflows, and hardware safety.

Reading Objective

Summarize common device configuration and readiness practices and identify essential hardware and workplace safety precautions.

Content Outline

1. Module Overview

• Briefly reinforce how IT professionals prepare, configure, and maintain devices for organizational use.
• Connect device readiness and safe hardware handling to reliable IT support.

2. Module Key Concepts

• Device Lifecycle Management: Devices move through acquisition, deployment, maintenance, reassignment, and retirement.
• Firmware and BIOS/UEFI: Firmware initializes hardware, while BIOS/UEFI settings influence startup, security, and hardware capabilities.
• Desktop Configuration: Imaging, cloning, and zero-touch provisioning support device deployment across operating systems.
• Mobile Configuration: Device ownership models, enrollment, and data protection influence mobile device setup and support.
• Mobile Device Management (MDM): Centralized platforms support application deployment, security policies, updates, and compliance monitoring.
• Device Readiness: Checklists verify operating system settings, user accounts, authentication, permissions, and connectivity.
• Hardware Safety: ESD protection, safe handling, cleaning, and disposal practices help protect equipment.
• Personal and Workplace Safety: Electrical, thermal, chemical, physical, and ergonomic hazards require appropriate precautions and reporting.

3. Connecting the Concepts

• Briefly connect device preparation, readiness verification, and safe handling to the process of providing a device to an employee.
• Reinforce that IT professionals follow organizational procedures throughout the process.

4. Final Takeaways

• Consistent configuration and device management support organizational needs.
• Readiness checks help verify that devices meet requirements.
• Safe handling and hazard awareness protect people and equipment.

Out of Scope

• New concepts or terminology
• Detailed configuration or troubleshooting procedures
• Extended workplace scenarios
• Repeating individual lessons in detail
• Introducing material from later modules

Writer Guidance

Keep this a concise review rather than a new instructional reading. Use brief explanations to reinforce the major concepts from all three lessons. Avoid introducing additional examples, procedures, or technical details. Focus on how device preparation, readiness verification, and safety work together in IT support.

C2M2 Reading: Operating Systems Review

Asset Type: New reading
Target Length: 400–500 words
Lesson: C2M2 Lesson 1: OS Interfaces

Purpose

Review the fundamental responsibilities of operating systems, including hardware resource management, file systems, system stability, security, and enterprise administration. Establish why understanding these functions is important for IT support professionals.

Prior Knowledge

Learners have been introduced to operating systems, hardware components, applications, files, accounts, and permissions in Course 1. They have also explored device configuration and readiness workflows in C2M1.

Reading Objective

Describe the primary functions of operating systems and explain how they support device operation, security, and administration.

Content Outline

1. Introduction to Operating Systems

• Briefly review the role of an operating system in managing hardware, applications, and user interactions.
• Explain how operating systems provide the foundation for reliable device operation.
• Connect operating system responsibilities to everyday IT support tasks.

2. Managing Hardware and System Resources

• Explain how operating systems coordinate communication between software and hardware.
• Introduce CPU scheduling and memory management as essential operating system responsibilities.
• Explain how resource management affects application performance and device responsiveness.

3. File Systems and Storage

• Explain how operating systems use file systems to organize and manage stored data.
• Review files, directories, and basic access permissions.
• Briefly connect file management to data accessibility and organization.

4. System Stability and Security

• Explain how operating systems support stable operation through process management and resource allocation.
• Introduce the role of updates, user permissions, and built-in security features.
• Connect system stability and security to reliable device operation.

5. Operating Systems in Enterprise Environments

• Explain how organizations manage operating systems across multiple devices.
• Introduce centralized administration of user accounts, settings, updates, and security policies.
• Reinforce how consistent operating system management supports organizational requirements.

6. Key Takeaways

• Operating systems manage hardware resources, applications, files, and user interactions.
• CPU and memory management help devices operate efficiently.
• File systems organize information and support controlled access.
• Operating systems support device stability and security.
• Centralized administration helps organizations manage devices consistently.

Future Learning

The following video introduces graphical user interfaces (GUIs) and command-line interfaces (CLIs). Later lessons provide opportunities to use operating system tools to access system information, monitor performance, and perform basic administrative tasks.

Out of Scope

• Detailed operating system architecture
• Advanced CPU scheduling or memory allocation
• File system types and configuration procedures
• Detailed security configuration or policy management
• Enterprise administration procedures
• Specific GUI navigation or command-line instructions
• Troubleshooting procedures and performance analysis

Writer Guidance

Build on the operating system concepts introduced in Course 1 rather than reteaching basic definitions.

Focus on what operating systems manage and why these responsibilities matter to IT support professionals. Use brief workplace examples to connect operating system functions to device performance, security, and administration.

Keep CPU and memory management, file systems, and enterprise administration conceptual. Avoid detailed technical explanations or procedures.

Do not introduce GUI and CLI comparisons, since those are covered in the following assets.

C4M1 Reading: Introduction to AI in Security

Asset Type: Existing reading, light revision
Target Length: 300–400 words
Lesson: C4M1 Lesson 1: Introduction to IT Security
Source: G-R4R86D, Introduction to AI in Cybersecurity

Purpose

Introduce how AI supports security work, including everyday IT support tasks, while recognizing that AI can also introduce risks and be used by malicious actors.

Reading Objective

Describe how AI can support security tasks and identify potential risks associated with its use.

Content Outline

1. Introduction to AI in Security

• Retain the existing introductory explanation of AI.
• Explain how AI helps professionals analyze information, summarize findings, and improve efficiency.
• Shift the audience from cybersecurity specialists to IT support professionals.

2. How AI Supports Security Work

• Provide two or three introductory examples:
  • Summarizing security alerts or technical information.
  • Helping identify potentially suspicious communications.
  • Drafting security documentation or user guidance.
• Emphasize that AI assists professionals rather than replacing their judgment.

3. The Dual Role of AI

• Retain the existing double-edged sword of AI concept.
• Explain that malicious actors can also use AI to create convincing phishing messages, automate tasks, and support attacks.
• Keep examples introductory, since specific attacks are covered later in the module.

4. Responsible AI Use

• Briefly introduce the importance of verifying AI-generated information.
• Reinforce protecting sensitive information and following organizational policies when using AI tools.
• Explain that security decisions should not rely solely on AI outputs.

Key Takeaways

• AI can help IT support professionals perform security-related tasks more efficiently.
• AI can also be misused to support cyberattacks.
• Human verification and responsible use remain essential.

Future Learning

The following video, Boost Your Security Skills with AI, builds on these concepts by exploring practical applications of AI in security work. Later lessons examine specific security threats, including AI-assisted phishing and malicious software.

Out of Scope

• Detailed explanations of AI models or machine learning.
• Specific AI security tools or platforms.
• Advanced threat detection and security operations.
• Detailed phishing and malware identification techniques.
• Hands-on AI prompting procedures.

Writer Guidance

Preserve as much of the existing reading as possible. This should be a light update rather than a complete rewrite.

Replace references to cybersecurity career preparation with language relevant to IT support professionals. Add a few practical examples and a brief reminder about responsible AI use. Remove the existing lesson-specific promises about hands-on practice and mastering AI security techniques.

Keep the reading introductory and avoid duplicating the following video or later security lessons.

C4M1 Reading: Essential Security Terms

Asset Type: Existing video converted to reading
Source: G-0LUOM3
Target Length: 650–750 words
Lesson: C4M1 Lesson 2: Malicious Software

Purpose

Introduce foundational cybersecurity terminology that IT support professionals need to recognize, understand, and communicate security concerns.

Prior Knowledge

Learners understand basic IT systems and support responsibilities. The preceding video introduced the CIA triad: confidentiality, integrity, and availability.

Reading Objective

Define foundational security terminology and distinguish between risks, threats, vulnerabilities, exploits, and attacks.

Content Outline

1. Foundational Security Terminology

• Define risk, vulnerability, threat, exploit, and attack.
• Explain the relationships between these concepts using an IT support example.
• Distinguish malicious threat actors from authorized security professionals.
• Introduce internal threats and AI threat vectors, including AI-generated phishing and impersonation.

2. Security Controls and Risk Reduction

• Define security controls, mitigation, system hardening, and security posture.
• Provide examples such as MFA, software patches, access permissions, and device locking.
• Explain how these practices reduce security risks.

3. Organizational Security Concepts

• Define security frameworks and compliance, briefly referencing the NIST Cybersecurity Framework.
• Introduce network security and cloud security.
• Define incident response and security operations centers (SOC).
• Explain how IT support professionals recognize, document, and escalate security concerns.

4. Applying Security Terminology

• Present a brief IT support scenario involving a security vulnerability.
• Identify the threat, vulnerability, potential attack, and associated risk.
• Explain how security controls could reduce the risk and when escalation is appropriate.

Key Takeaways

• Security terminology helps professionals recognize and communicate threats.
• Security controls and hardening practices reduce organizational risk.
• IT support professionals play a role in identifying and reporting security concerns.

Future Learning

The following reading, Zero-Day Threats, explores vulnerabilities, exploits, and attacks in greater detail. Later lessons address malware, network attacks, security controls, and incident response.

Out of Scope

• Detailed zero-day lifecycles and malware types.
• Advanced security frameworks and compliance requirements.
• Security operations procedures and incident investigation.
• Technical system hardening and remediation procedures.

Writer Guidance

Use the original video as a starting point, updating terminology and replacing lengthy analogies with practical IT support examples. Include a simple terminology table and one workplace scenario. Keep additional concepts introductory, since they are developed further in later modules.

Scope alignment: Covers all concepts identified for Essential Security Terms in the Skills and Knowledge document without expanding into advanced technical instruction.

C4M1 Reading: Zero-Day Threats

Asset Type: New reading
Target Length: 400–500 words
Lesson: C4M1 Lesson 2: Malicious Software

Purpose

Explain what zero-day threats are, distinguish between zero-day vulnerabilities, exploits, and attacks, and introduce how these threats are discovered and addressed.

Prior Knowledge

The preceding reading, Essential Security Terms, introduced vulnerabilities, threats, exploits, attacks, and security controls.

Reading Objective

Differentiate zero-day vulnerabilities, exploits, and attacks, and describe the lifecycle of a zero-day threat.

Content Outline

1. Understanding Zero-Day Threats

• Define a zero-day vulnerability as a software weakness for which a fix is not yet available.
• Distinguish between:
  • Zero-day vulnerability: The security weakness.
  • Zero-day exploit: The method or code used to take advantage of the weakness.
  • Zero-day attack: The actual use of the exploit against a target.
• Explain the significance of the term zero-day.

2. The Zero-Day Threat Lifecycle

• Explain the typical sequence:
  1. A software flaw exists.
  2. An attacker discovers the vulnerability.
  3. An exploit is developed.
  4. The exploit is used in an attack.
  5. The software vendor discovers the vulnerability or becomes aware of an attack exploiting it.
  6. A security patch or update is developed and distributed.
• Include a simple lifecycle diagram.
• Note that vulnerabilities may also be discovered and reported by security researchers before attackers exploit them.

3. Zero-Day Threats in IT Support

• Explain why zero-day threats are difficult to prevent using traditional patching alone.
• Introduce the importance of monitoring vendor security advisories, applying approved updates, and following organizational security procedures.
• Explain how IT support professionals may assist with documenting, reporting, and escalating suspected security concerns.

Key Takeaways

• Zero-day vulnerabilities, exploits, and attacks describe different stages or aspects of a security threat.
• Zero-day attacks can occur before a security patch becomes available.
• IT support professionals help reduce exposure by following security guidance and established procedures.

Future Learning

The following video, Malicious Software, introduces different types of malware and how malicious software can compromise systems.

Out of Scope

• Developing or executing exploits.
• Detailed vulnerability research and discovery methods.
• Advanced threat detection and incident investigation.
• Specific patch deployment procedures.

Writer Guidance

Build on the terminology introduced in Essential Security Terms without redefining every concept. Use one straightforward software vulnerability example to illustrate the lifecycle. Keep the emphasis on recognizing zero-day threats and understanding their significance rather than investigating or remediating them.

C4M1 Reading: System and Cloud Attacks

Asset Type: New reading
Target Length: 500–600 words
Lesson: C4M1 Lesson 2: Malicious Software

Purpose

Introduce system-level and cloud-based attacks that compromise devices, infrastructure, software, and identities, building on the malware concepts introduced in the preceding video.

Prior Knowledge

Learners understand common malware types, malware delivery methods, vulnerabilities, and exploits.

Reading Objective

Identify common system and cloud attacks and describe how they compromise systems, resources, and access.

Content Outline

1. System-Level Attacks

• Bots and botnets: Compromised devices controlled by attackers to perform coordinated activities.
• Backdoors: Hidden methods of maintaining unauthorized access to systems.
• Rootkits and deep system obfuscation: Malicious tools that operate with elevated privileges, conceal malicious processes, and evade common system monitoring tools.
• Logic bombs: Malicious code triggered by a specific event or condition.

2. Cloud and Supply Chain Attacks

• Cloud cryptojacking and resource hijacking: Unauthorized use of cloud computing resources, including environments such as AWS, Azure, and Google Cloud.
• Software supply chain attacks: Compromised third-party dependencies, open-source libraries, or vendor updates.

3. Cloud Identity and Access Threats

• Identity provider (IdP) attacks: Targeting services that manage authentication and access.
• MFA prompt bombing: Repeated authentication requests intended to trick users into approving access.
• OAuth permission abuse: Misuse of application permissions to access accounts or information.
• Explain how compromised administrative access can affect multiple systems or users.

4. Recognizing and Reporting Security Concerns

• Introduce warning signs such as unexpected authentication requests, unfamiliar account activity, and unusual resource consumption.
• Reinforce the importance of documenting observations and following organizational escalation procedures.

Key Takeaways

• System-level attacks can conceal malicious activity or provide persistent unauthorized access.
• Cloud and supply chain attacks can affect multiple systems and organizations.
• Cloud identity and administrative access are important security targets.

Future Learning

The next lesson introduces network attacks, including interception, spoofing, and denial-of-service attacks.

Out of Scope

• Detailed malware analysis and removal.
• Configuring cloud security services.
• Advanced identity and access management.
• Investigating or remediating security incidents.

Writer Guidance

Build on the preceding Malicious Software video without repeating basic malware definitions. Use practical IT support examples to explain how these threats affect devices, cloud services, and user accounts. Keep technical explanations introductory and focus on recognizing potential security concerns rather than performing advanced security investigations.

C4M1 Reading: Network Attacks and Transport Security

Asset Type: Existing video converted to an updated reading
Source: G-EZ9M3S, Network Attacks
Target Length: 650–750 words
Lesson: C4M1 Lesson 3: Network Attacks

Purpose

Introduce common network attacks and explain how attackers intercept, manipulate, or redirect network communications. Establish how transport security and encryption help protect information moving across networks.

Prior Knowledge

Learners understand basic networking concepts, including IP addresses, DNS, network protocols, and data transmission. Previous lessons introduced security threats, vulnerabilities, and attacks.

Reading Objective

Identify common network attacks and explain how transport security mechanisms help protect network communications.

Content Outline

1. Introduction to Network Attacks

• Explain how attackers target network communications to intercept, redirect, or manipulate data.
• Connect network attacks to confidentiality, integrity, and availability.

2. Network-Level Attacks

• IP spoofing: Falsifying source IP addresses to disguise the origin of network traffic.
• IP fragmentation attacks: Exploiting how network devices process fragmented packets.
• ICMP attacks and ping floods: Misusing network diagnostic messages to disrupt systems.
• DNS spoofing and cache poisoning: Manipulating DNS records to associate legitimate domain names with fraudulent IP addresses, redirecting traffic to attacker-controlled destinations.

3. Interception and Wireless Attacks

• Adversary-in-the-Middle (AiTM) attacks: Positioning an unauthorized entity between communicating systems to inspect, record, or modify network traffic. Introduce the alternative term meddler-in-the-middle.
• Session and cookie hijacking: Stealing authentication tokens to impersonate legitimate users.
• Rogue access points: Unauthorized wireless access points connected to a network.
• Evil twin attacks: Fraudulent Wi-Fi networks that imitate legitimate networks.
• Connect interception and manipulation to data integrity and verification.

4. Transport Security and Data Protection

• TLS and HTTPS: Explain how encryption protects data in transit, reduces exposure to packet sniffing, and helps prevent unauthorized modification of communications.
• Digital certificates: Introduce their role in verifying server identity and establishing trusted connections.
• DNSSEC: Explain how DNS responses can be authenticated to help detect tampering.
• DNS over HTTPS (DoH) and DNS over TLS (DoT): Introduce encrypted DNS communications and how they differ from DNSSEC.
• Briefly explain why browser certificate warnings should not be ignored.

5. Recognizing Network Security Concerns

• Introduce warning signs such as unexpected redirects, suspicious Wi-Fi networks, and certificate warnings.
• Explain how IT support professionals document observations and follow organizational escalation procedures.

Key Takeaways

• Network attacks can intercept, redirect, manipulate, or disrupt communications.
• Attackers may target IP traffic, DNS, wireless networks, and authenticated sessions.
• Encryption, certificates, and DNS security mechanisms help protect network communications.

Future Learning

The following video, Denial-of-Service, explores attacks designed to overwhelm systems and disrupt service availability. A subsequent reading examines distributed denial-of-service (DDoS) attacks.

Out of Scope

• Detailed packet analysis and attack execution.
• Advanced wireless security configuration.
• Certificate authority infrastructure and certificate management.
• Detailed TLS configuration and troubleshooting.
• Denial-of-service and DDoS attack mechanisms, which are covered in subsequent assets.

Writer Guidance

Use the existing video as a starting point, removing obsolete references to Java applets and updating terminology to adversary-in-the-middle or meddler-in-the-middle. Group related attack types rather than presenting lengthy technical explanations. Use practical networking and IT support examples to illustrate how attacks affect communications. Keep transport security explanations introductory, emphasizing what the protections accomplish rather than how to configure them.

C4M1 Reading: DDoS Attacks

Asset Type: Existing reading updated with new content
Target Length: 500–600 words
Lesson: C4M1 Lesson 3: Network Attacks

Purpose

Expand on distributed denial-of-service (DDoS) attacks by introducing reflection and amplification techniques, their impact on network services, and common defensive measures.

Prior Knowledge

The preceding Denial-of-Service video introduced DoS and DDoS attacks, ping floods, SYN floods, and the role of botnets.

Reading Objective

Differentiate DDoS attack techniques and describe how organizations reduce their impact on network availability.

Content Outline

1. Understanding DDoS Attacks

• Briefly review how DDoS attacks use multiple sources to overwhelm networks, servers, or services.
• Explain how distributed traffic makes these attacks difficult to manage.
• Connect DDoS attacks to the availability component of the CIA triad.

2. Reflection and Amplification Attacks

• Reflection attacks: Attackers use third-party systems to direct unwanted responses toward a target.
• Amplification attacks: Attackers generate disproportionately large responses from relatively small requests.
• Introduce DNS amplification and connectionless LDAP (CLDAP) as examples.
• Distinguish reflection from amplification and explain how the techniques can be combined.

3. Recognizing DDoS Attacks

• Introduce common indicators, including unusually high traffic, slow response times, service interruptions, and widespread connectivity complaints.
• Explain how legitimate traffic spikes and infrastructure problems can produce similar symptoms.
• Connect these observations to IT support documentation and escalation procedures.

4. DDoS Mitigation Strategies

• Introduce common defensive measures:
  • Traffic filtering and rate limiting.
  • Content delivery networks (CDNs) and distributed infrastructure.
  • DDoS protection services and traffic scrubbing.
• Explain why organizations often rely on upstream providers and specialized security teams to manage large attacks.
• Reinforce the IT support role in recognizing, documenting, and escalating suspected incidents.

Key Takeaways

• DDoS attacks use distributed traffic to disrupt service availability.
• Reflection and amplification techniques can increase the impact of attacks.
• Organizations use layered defenses and specialized services to reduce disruption.

Future Learning

The next lesson introduces other types of security attacks, including client-side vulnerabilities, application attacks, and password attacks.

Out of Scope

• Repeating detailed ping flood and SYN flood explanations.
• Historical DDoS case studies.
• Executing or simulating DDoS attacks.
• Configuring DDoS protection infrastructure.
• Advanced traffic analysis and incident response.

Writer Guidance

Build on the preceding video without repeating its explanations. Update outdated case studies and protocol references, distinguishing LDAP from CLDAP where relevant. Use a simple example or diagram to illustrate reflection and amplification. Keep mitigation strategies conceptual and focused on how organizations protect availability rather than detailed configuration procedures.

Skills and Knowledge Alignment: Covers DDoS attacks, reflection attacks, and amplification attacks identified in the Skills and Knowledge document, while incorporating the updated examples and mitigation strategies specified in the master asset list.

C4M1 Reading: Client-Side and Application Attacks

Asset Type: Existing reading updated with new content
Source: G-X56LF8, Prevent Injection Attacks
Target Length: 600–700 words
Lesson: C4M1 Lesson 4: Other Attacks

Purpose

Introduce common attacks targeting web browsers, client applications, and software vulnerabilities. Explain how attackers exploit weaknesses in applications to compromise systems, steal information, or execute unauthorized actions.

Prior Knowledge

Learners understand vulnerabilities, exploits, malware, network attacks, and basic web technologies.

Reading Objective

Identify common client-side and application attacks and describe how they compromise applications, systems, and data.

Content Outline

1. Client-Side Vulnerabilities

• Explain how attackers exploit weaknesses in browsers and applications.
• Insecure data storage: Sensitive information stored without adequate protection.
• Outdated extensions and plugins: Security risks associated with unpatched browser components.

2. Web Application Attacks

• Cross-site scripting (XSS): Malicious scripts executed in a user’s browser, including stored, reflected, and DOM-based XSS.
• Cross-site request forgery (CSRF): Tricking authenticated users’ browsers into performing unintended actions.
• SQL injection: Manipulating application database queries through malicious input.
• Command injection: Exploiting application inputs to execute unauthorized system commands.

3. Application Security Protections

• Input validation, output encoding, and sanitization: Help prevent malicious input or content from compromising applications.
• Parameterized queries: Help prevent SQL injection.
• CSRF tokens: Help prevent unauthorized requests made through authenticated user sessions.
• Web application firewalls (WAFs): Help detect and block suspicious web traffic.
• Code signing and digital signatures: Help verify software authenticity and integrity.
• Approved software repositories and sideloading restrictions: Help reduce risks from untrusted applications.

4. Recognizing Application Security Concerns

• Introduce warning signs such as unexpected browser behavior, suspicious extensions, unusual application requests, and security warnings.
• Explain how IT support professionals document concerns and follow organizational reporting and escalation procedures.
• Reinforce that IT support professionals are generally responsible for recognizing and escalating potential application security issues rather than investigating or correcting application vulnerabilities.

Key Takeaways

• Client-side and application vulnerabilities can expose systems and sensitive information.
• Attackers may exploit application inputs, browser components, or authenticated sessions.
• Application security controls help reduce risks associated with malicious code and unauthorized actions.

Future Learning

The following reading, Password Attacks, explores techniques attackers use to compromise user credentials and gain unauthorized access.

Out of Scope

• Writing or executing injection attacks.
• Detailed application development and secure coding practices.
• Configuring web application firewalls.
• Advanced vulnerability testing and penetration testing.
• Detailed implementation of security controls.
• Incident investigation and remediation.

Writer Guidance

• Use practical, entry-level examples to distinguish client-side vulnerabilities from application attacks.
• Keep explanations of XSS, CSRF, SQL injection, and command injection introductory.
• Explain what each security protection accomplishes without describing how developers implement it.
• Avoid code samples, attack demonstrations, and detailed technical configurations.
• Emphasize recognizing potential threats, understanding common protections, and following organizational escalation procedures.
• Use evergreen terminology and avoid references to specific browser or application versions.

Skills and Knowledge Alignment: Covers the identified client-side vulnerabilities, application attacks, and protective measures. The outline incorporates current security concepts while maintaining an appropriate level of complexity for entry-level IT support learners.

C4M1 Reading: Password Attacks

Asset Type: Reading
Target Length: 500–600 words
Lesson: C4M1 Lesson 4: Other Attacks

Purpose

Introduce common techniques attackers use to compromise passwords and gain unauthorized access to accounts. Explain how password security practices and authentication protections help reduce these risks.

Prior Knowledge

Learners understand authentication, user accounts, security vulnerabilities, and basic access controls.

Reading Objective

Identify common password attack techniques and describe security practices that reduce the risk of unauthorized account access.

Content Outline

1. Understanding Password Attacks

• Explain why passwords are common targets for attackers.
• Describe how compromised credentials can provide unauthorized access to accounts, applications, and organizational resources.
• Distinguish between guessing passwords and obtaining passwords through other means.

2. Common Password Attack Techniques

• Brute-force attacks: Systematically attempting password combinations.
• Dictionary attacks: Trying passwords from lists of common words and known password patterns.
• Password spraying: Trying a small number of commonly used passwords across many accounts.
• Credential stuffing: Using stolen username and password combinations from previous data breaches.
• Offline password cracking: Attempting to recover passwords from stolen password hashes.

3. Protecting Accounts Against Password Attacks

• Strong, unique passwords: Reduce the effectiveness of guessing attacks and prevent password reuse across accounts.
• Password managers: Help users create and securely store unique passwords.
• Multifactor authentication (MFA): Adds protection when passwords are compromised, although not all MFA methods are equally resistant to attacks.
• Account monitoring and rate limiting: Help organizations identify and restrict suspicious login attempts.
• Secure password storage: Briefly explain that organizations use password hashing rather than storing passwords in plain text.

4. Recognizing Password-Related Security Concerns

• Identify warning signs such as repeated failed logins, unexpected account lockouts, unfamiliar sign-in notifications, and suspicious MFA prompts.
• Explain how IT support professionals verify user identity before assisting with account recovery or password resets.
• Reinforce the importance of documenting suspicious activity and following organizational escalation procedures.

Key Takeaways

• Attackers use several techniques to guess, reuse, or recover passwords.
• Unique passwords, password managers, MFA, and organizational security controls reduce account compromise risks.
• IT support professionals help protect accounts by recognizing suspicious activity and following secure account recovery procedures.

Future Learning

The following Deceptive Attacks video introduces social engineering techniques that manipulate people into revealing information or taking unsafe actions.

Out of Scope

• Performing password cracking or attack demonstrations.
• Detailed cryptographic hashing algorithms.
• Configuring authentication servers or identity platforms.
• Advanced identity and access management.
• Detailed phishing and social engineering techniques, which are covered in subsequent assets.

Writer Guidance

• Use simple examples to distinguish brute-force attacks, password spraying, and credential stuffing.
• Keep offline password cracking and password hashing conceptual.
• Emphasize practical password security behaviors relevant to entry-level IT support.
• Avoid outdated recommendations such as requiring frequent password changes without evidence of compromise.
• Do not include password cracking tools, commands, or demonstrations.
• Keep the focus on recognizing threats, protecting accounts, and following organizational procedures.

Alignment note

The master asset list identifies two requirements that should be made more explicit before finalizing this outline:

1. Rainbow table attacks: Add these to Section 2 as a historical password-cracking technique that uses precomputed password hashes. Keep the explanation brief.
2. Salting: Add this to Section 3 alongside password hashing. Explain that a unique random value added before hashing helps protect stored passwords against precomputed attacks.

Both are appropriate for entry-level learners when explained conceptually.

With those additions, the reading will cover the master asset list’s required brute-force, dictionary, and rainbow table techniques, along with rate limiting and salting. It will also introduce current threats such as password spraying and credential stuffing without making the reading overly technical.

C4M1 Reading: Phishing

Asset Type: Existing reading rewritten with updated content
Target Length: 750–850 words
Lesson: C4M1 Lesson 4: Other Attacks

Purpose

Build on the Deceptive Attacks video by examining modern phishing techniques, how attackers make deceptive communications appear legitimate, and the steps IT support professionals take when phishing attempts or account compromises are reported.

Prior Knowledge

Learners understand social engineering, pretexting, spoofing, common phishing methods, MFA push bombing, and the importance of verifying suspicious requests.

Reading Objective

Identify common phishing techniques and describe appropriate IT support procedures for recognizing, documenting, containing, and escalating suspected phishing incidents.

Content Outline

1. Recognizing Modern Phishing Attacks

• Briefly reinforce phishing as a form of social engineering that can occur through email, text messages, phone calls, QR codes, social media, and workplace collaboration platforms.
• Explain how attackers make messages appear trustworthy:
  • Using publicly available information from social media and other sources to personalize attacks.
  • Spoofing sender information or using compromised legitimate accounts.
  • Using generative AI to create convincing messages without obvious spelling or grammar errors.
• Briefly introduce SPF, DKIM, and DMARC as email authentication protections that help organizations detect certain forms of sender spoofing, without discussing their configuration.
• Identify common warning signs, including unexpected credential requests, urgent payment demands, suspicious links, unfamiliar account activity, and unexpected MFA prompts.

2. Common Phishing Techniques

Build on the preceding video without repeating introductory definitions.

• Spear phishing: Targeted messages using information about a specific person, team, or organization.
• Whaling: Phishing targeting executives or other high-profile individuals.
• Business email compromise (BEC): Using impersonation or compromised business accounts to request fraudulent payments, vendor invoice changes, or payroll updates.
• QR code phishing (quishing): Using QR codes to direct users to fraudulent websites.
• MFA fatigue / push bombing: Repeated authentication requests intended to pressure users into approving unauthorized access.
• Adversary-in-the-middle (AiTM) phishing: Using deceptive sign-in experiences to capture credentials or authenticated session information, potentially allowing attackers to bypass some MFA protections.
• Introduce workplace examples such as fake cloud document invitations, HR policy updates, invoice approvals, and collaboration platform messages.

3. IT Support Phishing Incident Response

Introduce a structured workflow for responding to suspected phishing incidents.

Step 1: Intake and Verification

• Determine what the user received, whether they interacted with it, and whether credentials or sensitive information were provided.
• Document relevant details, such as the message, sender, time received, and reported actions.
• Explain that authorized personnel may collect email headers, message IDs, and destination URLs as part of the investigation.

Step 2: Containment

• Explain how organizations may quarantine suspicious messages to prevent additional users from interacting with them.
• Introduce account restrictions or device isolation as possible containment measures when warranted.
• Emphasize that these actions must follow organizational procedures and authorization.

Step 3: Identity Protection

• Explain why compromised accounts may require password resets and revocation of active single sign-on (SSO) sessions.
• Introduce reviewing unauthorized MFA method changes as an important account protection measure.
• Reinforce identity verification before assisting with account recovery.

Step 4: Investigation and Escalation

• Explain how security teams may review sign-in logs for unfamiliar IP addresses, locations, or other suspicious activity.
• Escalate potential account compromises or breaches to the security operations center (SOC) or designated security team.
• Document actions taken and communicate approved next steps to the affected user.

4. Safe IT Support Practices and Prevention

• Verify user identities and suspicious requests through approved organizational channels.
• Never request or disclose passwords, MFA codes, or other sensitive authentication information.
• Encourage prompt reporting of suspicious messages, even when users have already clicked a link or provided information.
• Introduce simulated phishing exercises and security awareness training as ways organizations help employees recognize threats.
• Explain that AI tools may assist with identifying suspicious indicators, but outputs must be verified and sensitive information should not be entered into unapproved tools.

Key Takeaways

• Modern phishing attacks use personalized information, trusted communication channels, and increasingly convincing impersonation techniques.
• Compromised legitimate accounts and authenticated sessions can make phishing attacks harder to recognize.
• IT support professionals contribute to incident response by gathering information, documenting concerns, performing authorized support actions, and escalating security incidents.
• Prompt reporting and established organizational procedures help limit the impact of phishing attacks.

Future Learning

The next activity, Use Generative AI to List Common Signs of Phishing and Malware, provides an opportunity to identify suspicious indicators and evaluate AI-generated security guidance.

Out of Scope

• Repeating detailed social engineering explanations from the Deceptive Attacks video.
• Advanced email header analysis and forensic investigation.
• Configuring SPF, DKIM, DMARC, or email security platforms.
• Technical operation of AiTM phishing frameworks.
• Configuring tenant-wide message quarantine or identity security controls.
• Independent incident investigation or remediation without authorization.
• Detailed malware removal procedures.

Writer Guidance

• Build directly on the preceding Deceptive Attacks video. Avoid repeating definitions of phishing, smishing, vishing, quishing, and MFA push bombing.
• Prioritize modern phishing examples and the IT support incident response workflow.
• Use a realistic scenario involving an employee who interacted with a suspicious message or entered credentials into a fraudulent sign-in page.
• Present the response workflow as an introductory model. Specific procedures and responsibilities vary by organization.
• Clearly distinguish actions entry-level IT support professionals may perform from those requiring security team authorization.
• Explain technical concepts such as session token theft, email authentication, and sign-in log analysis at a recognition level.
• Keep examples evergreen and avoid relying on specific phishing campaigns, products, or attack tools.
• Reinforce that legitimate-looking messages, familiar sender addresses, and professional writing do not guarantee authenticity.

Skills and Knowledge Alignment: Covers phishing, email spoofing, compromised legitimate accounts, social media reconnaissance, spear phishing, whaling, BEC, AI-generated phishing, quishing, MFA push bombing, AiTM phishing, and collaboration platform attacks. It also incorporates the specified IT support incident response workflow, including intake, containment, identity protection, investigation, and SOC escalation.

Scope recommendation: Keep the reading focused on two outcomes: recognizing modern phishing techniques and understanding the IT support response process. The technical controls should be introduced conceptually rather than taught as configuration or investigation procedures.

C4M1 Reading: Physical Security

Asset Type: Existing reading updated with new content
Source: G-J8PMJ7, Physical Security
Target Length: 550–650 words
Lesson: C4M1 Lesson 4: Other Attacks

Purpose

Introduce physical security threats and explain how attackers use in-person social engineering, unauthorized access, and physical devices to compromise organizational systems and information. Emphasize the role of IT support professionals in recognizing and reporting physical security concerns.

Prior Knowledge

Learners understand social engineering, impersonation, deceptive attacks, and basic organizational security practices.

Reading Objective

Identify common physical security threats and describe practices that help protect organizational facilities, devices, and information.

Content Outline

1. Understanding Physical Security

• Define physical security and explain its role in protecting technology systems, facilities, and sensitive information.
• Connect physical security to the confidentiality, integrity, and availability (CIA) triad.
• Explain how attackers may bypass technical security protections by gaining physical access to devices, workspaces, or network connections.

2. Physical Social Engineering Attacks

• Tailgating (piggybacking): Following an authorized employee into a restricted area without using approved access credentials.
• Impersonation: Posing as a delivery driver, contractor, utility worker, or IT technician to gain unauthorized access.
• Shoulder surfing: Observing someone entering passwords or viewing sensitive information.
• Dumpster diving: Searching improperly discarded materials for sensitive organizational information.
• USB baiting: Leaving malicious removable devices where employees may find and connect them.
• Badge cloning: Copying information from vulnerable access badges to attempt unauthorized entry.

3. Physical Security Controls and Safe Practices

• Badge requirements and visitor management: Using approved credentials, visitor verification, and escorts to control access.
• Clean desk policies: Securing sensitive documents, removable media, and unattended devices.
• Secure document disposal: Using approved shredding bins or disposal procedures.
• Device security: Locking workstations and protecting laptops, mobile devices, and removable storage.
• Environmental controls: Briefly introduce physical protections such as secured equipment rooms, surveillance, and restricted access to network infrastructure.

4. Recognizing and Reporting Physical Security Concerns

• Identify warning signs such as unfamiliar individuals in restricted areas, unattended USB drives, missing equipment, or suspicious requests for access.
• Briefly explain how unauthorized physical access can also enable rogue wireless access points, including evil twin networks.
• Describe appropriate IT support responses:
  • Follow established visitor and access procedures.
  • Avoid connecting unknown devices to organizational systems.
  • Document and report suspicious activity through approved channels.
  • Escalate potential physical security incidents to security personnel or designated teams.

Key Takeaways

• Physical security is an essential part of protecting technology systems and organizational information.
• Attackers may exploit human behavior, physical access, or unattended devices to bypass technical protections.
• Access controls, secure workspaces, and proper reporting procedures help reduce physical security risks.

Future Learning

The Other Attacks practice quiz provides an opportunity to review client-side attacks, password attacks, deceptive attacks, phishing, and physical security threats.

Out of Scope

• Detailed physical penetration testing techniques.
• Instructions for cloning access badges.
• Configuring physical access control systems.
• Advanced surveillance or environmental monitoring systems.
• Detailed wireless attack mechanisms.
• Physical security investigations and incident remediation.

Writer Guidance

• Build on the Deceptive Attacks video, which already introduces tailgating and USB baiting. Avoid repeating those examples in detail.
• Use practical workplace examples involving offices, equipment rooms, and shared workspaces.
• Explain badge cloning conceptually without describing how it is performed.
• Keep rogue Wi-Fi coverage brief because evil twin attacks were introduced in the Network Attacks lesson.
• Emphasize physical security practices that entry-level IT support professionals are likely to encounter.
• Avoid detailed security system configurations or advanced investigative procedures.
• Keep the content evergreen and focused on recognizing threats and following organizational procedures.

C4M1 Reading: Module 1 Review

Asset Type: Standard module review reading
Target Length: 250–350 words
Lesson: C4M1 Lesson 5: Review

Purpose

Summarize the key concepts covered in Module 1 and prepare learners for the Module 1 Challenge.

Reading Objective

Summarize common security threats and safe IT support practices.

Content Outline

1. Security Threats and Attacks

• Review foundational security terminology and the CIA triad.
• Summarize common malware, system, cloud, and network attacks.
• Reinforce DoS and DDoS attacks.

2. Deceptive and Application Attacks

• Review client-side, application, and password attacks.
• Summarize social engineering and modern phishing techniques.
• Reinforce physical security threats and protections.

3. Safe IT Support Practices

• Recognize and report suspicious activity.
• Follow identity verification and security procedures.
• Document and escalate potential security incidents.

Key Takeaways

• Security threats can affect systems, networks, applications, accounts, and physical environments.
• IT support professionals help protect organizations by recognizing threats and following established procedures.

Future Learning

Module 1 Challenge.

Writer Guidance

Follow the standard module review format used throughout the certificate. Provide brief summaries of previously introduced concepts without adding new information or detailed explanations.