CYB102 Assignment Help — Project 2, Audit Lab & Capstone HW 3

Assignment 1

CYB102 · Unit 2 · Project 2 — "Let's wget This Bread"

Source: courses.codepath.org/courses/cyb102/unit/2 — Submit by Friday, September 19, 11:59PM EDT.

Machine Access Check

To proceed with this unit, please ensure you have access to a cyb102 Ubuntu VM using Azure Labs or an "Alternative Option" from the IDE Setup Guide. Alternatives that work for this unit: Azure VM, VMware on Windows / Intel Mac, VMware on M-Chip Mac, Manual VM.

Overview

For Project 2 we will continue using the Linux Audit daemon set up in this unit's lab to perform the following:

• Watch a protected directory of our filesystem through writing custom audit.rules
• Run provided attack scripts that will alter some files in that directory
• Identify which files in our filesystem were modified by reviewing the audit output and filtering on a filter key via ausearch

Goals

By the end of this assignment, you will be able to…

• Configure a set of Audit rules to monitor file changes in /protected_files.
• Launch three attacks on some unknown files, and use Audit to identify the altered files and which attacks made the changes.

Resources

• Vim Cheat Sheet — most common vim editing commands on 1 page
• Auditctl Manual Pages — Ubuntu package guide detailing flags and configuration options
• Auditd Rules Guide — guide to use the Linux Audit daemon to watch files and directories

What You'll Turn In

For this assignment, you'll be filling and submitting a copy of the Project 2 Submission Template (Google Doc). Before proceeding, we recommend you open it up now and read over the requirements in the document. It might be easier to "fill-as-you-go" than try to fill it all out after you complete the project.

Required Challenges — to receive full credit, you must submit:

• The names of the files modified by the attack scripts.
• The (file, attack) pairings of which attack changed which file.

Note: There are no stretch features for this project.

Tasks

1. Download the Starter Repo to your VM (make sure you are in the ~ directory so filepaths are consistent) with the command:

   wget https://github.com/codepath/project2/archive/main.zip

   Note: the above file is zipped and must be unzipped before you can use its contents. You can unzip the file by running unzip main.zip.
2. Navigate into the Project 2 folder with cd project2-main.
3. Add permissions to run the attack files with chmod u+x attack-a attack-b attack-c.
4. Set up write watch permission file monitoring rules for the 10 files in /protected_files. For a refresher on creating rules to watch files and directories for write mutations review the Auditd Rules Guide.
5. Run ./attack-a, ./attack-b, and ./attack-c to change unknown files in /protected_files. As we've used chmod to make the attack files executable, running ./attack-a should be all you need to run the attack-a, for instance. Each attack executable modifies a different file in the protected directory, therefore the attacks may either be run all at once or one by one.
6. Use the event log filtering techniques from this unit's lab to identify which attack was responsible for changing which file.

Hints

• If you mess up your files and want to start over, you can always delete the project2-main folder and use wget to download a fresh copy.
• Remember how important the filter key is and what it does — it allows us to filter the event logs for a specific rule. Since this is the only identifier for our rules, we probably don't want to repeat filter keys, right?
• Remember to restart Audit with sudo systemctl restart auditd after updating the rules so that the changes take hold.

Assignment 2

CYB102 · Project 2 — Submission Template (Google Doc)

Reflection (Required)

Reflection Question #1: If I had to explain "what Audit does" in 3 emojis, they would be… (Feel free to put other comments about your experience in this unit here, too!)

Reflection Question #2: How does Audit track changes made to specific files?

Shoutouts: Share appreciation for anyone who helped you out with this project or made your day a little better!

Required Challenges

• Item #1: The names of the affected files.
• Item #2: Every (file, attack) pairing for which file was changed by which attack.

Submission Checklist

Check off each of the features you have completed. You will only be graded on the features you check off.

• Required Challenges — Item #1
• Required Challenges — Item #2

Tip: You can see specific grading information, including points breakdown, by going to the grading page on the course portal.

Submit Your Work

1. Click the Share button at the top of your screen and double-check that anyone with the link can edit.
2. Copy the link to this document.
3. Submit the link on the portal.

Assignment 3

Homework 3 — Final Report, Poster, and Presentation Prep (ISC 4941 Capstone)

Due: October 27, 2025 · Course: ISC 4941 — Data Science Capstone (frequently bundled with CYB102 coursework).

Objective

This assignment helps you consolidate your project's findings, prepare your final report, design your poster, and organize your presentation. By completing Homework 3, you will be ready to deliver your final deliverables (Milestones 6–8).

Learning Goals

• Synthesize results from data preparation, modeling, and evaluation.
• Translate technical findings into clear visuals and concise text for a non-technical audience.
• Design an academic poster and prepare a short presentation summarizing your work.

1. Final Report Draft (40 pts)

Prepare a near-final written report (3–5 pages plus visuals). Include the following sections:

• Title and Authors (Team #)
• Abstract (150–200 words) summarizing your question, methods, and key findings.
• Introduction: Restate the problem and motivation.
• Methods: Summarize preprocessing, models tested, and metrics used.
• Results & Discussion: Compare models with visuals and interpret results.
• Conclusions & Next Steps: Summarize insights, implications, and future improvements.
• References: Cite datasets, tools, and key sources.

2. Poster Design Proposal (35 pts)

Create a 1-page draft layout of your final poster (PowerPoint, Canva, or similar). Include:

• Title, team members, and FAU logo.
• Problem & Objectives section.
• Dataset & Methods section.
• Results & Visuals section (e.g., ROC, confusion matrix, feature importance).
• Conclusions & Impact section.
• At least two figures (real or placeholders).

3. Presentation Slides (25 pts)

Prepare a short presentation (5–7 slides, ~5 minutes) covering:

• Motivation and problem overview.
• Data and methods summary.
• Key results and takeaways.
• Visual storytelling with clear, minimal text.
• Defined speaking roles for each team member.

Bonus (+5 pts): Outstanding creativity or integration of results into the poster.

Submission

Submit the following as a single ZIP file on Canvas:

• teamX_HW3_report.pdf (Final Report Draft)
• teamX_HW3_poster.pdf (Poster Design Draft)
• teamX_HW3_slides.pptx or .pdf (Presentation Slides Draft)
• Provide for your code a link to a GitHub or Google Colab repository.

Make sure your submission reflects collaboration from all team members and aligns with Milestones 6–8 in the Capstone schedule.