CyberPatriot Resources · Resource 12
Team Templates & Offline Reference Pack
Build a clean, searchable collection of team templates and defensive references that helps competitors communicate, document, verify, and find trusted technical information quickly.
Always follow the current CyberPatriot Rules Book, round instructions, and coach guidance regarding permitted resources. Never treat this page as authorization to use a resource during a scored competition.
Competition integrity boundary
A reference pack is not a place for competition intelligence
Keep active-round answers, another team's findings, restricted images, credentials, scoring information, and other controlled competition material out of reusable study references.
Core team templates
Mission Extraction Sheet
Turn the README and round instructions into a short list of systems, approved users, required services, restrictions, and priorities.
Priority Board
Give the team one shared view of what is being investigated, changed, verified, or deferred.
Change Log
Record meaningful changes so the team can understand what happened and recover from mistakes.
Evidence Log
Preserve useful observations before remediation and make findings reproducible for another teammate.
Handoff Note
Transfer ownership without forcing the next teammate to repeat the investigation.
Final Verification Sheet
Run a controlled final sweep without introducing risky late-round experimentation.
Shared status language
A short common vocabulary makes the priority board easier to read and reduces ambiguous handoffs.
Not Started
The finding or review item has not yet been assigned or investigated.
Investigating
A teammate owns the item and is collecting evidence or checking dependencies.
Changed
A modification was made but the result has not yet been fully verified.
Verified
The change and required functionality were checked successfully.
Unresolved
The team investigated the issue but does not yet have a safe, justified resolution.
Do Not Touch
The team identified an explicit mission dependency, restriction, or unacceptable risk.
Suggested reference-pack structure
00-RULES-AND-ROUND01-MISSION-TEMPLATES02-WINDOWS03-WINDOWS-SERVER04-LINUX05-CISCO06-FORENSICS07-QUICK-REFERENCEGeneral study content
Useful material to prepare
Keep out
Material that does not belong in the pack
Current competition answers
Do not place vulnerability answers, discovered scoring items, or answer keys from an active scored round into a shared reference pack.
Other teams' material
Do not collect another team's scripts, notes, findings, scoring reports, or competition intelligence.
Competition credentials
Do not store Team IDs, unique identifiers, passwords, NetAcad credentials, or other sensitive round credentials in a general study pack.
Restricted images or round files
Competition images and controlled round materials should be handled only according to current CyberPatriot instructions.
Unreviewed hardening scripts
A large script can make broad changes, break mission services, and hide what actually changed.
Mystery command collections
Do not build a pack of commands the team cannot explain, scope, or verify.
Quick-reference categories
Windows
Windows Server
Linux
Cisco
Forensics
Team Operations
Build references that are actually usable
01
Know the source
Prefer official vendor documentation, official project manuals, CyberPatriot materials, and reputable security standards.
02
Know the version
A command, setting, service, or menu can change between operating-system and product versions.
03
Know the purpose
Every reference entry should explain why the command or setting matters, not only what to type.
04
Know the impact
Mark commands and settings that can recursively change files, stop services, alter firewall state, or affect multiple users.
05
Know the verification
A useful reference should include how to confirm that the system still performs its required function.
06
Keep it searchable
Use clear names, short headings, platform folders, and predictable structure instead of one enormous document.
Example change log
| Time | System | Owner | Original State | Action | Reason | Verification | Status |
|---|---|---|---|---|---|---|---|
| 10:14 | Win11 | Alex | Remote Desktop enabled | Disabled RDP | README did not require remote access | Confirmed local login and required application | Verified |
| 10:27 | Ubuntu | Jordan | User in sudo group | Removed unauthorized sudo membership | User approved but not approved administrator | User login still works | Verified |
| 10:41 | Server | Sam | Share permission under review | No change | Required department share may depend on existing group | Needs team lead review | Unresolved |
Example handoff note
System
Ubuntu VM
Issue
Unexpected listening service on TCP port 8080
Checked
ss output, systemctl status, service configuration, journal entries
Finding
Service is tied to the required internal web application
Action
No disable action taken
Next
Review firewall exposure while preserving local application access
Pre-round reference-pack review
Confirm the current CyberPatriot rules and round instructions.
Confirm which references and resources are permitted for that round.
Confirm required competition software and network access.
Test the team's lab computers and virtualization environment.
Organize reference material by platform.
Remove stale or duplicate copies of notes.
Remove any restricted or team-external competition material.
Prepare blank mission, priority, evidence, change, and handoff templates.
Make the pack readable without depending on one teammate.
Confirm everyone knows where the pack is located.
Keep credentials separate from general reference material.
Let the coach control materials that the rules assign to the coach.
Using the pack during team operations
Start
Work
Sync
Finish
Weak pack vs better pack
Weak approach
Create a 200-page document containing every command the team has ever seen.
Better approach
Organize short references by platform, task, impact, and verification method.
Weak approach
Copy scripts from the internet into the reference pack.
Better approach
Include only commands and scripts the team understands, is permitted to use, and can verify safely.
Weak approach
Store passwords and competition credentials beside general notes.
Better approach
Keep sensitive competition credentials controlled separately according to current rules and coach instructions.
Weak approach
Use an old checklist without reading the current README.
Better approach
Treat the current mission and round instructions as the authority for that image.
Weak approach
Record only successful fixes.
Better approach
Record meaningful changes, verification, unresolved risks, and important no-change decisions.
Weak approach
One teammate owns all reference knowledge.
Better approach
Use a shared structure that every team member can navigate quickly.
Final reference-pack checklist
Verify current rules before every scored round.
Keep the competition README and mission above generic hardening advice.
Use blank reusable team templates.
Organize references by platform and task.
Prefer official documentation.
Include purpose and verification with important commands.
Flag high-impact actions clearly.
Keep restricted competition materials out of general reference packs.
Never use another team's competition information.
Keep sensitive credentials controlled separately.
Review and clean the pack before competition day.
Use the pack to support reasoning rather than replace it.