The Week-by-Week Syllabus
This syllabus focuses on hands-on projects paired with essential theoretical knowledge in cybersecurity.
Week 1: Secure Software Development Lifecycle (SDLC)
What to learn: Principles of secure SDLC, threat modeling, and security requirements gathering.
Why this comes before the next step: Understanding SDLC principles sets a strong foundation for integrating security at every phase of development.
Mini-project/Exercise: Create a threat model for a sample application, identifying potential vulnerabilities.
Week 2: Authentication and Authorization
What to learn: Implement OAuth 2.0 and OpenID Connect in a web application.
Why this comes before the next step: Mastering secure authentication is critical before exploring deeper security layers.
Mini-project/Exercise: Build a sample application that uses OAuth 2.0 for user authentication.
Week 3: Vulnerability Assessment Tools
What to learn: Practical use of OWASP ZAP and Burp Suite for web application security testing.
Why this comes before the next step: Familiarity with these tools is necessary to conduct effective security assessments.
Mini-project/Exercise: Perform a vulnerability scan on a sample application and report findings.
Week 4: Secure Coding Practices
What to learn: Secure coding techniques in Java using Spring Security and Python using Flask-Security.
Why this comes before the next step: Knowing how to write secure code helps mitigate risks identified in previous assessments.
Mini-project/Exercise: Refactor existing insecure code to incorporate secure coding practices.
Week 5: Penetration Testing Basics
What to learn: Introduction to penetration testing with Metasploit, including basic exploits and payloads.
Why this comes before the next step: Understanding penetration testing lays the groundwork for assessing the security posture of your applications.
Mini-project/Exercise: Set up Metasploit and execute a simple penetration test against a vulnerable application.
Week 6: Writing Security Policies
What to learn: Developing effective security policies and requirements for development teams.
Why this comes before the next step: A solid policy framework guides all future security practices and ensures team compliance.
Mini-project/Exercise: Draft a security policy document for a development team based on your learned principles.