VCA-HW-101: Electronics and Microcontrollers

Classroom

Full course content (weekly modules, labs, capstone packet, instructor guide) lives in the Virtus Cyber Academy classroom, which is in active build. The public preview is on the way.

Open in classroom

Course Overview

VCA-HW-101 is the course where abstractions become physical. A student who completes FND-101 and FND-102 can reason about a byte in memory; after HW-101 they can reason about the voltage on a trace, the timing of a clock signal, and the difference between a datasheet pin description and the actual behavior they can measure on the bench. The course assumes no prior electronics experience but does assume FND-102 fluency with Python and the Linux shell, Arduino sketches are written and uploaded from the command line alongside the Arduino IDE, and the lab-notebook discipline that begins here continues into every subsequent Virtus Academy course.

HW-101 is also the gate to the hardware half of the curriculum. The originating tools the student meets here (breadboard, multimeter, soldering iron, logic probe, oscilloscope) are the first entries in the cross-course Tool Journal that CSA-101 Chapter 1 picks up and that every subsequent course extends. The schematic-reading and PCB-trace-following skill the student practises on the Arduino kit is the same skill RE-101 demands when students inspect the Motorola SB6141 cable modem's real PCB, identify chip packages by their silkscreen, and follow probe points to JTAG headers. HW-101 plants the physical-intuition seeds that RE-101 harvests.

What Belt-3 Hardware Track Graduates Recognize

HW-101 reads paired anchors at intermediate depth: bunnie Huang's The Hardware Hacker (No Starch 2017) plus Hacking the Xbox (No Starch 2003; free PDF via the author) supply the genre-foundational narrative (the Shenzhen supply chain as textbook; hardware reverse-engineering as a literature with legal-precedent grounding), and van Woudenberg + O'Flynn's Hardware Hacking Handbook (No Starch 2021) supplies the modern applied-attacks reference (fault injection, side channels, glitching, JTAG/SWD/chip-off workflows). Joe Grand's DEF CON Hardware Hacking Village training corpus (free on Internet Archive) plus Adafruit Learn and SparkFun Tutorials anchor the build-it-yourself side. Graduates leave able to discuss the production-hardware debug-interface inheritance (JTAG/SWD/UART/ICSP at standard electrical levels), the fault-injection and side-channel attack families, the Tang Primer 25K toolchain, and the bench-tool families (oscilloscope, logic analyser, JTAGulator, Bus Pirate, ST-Link, J-Link).

The teaching method uses paired textbook readings on canonical practitioner texts plus the most physical-hardware-heavy lab progression in the academy (oscilloscopes, soldering, chip-off rework, JTAG probing), with the per-chapter reading guide published as a separate handout (handouts/cross-chapter-hw-101-anchor-reading-guide.md) so the catalog page stays thin. Twelve hands-on labs anchor each module to a measurable artifact, and the capstone is a student-fabricated Arduino-based data logger in a hand-built enclosure with a written engineering report. Graduates carry the supply-chain framing, the debug-interface discovery discipline, and the Tang Primer 25K hardware fluency into RE-101's embedded-systems teardowns, into ADV-101's CVE-to-tool work where the target is hardware, and into the broader practitioner community Joe Grand and bunnie Huang shaped.

Learning Objectives

Listed in Bloom's-taxonomy order. Each is measurable against a specific lab or written deliverable.

