ISACA Computing Fundamentals (ITCA)

New hires who can't explain where data lives, why a single switch is a single point of failure, or how privilege escalation works create risk on day one. IT Directors and Training Managers use this course to give junior staff a shared baseline across hardware, software, networking, virtualization, and security before they touch production systems.

Role fit: Help desk technicians, junior administrators, and employees moving into entry-level IT roles with about a year of IT exposure. Experienced practitioners can use it to validate fundamentals for the ISACA ITCA credential.

Time investment: About 14 hours across 15 skills. Most learners can finish in two to three weeks at a few hours per week. Skills end with validations, and some run on the learner's own machine using the command prompt or terminal.

Risk and compliance framing: The security half covers the threat landscape, common attack patterns, identity and access management, multi-factor authentication, physical safeguards, whole-disk encryption with BitLocker, endpoint security concepts, and log auditing. This gives teams a common vocabulary for controls work.

Change management: The material is introductory and vendor-neutral where it matters, such as the OSI model. Expect little disruption to current workflows.

Use Playlists to pair this course with related ISACA ITCA courses, and Team Reporting to track completion across your cohort.

IT teams use this training to build a shared, vendor-neutral foundation, so newer staff can reason through everyday hardware, network, and security issues instead of escalating every issue. Many lessons are grounded in workplace scenarios. Learners walk through the boot process, including POST beep codes and peripheral detection. They compare why a single cable break can disrupt an entire bus topology with how switches create point-to-point connections in star-style networks. They also review a newly hired admin's assessment of a medium-sized company's risks, such as a shared folder named "Secrets."

• Faster first-line troubleshooting: Practitioners learn how BIOS/UEFI hands off to the operating system. They also learn to check machine and IP address details from a command prompt or terminal on Windows, macOS, or Linux, which helps narrow down issues before they reach senior staff.
• Better uptime decisions: Teams learn how redundancy, active-passive clustering, failover NICs, and scaling up or out protect services during demand spikes or hardware and software failures. This gives Team Leads a shared language for justifying resilience spending.
• Practical security habits: Learners see demos of turning on whole-disk encryption and reading logs for unexpected shutdowns. They also study privilege escalation, buffer overflows, two-factor authentication, and physical controls such as mantraps.
• Safer testing with virtualization: Practitioners see how type 1 and type 2 hypervisors differ and watch a virtual machine being built. They learn why organizations pilot applications on test VMs with a sample of departments before rolling them out broadly.

Knowledge

• How computers represent numbers in binary, and how to convert between binary and decimal values
• How the processor, cache, memory, and primary through tertiary storage work together, and how quickly each returns data
• How BIOS and UEFI run startup checks, report errors through codes or beep patterns, detect peripherals, and hand off to an operating system
• Foundational networking concepts, including common network models, topologies, and points of failure
• Type 1 vs. Type 2 hypervisors, and why teams virtualize desktops for testing and servers for scaling up or out
• Core security concepts: the threat landscape, identity and access management, and physical access controls such as multi-step entry checks for secured spaces

Ability

• Use a command prompt, PowerShell, or terminal on Windows, macOS, or Linux to look up a machine's own addressing details
• Create and format volumes in Windows, including FAT and FAT32 file systems, after shrinking existing space
• Build a virtual machine and configure its networking and virtual hard disk settings
• Navigate Linux distributions such as Fedora and Ubuntu, and recognize where the terminal is a better choice than the GUI
• Turn on BitLocker whole disk encryption, choose an unlock method, and back up the recovery key
• Review Windows Security and Microsoft Defender settings, and recognize which events to log and audit, such as unexpected server shutdowns