Virtual PC Build: Design the System for the Job

The Garden State Cyber curriculum includes a virtual desktop PC-building activity.

The point should be more than matching parts.

A good build starts with a workload, chooses components that support it, and explains how failures or security controls affect the complete system.

The design brief

Build a fictional desktop for a school cybersecurity lab.

Requirements:

• web-based coursework
• virtual machines or browser labs
• packet-capture analysis of supplied files
• basic scripting
• video conferencing
• local project storage with cloud backup
• no gaming-performance requirement

You have a limited budget.

Choose components by requirement

Your virtual build should include:

• CPU
• RAM
• storage
• motherboard/platform
• network interface
• input/output devices
• backup strategy

For every component, write:

Requirement

What course task needs this component or capacity?

Choice

What type or capacity did you select?

Trade-off

What did you give up to stay within the budget?

Security/reliability concern

What can fail or expose data?

Do not overspend without a reason

More expensive is not automatically better.

If the workload does not require a high-end GPU, spending the budget there may reduce money available for memory, storage, warranty, backup, or other useful needs.

Architecture is prioritization.

Add security controls to the build

Your system proposal must include:

• individual accounts
• supported operating system
• automatic updates
• screen lock
• firewall
• least-privilege daily use
• backup plan
• storage protection appropriate to the scenario

Explain which CIA property each control helps protect.

Failure injection

After you finish the build, draw one teacher-provided failure card:

• SSD fails
• one RAM module fails
• Wi-Fi adapter fails
• laptop/desktop is stolen
• cloud backup is unavailable
• power interruption corrupts an active file

Revise the architecture so the course can continue or recover.

Build the system diagram

Show:

input → CPU/RAM → storage → output/network

Add:

• operating system
• applications
• user account boundary
• backup location

Then mark where each of your security controls applies.

Defend the design

Prepare a two-minute architecture defense:

• What workload drove your choices?
• Which component was the hardest trade-off?
• Which failure would hurt the class most?
• Which security control provides the most value?
• What would you upgrade first with an additional $200 fictional budget?

Evidence for Lesson 3

Submit:

• virtual PC parts list
• requirement/choice/trade-off table
• system architecture diagram
• failure-injection revision
• two-minute architecture defense outline

Finish with:

My build is defensible because every major component connects to ________, not because ________.

A system design is stronger when every part has a reason to exist and every critical failure has a recovery story.