1. Remember. State Ohm's law (V = IR), Kirchhoff's current and voltage laws, the four-band resistor color code, and the standard breadboard rail conventions. (Assessed: closed-book bench quiz; Lab 1 worksheet.)
2. Understand. Explain why a 5 V source through a 220 Ω resistor delivers ~22.7 mA, and why an LED in series with that resistor will not exceed its forward-current rating. Distinguish series from parallel by the voltage and current relationships in each. (Assessed: Lab 2 power-budget worksheet.)
3. Apply. Build a working DC circuit on a breadboard from a schematic, using a multimeter to verify expected voltages and currents at named test points, and a logic probe or oscilloscope to verify expected digital signals. (Assessed: Lab 3 multi-LED bus driven by Arduino digital output.)
4. Apply. Write, compile, and upload Arduino sketches using both the Arduino IDE and the command-line arduino-cli workflow. Use the serial monitor to debug runtime behavior; use the multimeter to debug hardware behavior; distinguish the two failure modes. (Assessed: Lab 4 sensor-read-and-print sketch with diagnostic write-up.)
5. Apply. Solder through-hole connections to a standard pad-per-hole prototyping board with mechanically sound joints (visually shiny, fully wetted, no cold joints) and electrically continuous (verified by multimeter resistance check < 1 Ω across each joint). (Assessed: Lab 7 capstone-precursor; ungraded but pass-required for capstone enrollment.)
6. Analyze. Given an unknown circuit on a breadboard, work backward from observed behavior (LED won't light; servo twitches; sensor reads garbage) to root cause, by systematic voltage-and-continuity tracing. The diagnostic discipline is the same the student will use against real PCBs in RE-101. (Assessed: Lab 5 instructor-seeded fault-finding exercise.)
7. Analyze. Read a datasheet for a sensor (DHT22, BMP280, MPU6050) and translate the pin/protocol description into working Arduino code. Distinguish what the datasheet promises from what the chip actually does on the bench when measured. (Assessed: Lab 6 datasheet-to-working-driver exercise.)
8. Create. Design, build, solder, enclose, and deliver a self-contained Arduino data logger that measures a student-chosen physical phenomenon over time, with a written design report documenting calibration procedure, observed measurement variance, and one bug encountered and resolved during the build. (Assessed: Lab 8, the capstone.)

Week-by-Week Topic Flow

Fourteen weeks. Lab time roughly doubles lecture time per the bench-heavy nature of the course.

1. Week 1. What electricity is. Voltage as a difference, current as a flow, resistance as opposition. The flashlight-and-battery demonstration; the multimeter as the first instrument. Lab 1. Safe wire-up, first multimeter measurements.
2. Week 2. Ohm's law, series and parallel. Resistor color code drill. Power dissipation and the smell of an over-current resistor. Lab 2, LED-and-resistor power budget; deliberate over-current as instructor demo.
3. Week 3. Breadboarding conventions. Rail layout, color discipline, jumper management. The lab-notebook standard. Lab 3. Multi-LED display driven by manual switches.
4. Week 4. Introduction to the Arduino UNO R4 (or successor) board. Anatomy: microcontroller, USB interface, voltage regulator, pin headers. The Arduino IDE workflow. First sketch: Blink.
5. Week 5. Digital I/O. pinMode, digitalRead, digitalWrite. Push-buttons and pull-up resistors. Lab 4. Button-controlled LED bus.
6. Week 6. Analog I/O. ADC, PWM. Reading a potentiometer; fading an LED. The serial monitor as debugging output.
7. Week 7. Sensors. Temperature (DHT22 or DS18B20), light (LDR, photodiode), accelerometer (MPU6050), button arrays. Datasheet reading. Lab 5. Instructor-seeded fault-finding.
8. Week 8. Actuators. LEDs (single, RGB, addressable WS2812 strips), buzzers, servos, DC motors. The H-bridge. Power supply considerations. Lab 6. Sensor-driven servo, datasheet-to-working-driver.
9. Week 9. Soldering, theory and practice. Iron temperature, flux, solder type, joint inspection. Through-hole on pad-per-hole prototyping board. The cold-joint failure mode. Safety: ventilation, eye protection. Lab 7. Solder a 10-pin breakout cleanly; capstone-prerequisite.
10. Week 10. Serial communication. UART between Arduino and host PC. Baud rates, framing, the meaning of bits-on-wire. Logic probe and the introductory oscilloscope; what a clock signal looks like. Forward-pointer to NET-101 (the same UART signals carry every embedded-device debug interface) and RE-101 (the SB6141's console UART is reachable via probe points the student will identify).
11. Week 11. Capstone scoping. Each student selects a physical phenomenon, drafts a block diagram, builds a parts list, and gets instructor sign-off before purchasing or fabricating.
12. Week 12. Capstone build. Circuit and firmware. Breadboard prototype first; sketch development; sensor calibration against a reference instrument.
13. Week 13. Capstone build. Soldering and enclosure. Migrate the breadboard prototype to a soldered prototyping board; design and fabricate an enclosure (laser-cut, 3D-printed, or hand-built; choice depends on lab equipment access).
14. Week 14. Capstone delivery. Demo + lab-notebook report submission. Lab 8 due.

Lab Manifest

Eight numbered labs across the course. Lab 1-6 are graded on correctness and lab-notebook quality; Lab 7 is pass/fail (capstone prerequisite); Lab 8 is the capstone, two-tier-graded against the rubric below.

• Lab 1. Safe wire-up, multimeter familiarisation. Measure the voltage of a 9 V battery; measure resistance across known-value resistors; confirm color-code reading.
• Lab 2. Power budget and Ohm's law. Build an LED-and-resistor circuit; predict and measure current at three resistor values; observe deliberately-undersized resistor failure mode.
• Lab 3. Multi-LED display driven by manual breadboard switches. First multi-component circuit; voltage-divider mathematics applied.
• Lab 4. Arduino digital I/O. Button-controlled LED bus. First firmware-on-hardware integration; the diagnostic distinction between firmware bug and wiring bug enters here.
• Lab 5. Instructor-seeded fault-finding. Given a circuit on a breadboard that does not work, the student systematically traces voltage and continuity to find the fault. The same technique used against real PCBs in RE-101.
• Lab 6. Sensor-driven actuator. Analog read, PWM write. Datasheet-to-working-driver translation; calibration mathematics.
• Lab 7. Solder a 10-pin breakout cleanly. Capstone-prerequisite. Pass requires all 10 joints visibly shiny and electrically continuous (<1 Ω across each joint, multimeter-verified).
• Lab 8, Capstone. Self-contained Arduino data logger with student-fabricated enclosure. See Capstone section below for full rubric.

Equipment per student

Manifest pending finalization of the Arduino kit decision (per OPEN-QUESTIONS §17). The list below is the functional requirement; specific kit BOM depends on whether the chosen kit (e.g., the Arduino R4 Starter Kit Classroom Pack) supplies the items or whether they need supplementing.

• Breadboard (full-size, 830 tie-points)
• Jumper-wire kit (M-M, M-F, F-F, ~120 wires)
• Resistor assortment (1/4 W, ~100 pieces across common values 220 Ω through 10 kΩ)
• LED assortment (red, green, yellow, blue; ~20 pieces)
• Push-buttons, slide switches, potentiometer
• Multimeter (digital, voltage / current / resistance / continuity beep)
• Logic probe; access to a shared introductory oscilloscope (~50 MHz benchtop or USB-attached)
• Arduino UNO R4 (or successor) board with USB-C cable
• Sensor assortment (DHT22 temperature/humidity; LDR or BH1750 light; MPU6050 accelerometer; HC-SR04 ultrasonic)
• Actuator assortment (RGB LED, servo, DC motor, piezo buzzer)
• Soldering iron (temperature-controlled, 25-40 W) with stand and tip-cleaning sponge
• Solder (60/40 lead-tin or lead-free; both acceptable, lab discloses health considerations)
• Solder wick / desoldering pump
• Pad-per-hole prototyping board (~5 pieces)
• Eye protection; ventilation per local lab safety code
• Lab notebook (paper, bound, no detachable pages, the discipline matters)

Hardware-Software Boundary, the bridge to RE-101

HW-101's deliberate forward-pointer is the boundary between firmware and silicon. By Week 10 (UART and the introductory oscilloscope), the student has watched bytes-on-wire move physically through a probe tip into a scope display, the same probe technique RE-101 will use against the SB6141 cable modem's console UART pads. The skills bracket cleanly:

• Schematic-to-PCB-trace mapping. The student learns to follow a schematic line to a physical wire on a breadboard and, in Lab 7's soldered breakout, to a physical trace on a PCB. RE-101's SB6141 teardown applies the same mapping in the opposite direction. Observe a trace, infer the schematic.
• Chip-package identification. The Arduino UNO R4's ATmega-class microcontroller, in a TQFP package, is the structural cousin of the SB6141's ARM1176JZ-S in BGA. HW-101 students learn to read the silkscreen, identify the package family, and look up the datasheet, the same workflow that RE-101 uses to identify the Puma 5 SoC and the MaxLinear MxL261 RF front-end on the SB6141's board.
• Probe-point reading. The Arduino board's ICSP header (a 6-pin in-circuit programming connector) is structurally identical to the JTAG headers RE-101 students locate on the SB6141. The student learns, in HW-101, that production hardware exposes debug interfaces deliberately, and that those interfaces are how reverse engineers get in.
• Datasheet-as-truth. The discipline of reading a datasheet, observing the chip's real behavior on the bench, and resolving the gap between specification and observation is the central skill of every reverse-engineering investigation. HW-101 builds the discipline at the sensor scale; RE-101 applies it at the SoC scale.

The course's closing message: every PCB the student will examine in RE-101, ADV-101, and the Virtus Cybersecurity research workflows is the same kind of artifact as the breadboard-and-soldered-prototype they personally built in HW-101. The scale changes; the apparatus does not.

Tool Journal: HW-101 Originating Entries

Per the academy's first-introduce-track-ownership rule, HW-101 is the canonical originating course for the bench-electronics + hardware-hacking tool corpus. Subsequent courses (CSA-101, RE-101, RE-201, ADV-101, RF-201/301) reference rather than re-introduce these entries.

HW-101 originates the following diary entries:

• Breadboard. First met Week 3. The standard prototyping fixture for any small DC or low-frequency circuit.
• Multimeter. First met Week 1. Voltage, current, resistance, continuity. Every subsequent course assumes fluency with this instrument.
• Logic probe. First met Week 10. Distinguishes high from low at digital speeds without the cost of a scope.
• Introductory oscilloscope. First met Week 10. The first instrument that shows the student a signal in time. RE-101 and RE-201 deepen this; a bench scope is on the lifetime tool list of every embedded-security practitioner.
• Saleae logic analyzer, the canonical USB logic analyzer used across embedded-security practice; Bus Pirate alternative for budget-constrained students.
• Soldering iron + flux + chip-off rework. Through-hole + surface-mount progression. First met Week 9. Anchored on bunnie's Shenzhen-factory chapters + van Woudenberg + O'Flynn's chip-off coverage.
• JTAGulator, Joe Grand's automated JTAG/UART pinout-discovery tool; canonical first-introduce here per cross-track-toolchain-roster (RE-track references). Anchored on Grand's DEF CON 21 introduction.
• Bus Pirate. Multi-protocol bench tool (I2C / SPI / UART / 1-Wire / JTAG); cousin of JTAGulator; canonical first-introduce here.
• ST-Link / J-Link / OpenOCD. Production debug probes for ARM Cortex-M targets; canonical first-introduce here; cross-cuts to RE-101 SB6141 teardown.
• ESP32-S IoT learning kit. Cross-cut to RF-track + NET-track + HW-track; promiscuous-mode WiFi + BLE radio for hands-on integration labs.
• DualShock 2 controllers (academy kit). Canonical input-device kit for HW-track + CON-track integration labs.
• Arduino IDE / arduino-cli. First met Week 4; the first time the student watches firmware compile and flash to physical hardware.
• Serial monitor. First met Week 6; the simplest debugging fixture in firmware development; the same UART that NET-101 packets-on-wire and RE-101 console-port-discovery work depend on.
• Falstad circuit simulator (browser-native). Runs in the academy workbench; lets students sketch and verify a circuit before they wire it up on the bench.
• In-browser Verilog simulator. An entry-level FPGA simulation companion; the full Verilog toolchain is introduced in CSA-101.
• Datasheet Reading 101 (interactive walk-through). Academy-built; teaches datasheet-reading discipline against curated annotated examples.
• Decap-photo-archive viewer. Academy-built; visual chip-identification pedagogy against the Schlaepfer+Oskay Open Circuits cross-section corpus.
• JTAG-replay visualizer. Academy-built; teaches JTAG protocol decoding without requiring physical JTAGulator hardware (also feeds into the NET-track Wireshark-decode discipline).

Roughly 18 tool entries originate in HW-101 (up from 7 pre-anchor-pair). CSA-101 adds ~23 more (per Chapter 12's closing retrospective). RE-101 adds ~10 more (Ghidra / IDA / radare2 / GDB / pwntools canonical introductions). The diary is the personal reference document the student opens in the middle of a real engagement, years after the grade is posted.

Recommended Readings & Practitioner Companions

Primary anchor TRIPLE pairing (down-to-earth narrative)

• Andrew "bunnie" Huang, The Hardware Hacker: Adventures in Making and Breaking Hardware. No Starch, 2017 (ISBN 978-1-59327-758-1). The Shenzhen-factory and supply-chain narrative anchor; canonical hardware-hacking memoir-and-reference. Library-acquire or paperback ~$30.
• Andrew "bunnie" Huang, Hacking the Xbox: An Introduction to Reverse Engineering. No Starch, 2003 (FREE PDF via the author). The foundational-genre text that established hardware-hacking as a literature; includes a famous legal-precedent foreword (Lessig). Free download.
• Jasper van Woudenberg & Colin O'Flynn, The Hardware Hacking Handbook: Breaking Embedded Security with Hardware Attacks. No Starch, 2021 (ISBN 978-1-59327-748-2). The modern applied-attacks handbook (fault injection, side channels, glitching, JTAG/SWD, chip-off). Library-acquire or paperback ~$50.

Primary anchor pair (build-it-yourself / practitioner training)

• Joe Grand DEF CON Hardware Hacking Village training corpus, FREE on Internet Archive + YouTube. Talks from DEF CON 14 / DEF CON 21 (the JTAGulator introduction) and ongoing HHV training; Grand is the canonical hardware-hacking instructor in the security community (Kingpin / L0pht alumnus; JTAGulator inventor).
• Adafruit Learn, FREE at learn.adafruit.com. Thousands of hands-on tutorials covering electronics fundamentals, microcontrollers, sensors, and maker-community patterns.
• SparkFun Tutorials, FREE at learn.sparkfun.com/tutorials. Companion entry-tier corpus.

Secondary anchors (supplementary)

• Eric Schlaepfer & Windell H. Oskay, Open Circuits: The Inner Beauty of Electronic Components. No Starch, 2022. Cross-section photography of common components; bunnie-endorsed; pairs with the academy decap-photo-archive viewer.
• Craig Smith, The Car Hacker's Handbook. No Starch, 2016 (FREE on Internet Archive under CC-BY-NC-SA). Canonical automotive-hardware-hacking reference.
• Travis Goodspeed's GoodFET research / PoC·GTFO writing, for students wanting deeper bench-research practice exposure.
• Hackaday + Hackster + Element14 + Make: + EEVblog + Hardwear.io, the broader maker-and-hardware-security community corpus; ongoing news + tutorials + conference talks.

Capstone: Arduino Data Logger in Student-Fabricated Enclosure

The chapter capstone. The student selects a physical phenomenon to measure (temperature over time, soil moisture in a planter, room light levels, door open/close events, power consumption of a small appliance, whatever the student finds genuinely interesting), designs the circuit, writes the firmware, calibrates against a reference instrument where possible, solders the connections to a prototyping board, fabricates an enclosure, delivers a working device, and writes a lab-notebook report.

Required artifacts

• The working device, capable of running for ≥1 hour standalone on its power source.
• The Arduino sketch source (committed to the student's course Git repository).
• The schematic (hand-drawn or KiCad; either is acceptable at this level).
• A 30-second video demonstrating the device in operation.
• A 4-6 page lab-notebook report covering: design intent and the phenomenon being measured; circuit topology and component selection rationale; firmware structure; calibration procedure (against what reference, observing what variance); one bug encountered during the build and how it was diagnosed; what the student would change in a v2.

Two-tier grading rubric

First, your project must work. The device works. It powers on, measures something, records or displays the measurement, runs for at least the demonstration interval. If the device does not work, the capstone does not pass. No rubric scoring is performed on a non-functional artifact.

Then we score the report on three dimensions. Once the artifact passes Tier 1, the lab-notebook report is scored on three dimensions:

• Engineering discipline (40%). Was the circuit designed before it was built? Was a power budget computed? Were sensor datasheets actually consulted? Is the calibration procedure sound?
• Debugging discipline (30%). Is the "one bug encountered" section honest about the failure mode, the diagnostic process, and the root cause? A perfect-build report scores zero on this dimension. Either the student hit no bugs (implausible) or omitted them (a worse fault).
• Build quality (30%). Are the soldered joints sound? Is the enclosure usable? Is the device safe to plug in? Could a stranger in the cohort use the device without supervision?

There is no curve. There is no participation credit. The device works, or it does not. The report is honest, or it is not. This is the student's first long-form independent hardware deliverable, the structural precursor to the CSA-101 Lab 12.5 Virtus Console capstone, the RE-101 SB6141 teardown report, and every subsequent portfolio piece.

Prerequisite Map

What HW-101 depends on, and what depends on HW-101:

• Depends on: VCA-FND-102 (Python and command-line fluency, Arduino sketches and arduino-cli are command-line workflows; the firmware-debugging discipline transfers from FND-102's scripting work).
• Feeds into VCA-CSA-101: The breadboard / multimeter / logic-probe / soldering-iron tool roster originated here is exactly the hardware-side foundation CSA-101 Chapter 1 picks up when students build NAND from a flashlight. CSA-101 students who completed HW-101 land Chapter 1 with bench fluency; students arriving without HW-101 are referred to a Week-0 catch-up lab.
• Feeds into VCA-RE-011: Datasheet-reading and probe-point identification are the central skills RE-011's introductory disassembly work assumes when students examine simple firmware images.
• Feeds into VCA-RE-101: Schematic-reading, PCB-trace following, chip-package identification, and JTAG/UART probe-point recognition are the hardware-side skills RE-101's SB6141 cable-modem teardown depends on. The student who completed HW-101 walks into RE-101's first lab with the physical-bench intuition the course assumes.
• Feeds into VCA-WIR-101: RF probe technique, antenna basics, and the discipline of measuring rather than guessing are the precursors to wireless-pentesting bench work.
• Feeds into VCA-RF-201 / VCA-RF-301: The HW-101 oscilloscope + Saleae + ESP32 integration substrate carries directly into the RF-track's SDR + cellular + SATCOM lab work.
• Feeds into VCA-CON-101: The Tang Primer 25K substrate from HW-101 (~$144 kit) carries forward; the soldering / probe / datasheet discipline transfers to retro-console hardware analysis, where CON-101 students analyze and modify community soft cores rather than copy them.
• STRONG cross-cut to the SB6141 cable-modem lab-target pipeline. Cable-modem RE is the hardware-hacking endgame of the academy curriculum; HW-101's tool roster (oscilloscope / Saleae / JTAGulator / Bus Pirate / soldering iron / ST-Link/J-Link/OpenOCD / chip-off rework / flux / microscope / reflow oven) is exactly the toolset RE-101 students bring to the SB6141 teardown. The bunnie weave reinforces this thread; van Woudenberg + O'Flynn cover the chip-off + glitching + side-channel attack classes that mature SB6141 work uses.

Certification Alignment

No direct industry certification covers this content at the entry-level practitioner level. Arduino offers a Fundamentals certification that may be bundled with classroom-pack kit purchases (per the open kit-evaluation question); the credential is recognised inside the maker / Arduino-educator community but does not yet carry industry-wide weight at the cybersecurity practitioner level. Virtus's own VCA-HW-101 Certificate is the credential of record; the student's capstone data logger is the portfolio piece. CompTIA, ISC², and SANS curricula do not cover the bench-electronics and microcontroller programming HW-101 teaches; the closest 2-day industry courses (Black Hat hardware-hacking) are professional and assume the foundations HW-101 builds.

Format Prescriptions

Hour budget: ~13 lec hr + ~43 lab hr + ~40 indep hr (= ~95 hr total). Lab time roughly doubles lecture time per the bench-heavy nature of the course.

Live (standard cadence)

2 sessions/wk × 90 min each (45 min lecture + 45 min hands-on per session) + 30 min stay-after office time. 14 weeks total. Best for college-elective + adult-learning + homeschool-co-op cadence with shared bench access.

Night class (working-adult cadence)

1-2 sessions/wk in evenings; spread over ~28 weeks. Best for community-college + vocational-tech students with day jobs. Bench-heavy course; evenings need ~3-hour blocks for soldering + capstone build.

Bootcamp

8 hr/day × 5 days/wk = 40 hr/wk; total ~3 weeks. Foundationals (≤ 80 hr) fit in 2 weeks; HW-101's 95 hr lands at ~2.5 weeks. Best for adults / age-irrelevant students with prereq comfort + dedicated bench time.

Async self-paced

Lecture hours via recorded video; lab hours via per-student bench-kit purchase (~$110-150 BOM); indep hours = student pace. Includes Discord-group access (1-2 days/wk instructor-advertised availability). Live 1:1 tutoring premium tier add-on for soldering walkthrough.

High school / homeschool co-op

Adapted live cadence over a school year (~18 weeks at typical school cadence) OR semester (14 weeks at college cadence). Detailed per-syllabus planning available on request. Bench-heavy course strongly favours in-person co-op format.

Interested in VCA-HW-101?

Email interested@virtuscyberacademy.org with your background and interest. Demand signals drive the priority of charter completion.

Email interested@virtuscyberacademy.org