|
1 | 1 | <div class="flex-container"> |
2 | 2 | <img src="https://github.com/ProfessionalLinuxUsersGroup/img/blob/main/Assets/Logos/ProLUG_Round_Transparent_LOGO.png?raw=true" width="64" height="64"></img> |
3 | 3 | <p> |
4 | | - <h1>Under Construction</h1> |
| 4 | + <h1>Unit 10 - Recap and Final Project</h1> |
5 | 5 | </p> |
6 | 6 | </div> |
| 7 | + |
| 8 | +## Overview |
| 9 | + |
| 10 | +This final unit serves as a reflection point for the course, providing students the |
| 11 | +opportunity to step back, assess what they've learned, and think deeply about how |
| 12 | +these skills apply to real-world systems and career goals. |
| 13 | + |
| 14 | +Unit 10 is less about introducing new tools or frameworks and more about |
| 15 | +consolidating your knowledge into a cohesive security engineering mindset. Whether |
| 16 | +through discussion posts, project finalization, or self-assessment, this unit is |
| 17 | +designed to help you articulate your growth and prepare to present yourself as a |
| 18 | +capable security professional. |
| 19 | + |
| 20 | +## Learning Objectives |
| 21 | + |
| 22 | +1. Reflect on key topics covered throughout the course and identify strengths and weaknesses. |
| 23 | +2. Practice articulating technical security concepts and processes in your own words. |
| 24 | +3. Prepare for technical interviews or resume reviews through self-explanation of security workflows. |
| 25 | +4. Finalize and polish your capstone project deliverables. |
| 26 | +5. Connect course topics to real industry expectations in security engineering. |
| 27 | + |
| 28 | +## Relevance & Context |
| 29 | + |
| 30 | +Cybersecurity isn't about memorizing tools -- it's about learning how to |
| 31 | +think like both a defender and an attacker. |
| 32 | +By this point in the course, you’ve explored threat modeling, auditing, configuration management, logging, and more. This unit challenges you to connect the dots. |
| 33 | + |
| 34 | +Real-world roles demand not just technical skills, but also the ability to |
| 35 | +communicate your reasoning, defend your design decisions, and think critically under |
| 36 | +pressure. |
| 37 | + |
| 38 | +Reflection helps you distill your experience into something actionable and |
| 39 | +transferable -- whether you're applying for jobs, building infrastructure, or |
| 40 | +consulting on hardening strategies. It can also help you determine where your weak |
| 41 | +points are and what you need to spend more time on learning. |
| 42 | + |
| 43 | +## Prerequisites |
| 44 | + |
| 45 | +To make the most of this unit, students should: |
| 46 | + |
| 47 | +1. Have completed or attempted all prior labs and worksheets. |
| 48 | +2. Be comfortable referencing course topics such as logging, STIGs, monitoring, automation, and baselining. |
| 49 | +3. Be prepared to synthesize and summarize technical content in their own words. |
| 50 | +4. Have begun (or be close to completing) their final project documentation and diagrams. |
| 51 | + |
| 52 | +## Key terms and Definitions |
| 53 | + |
| 54 | +This unit's terms and definitions are to be drawn from the lesson or recording. |
| 55 | + |
| 56 | +As you watch the recording, take note of terms you're not familiar with and take the |
| 57 | +time to research them. |
0 commit comments