FREE COURSE PROJECT · Security Operations
Misconfigurations Defense for Red and Blue Teams
A fictional lab estate contains avoidable weaknesses. The defender must fix underlying causes and prove that ordinary business access still works.
Plan 9–14 hours across several sessions. Work at your own pace. Use the full Udemy course for the instructor’s complete demonstrations.
Start here
- Download and extract the pack. Open walkthrough.html in your browser to work offline.
- Read evidence-pack.html. Use only synthetic or authorized lab data.
- Record your answers in project-workbook.csv or the individual stage worksheets. Worked files include suggested decisions and limitations.
- For each task, explain what the evidence supports, what remains unknown and who should act.
- Complete the portfolio review, then continue to the full course for the complete learning sequence and its certificate of completion.
Open evidence pack · Blank project workbook · Worked examples · Completion checklist
Terms used in this project
- evidence
- An observation or record that supports a specific claim. Its source, date, scope and limitations determine what you can infer.
- MFA
- Multifactor authentication uses different types of authentication factor. Verify actual policy scope and sign-in behavior.
- baseline
- A defined minimum configuration or set of safeguards for a stated environment, with acceptance and exception criteria.
Your practice progress
0 of 7 stages marked complete
Checklist and notes can be saved in this browser.
STAGE 1 OF 7
Inventory the ten weakness classes
This is how you would approach the task
- Map MC-01 through MC-10 to affected assets and owners.
- Record current configuration and business purpose.
- Distinguish observed settings from a claim that compromise occurred.
What you will produce
Ten-class configuration inventory.
Worked reasoning and expected decision
Keep ten separate findings even if one missing baseline contributes to several. Each needs evidence and a verification path.
Review your result
Use the case facts to explain inventory the ten weakness classes. Record any missing evidence, the person who can resolve it, and what would change your conclusion.
STAGE 2 OF 7
Fix defaults and privilege separation
This is how you would approach the task
- Define approved settings for MC-01 and remove unnecessary ordinary-user admin in MC-02.
- Test the intended user workflow after change.
- Record rollback and required privileged support.
What you will produce
Defaults and privilege remediation test.
Worked reasoning and expected decision
Removing admin rights should leave the approved application usable. Document the exception route when a legitimate task needs elevation.
Review your result
Use the case facts to explain fix defaults and privilege separation. Record any missing evidence, the person who can resolve it, and what would change your conclusion.
STAGE 3 OF 7
Improve visibility segmentation and patching
This is how you would approach the task
- Identify the flows and events needed for MC-03 and MC-04.
- Design least-required communications and monitoring checks.
- Expire patch exceptions in MC-05 with named ownership.
What you will produce
Monitoring segmentation and patch plan.
Worked reasoning and expected decision
A firewall rule passing a configuration review is insufficient; observe an authorized allowed flow and a prohibited denied flow in the lab.
Review your result
Use the case facts to explain improve visibility segmentation and patching. Record any missing evidence, the person who can resolve it, and what would change your conclusion.
STAGE 4 OF 7
Close bypass MFA and share permissions
This is how you would approach the task
- Trace the legacy path in MC-06.
- Reconcile all privileged identities with MFA in MC-07.
- Verify MC-08 by testing authorized and unauthorized write actions.
What you will produce
Access-boundary validation matrix.
Worked reasoning and expected decision
An application gate does not protect a legacy route that avoids it. Retest the bypass path directly after mitigation.
Review your result
Use the case facts to explain close bypass mfa and share permissions. Record any missing evidence, the person who can resolve it, and what would change your conclusion.
STAGE 5 OF 7
Protect credentials and code execution
This is how you would approach the task
- Replace shared service credentials in the design with managed, scoped identity where feasible.
- Define storage rotation and audit responsibilities.
- Limit execution for MC-10 and verify approved software remains usable.
What you will produce
Identity and execution control design.
Worked reasoning and expected decision
A password change alone leaves shared accountability unresolved. Assign a unique identity and a traceable privilege owner.
Review your result
Use the case facts to explain protect credentials and code execution. Record any missing evidence, the person who can resolve it, and what would change your conclusion.
STAGE 6 OF 7
Use ATT&CK and sandbox testing
This is how you would approach the task
- Map relevant behaviors to the observed lab weaknesses.
- Set authorized scope before validating configuration.
- Record expected telemetry and defender evidence.
What you will produce
Behavior-to-control and telemetry map.
Worked reasoning and expected decision
Use ATT&CK to explain behavior and detection needs. The exercise performs only controlled validation in assets you own.
Review your result
Use the case facts to explain use att&ck and sandbox testing. Record any missing evidence, the person who can resolve it, and what would change your conclusion.
STAGE 7 OF 7
Find root causes and prevent recurrence
This is how you would approach the task
- Trace weak change approval, missing baselines and absent ownership.
- Write prevention checks at provisioning and change time.
- Use AI only to draft checklist questions and verify them against evidence.
What you will produce
Root cause report and prevention checklist.
Worked reasoning and expected decision
A repeated MFA omission may stem from role assignments outside the governed group. Repair the reconciliation process as well as the two accounts.
Review your result
Use the case facts to explain find root causes and prevent recurrence. Record any missing evidence, the person who can resolve it, and what would change your conclusion.
Course coverage and learning review
Course topics checked against the published curriculum returned by Udemy on 9 November 2026. Lecture titles are a coverage index; the worked project is an original exercise.
The topics below identify how this exercise connects to the course. After each section, explain how its concepts change a decision in the case. Record examples or questions that require further study in curriculum-review.csv.
SECTION 1
- Introduction · Curriculum reflection
- Course Agenda.mp4 · Curriculum reflection
- Intro to Systemic weaknesses in relation to cybersecurity misconfigurations · Curriculum reflection
- Intro to the top 10 NSA & CISA Misconfigurations · Curriculum reflection
- Misconfiguration #1 · Curriculum reflection
- Misconfiguration #2 · Curriculum reflection
- Misconfiguration #3 · Curriculum reflection
- Misconfiguration #4 · Curriculum reflection
- Misconfiguration #5 · Curriculum reflection
- Misconfiguration #6 · Curriculum reflection
- Misconfiguration #7 · Curriculum reflection
- Misconfiguration #8 · Curriculum reflection
- Misconfiguration #9 · Curriculum reflection
- Misconfiguration #10 · Curriculum reflection
- End of Section 1 Quiz · Curriculum reflection
SECTION 2-Misconfigurations Mitigation Recommendations
- An Intro to MITRE ATT&CK Framework · Curriculum reflection
- Mitigate-Default configurations of software and applications · Curriculum reflection
- Mitigate-Improper separation of user/administrator privilege · Related stage 2
- Mitigate-Insufficient internal network monitoring · Curriculum reflection
- Mitigate-Lack of network segmentation · Curriculum reflection
- Mitigate-Poor patch management · Curriculum reflection
- Mitigate-Bypass of system access controls · Curriculum reflection
- Mitigate-Weak or misconfigured multifactor authentication (MFA) methods · Curriculum reflection
- Mitigate-Insufficient access control lists (ACLs) on network shares and services · Curriculum reflection
- Mitigate-Poor credential hygiene · Curriculum reflection
- Mitigate- Unrestricted code execution · Related stage 5
- Validating Security Controls · Curriculum reflection
- Open-Source Tools for Testing Active Directory Misconfigurations · Curriculum reflection
- Intro to Open-Source Tools for addressing the top 10 misconfigurations · Curriculum reflection
- Open-Source Tools for Preventing Insufficient Access Control Lists (ACLs) on Net · Curriculum reflection
- Open-Source Tools for Preventing Lack of Network Segmentation · Curriculum reflection
- Open-Source Tools for Preventing Insufficient Internal Network Monitoring · Curriculum reflection
- Establishing security baselines to help with mitigating misconfigurations · Curriculum reflection
- Lab#1- Creating Security Baselines In Azure · Curriculum reflection
- Lab#2- PenTest Azure Deployments Misconfigurations using ChatGPT · Curriculum reflection
- Lab#3- PenTest Azure Deployments Misconfigurations using ChatGPT · Curriculum reflection
- Lab#4-Misconfigurations Research Defense Challenge · Curriculum reflection
SECTION 3-Putting everything into perspective
- Introduction to Section 3 · Curriculum reflection
- Intro to Root Cause Analysis (RCA) · Curriculum reflection
- Benefits of RCA for both Red and Blue Teamers · Curriculum reflection
- Steps for conducting RCA · Curriculum reflection
- Quiz#2 · Curriculum reflection
- Intro to creating misconfigurations mitigation checklists using AI · Curriculum reflection
- Creating a misconfiguration prevention checklist · Curriculum reflection
- Creating a misconfiguration checklist that prevents bypass of system access cont · Related stage 4
- Challenge-Create Your own misconfigurations checklist · Curriculum reflection
- Case Scenario- Applying Misconfigurations Checklist to a Data Breach Incident · Curriculum reflection
- Improving Hardening of environment against these misconfigurations · Curriculum reflection
- Prevent cloud security misconfigurations via Azure Red Team Pen Testing · Curriculum reflection
- End of Course · Curriculum reflection
Course Resources
- Bonus Lecture · Curriculum reflection
References and related CyberJA tools
Use these sources to deepen the reasoning behind the tasks. Check the current version and applicability before applying guidance to a real organization.
Build your portfolio
- Assemble the stated deliverable from every stage, with record IDs linking claims to synthetic evidence.
- Write a one-page recommendation that names the decision, evidence, assumptions, owners and next review.
- Prepare a two-minute explanation of a conclusion you changed when the evidence was incomplete.
- Label the work as a simulated project in your CV or professional profile.
Self-assessment rubric
Score each area from 0 to 4: 0 absent, 1 assertion without support, 2 partial evidence, 3 supported and reproducible, 4 supported with limitations and alternatives. Aim for at least 3 in every area.
- Correct use of the scenario and source facts.
- Clear reasoning and treatment of uncertainty.
- Practical implementation or decision steps.
- Evidence, ownership and verification.
- Clear communication and honest portfolio claims.
This rubric is a self-review aid. Your checklist is self-recorded.
Continue with the full Udemy course
Use your completed practice work as a starting point for Richea Perry’s full course, Misconfigurations Defense for Red and Blue Teams. Learn through the instructor’s complete demonstrations and course resources.
Enroll and complete the required curriculum items on Udemy to receive the course’s certificate of completion. This free project records practice progress. The certificate is issued through completion of the full Udemy course.
Take the full course on Udemy ↗Udemy certificate requirements · Discuss your practice in CyberJA Connect