Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
syssec:semester_startup [2019/03/17 21:24] vnbruno |
syssec:semester_startup [2019/09/05 00:43] (current) sjames5 Update content and wording slightly |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Semester Startup Checklist ====== | + | # Semester Startup Checklist |
| - | # BEFORE SEMESTER | + | ## BEFORE SEMESTER |
| ### In General | ### In General | ||
| - | * Make sure that current class lead and "seasoned (1+ semester)" SecDev members + Leads for Lockdown to (`ubnetdef@buffalo.edu` aka `UBNETDEF-LIST@listserv.buffalo.edu`) | + | * Make sure that current class lead, "seasoned" (1+ semester) SecDev members, and team leads for Lockdown are added to (`ubnetdef@buffalo.edu` aka `UBNETDEF-LIST@listserv.buffalo.edu`) |
| * Send list to: [Dave](:user:djmurray), [Kevin](:user:kpcleary), or [James](:user:jamesdro) | * Send list to: [Dave](:user:djmurray), [Kevin](:user:kpcleary), or [James](:user:jamesdro) | ||
| - | * Add all of SecDev to the vSphere "SecDev-Users" | + | * Add all of SecDev to the "SecDev" group in vCenter |
| * Contact the nearest vCenter Administrator | * Contact the nearest vCenter Administrator | ||
| Line 26: | Line 26: | ||
| * Ensure all of SecDev is joined to the SysSec channel (`~syssec`) | * Ensure all of SecDev is joined to the SysSec channel (`~syssec`) | ||
| - | |||
| - | * Create a schedule for the semester, look at the previous SysSec syllabus to see a topic-by-topic one | ||
| ### Before First Class | ### Before First Class | ||
| Line 34: | Line 32: | ||
| * Assign roles to each of the many weekly tasks | * Assign roles to each of the many weekly tasks | ||
| * Clone VMs on vCenter | * Clone VMs on vCenter | ||
| - | * Update attendance | + | * Set up attendance form |
| * Lecture | * Lecture | ||
| * Grade and update UBLearns | * Grade and update UBLearns | ||
| * Post homework to homework.ubnetdef.org | * Post homework to homework.ubnetdef.org | ||
| - | * Keep class doc's in the Wiki updated | + | * Keep class docs in the Wiki updated |
| * Upload lecture slides to website | * Upload lecture slides to website | ||
| * Upload the schedule to website | * Upload the schedule to website | ||
| Line 44: | Line 42: | ||
| * Discuss syllabus and agree to grading scheme, the current one as of System Security Spring 2019 works well | * Discuss syllabus and agree to grading scheme, the current one as of System Security Spring 2019 works well | ||
| * Adjust syllabus with new SecDev members | * Adjust syllabus with new SecDev members | ||
| - | Make vCenter accounts and folders for students + assign permissions | + | * All SysSec should be emailed a few days before the first class with a link to the syllabus and with basic directions to the classroom |
| - | * All SysSec should be emailed ahead of the first class asking them to download the Windows Client and if they have a Mac the Windows VM | + | * [Typically before second class] Make vCenter accounts and folders for students + assign permissions |
| - | * [VCENTER] | + | |
| - | * [VM Link] | + | |
| - | # DURING SEMESTER | + | ## DURING SEMESTER |
| ### [Overview] Every Class "Checklist" of Tasks | ### [Overview] Every Class "Checklist" of Tasks | ||
| Line 77: | Line 73: | ||
| Each section below are what we consider our //core// classes, in each topic there is some information about reasoning and how we went about things. These are **NOT** playbooks and exact steps, but rather guidance on how we executed each topic and corresponding lecture. | Each section below are what we consider our //core// classes, in each topic there is some information about reasoning and how we went about things. These are **NOT** playbooks and exact steps, but rather guidance on how we executed each topic and corresponding lecture. | ||
| - | # 1000 Mile Overview + Virtualization + Setup | + | ## 1000 Mile Overview + Virtualization + Setup |
| ### Disclaimer | ### Disclaimer | ||
| Line 96: | Line 92: | ||
| ### During Class | ### During Class | ||
| - | * This is class leads lecture, they should be speaking to the students in a confident manner | ||
| - | * Class lead starts the class off, makes sure all students are in the right place | ||
| - | * SecDev members introduce themselves, ice-breakers are fun | ||
| - | * Makes a great example for the class when SecDev takes the ice-breaker seriously | ||
| - | * Students turn for the ice-breaker | ||
| - | * Overview of Syllabus, Website, Wiki, Homework Engine | ||
| - | * Have students sign the Code-of-Ethics, digital is ok - [Ethics](https://wiki.ubnetdef.org/code_of_ethics?) | ||
| - | * Have them submit to `homework.ubnetdef.org` | ||
| - | * 10 minute break | ||
| - | * 1000 Mile Overview Lecture | ||
| - | * 10 minute break | ||
| - | * Virtualization and Infrastructure Overview/ Mini-Lecture | ||
| - | During the first class you want to accomplish the items below, have a SecDev member send invites and the others make accounts if not done yet. | + | * This is class leads lecture, they should be speaking to the students in a confident manner |
| + | * Class lead starts the class off, makes sure all students are in the right place | ||
| + | * SecDev members introduce themselves, ice-breakers are fun | ||
| + | * Makes a great example for the class when SecDev takes the ice-breaker seriously | ||
| + | * Students turn for the ice-breaker | ||
| + | * Overview of Syllabus, Website, Wiki, Homework Engine | ||
| + | * Have students sign the Code-of-Ethics, digital is ok - [Ethics](https://wiki.ubnetdef.org/code_of_ethics?) | ||
| + | * Have them submit to `homework.ubnetdef.org` | ||
| + | * 10 minute break | ||
| + | * 1000 Mile Overview Lecture | ||
| + | * 10 minute break | ||
| + | * Virtualization and Infrastructure Overview/ Mini-Lecture | ||
| - | * Invite all of SysSec and have get them in Mattermost | + | **During the first class you want to accomplish the items below, have a SecDev member send invites and the others make accounts if not done yet. |
| - | * [After Registration] Force join (`/invite @username`) every SysSec student to the `~syssec` channel | + | ** |
| - | * Have everyone connect into vCenter `cdr-vcenter1.cse.buffalo.edu` | + | |
| - | * Have everyone sign-up on LucidChart | + | * Invite all of SysSec and have get them in Mattermost |
| - | * Make everyone a `homework.ubnetdef.org` account and have them all sign and submit the `Code of Ethics` | + | * [After Registration] Force join (`/invite @username`) every SysSec student to the `~syssec` channel |
| - | * Anything that you don't get to above is homework for the students | + | * Have everyone connect into vCenter `cdr-vcenter1.cse.buffalo.edu` |
| - | * You may not get to it all... don't worry about it we often don't | + | * Have everyone sign-up on LucidChart |
| + | * Make everyone a `homework.ubnetdef.org` account and have them all sign and submit the `Code of Ethics` | ||
| + | * Anything that you don't get to above is homework for the students | ||
| + | * You may not get to it all... don't worry about it we often don't | ||
| Line 130: | Line 128: | ||
| - | # Networking 101 | + | ## Networking 101 |
| ### Disclaimer | ### Disclaimer | ||
| - | * In the past we have taught this class as a general networking foundation lecture, but found that was really to much for students. So we moved to a more focused lecture on our Infrastructure and what they will need to know for the labs and assignments. So a more targeted lecture on networking so the students can be successful in the assignments without having to know everything. | + | * In the past we have taught this class as a general Networking foundation lecture, but found that was really to much for students. So we moved to a more focused lecture on our Infrastructure and what they will need to know for the labs and assignments. So a more targeted lecture on Networking so the students can be successful in the assignments without having to know everything. |
| ### Lecture Goals | ### Lecture Goals | ||
| - | * Students to gain enough networking knowledge to be successful in the assignments | + | * Students to gain enough Networking knowledge to be successful in the assignments |
| - | * Gain a bit of understanding of the networking around them (LAN, WAN, IP Addresses) | + | * Gain a bit of understanding of the Networking around them (LAN, WAN, IP Addresses) |
| ### Preparation | ### Preparation | ||
| - | * Students //should// have folders in vCenter | + | |
| - | * pfSense template should be cloned into those folders | + | * Students //should// have folders in vCenter |
| - | * Point students to the Wiki where there will be documentation on "How to Load an ISO Image" | + | * pfSense template should be cloned into those folders |
| - | * Make sure there is enough static routes for all the students | + | * Point students to the Wiki where there will be documentation on "How to Load an ISO Image" |
| - | * Upload the pfSense assignment to engine.ubnetdef.org | + | * Please keep these doc's updated! |
| - | * Make sure everyone has signed the Ethics Policy **BEFORE** using vCenter | + | |
| - | * Upload slides to website BEFORE lecture | + | * Make sure there is enough static routes for all the students |
| - | * Make sure attendance is posted | + | * Upload the pfSense assignment to engine.ubnetdef.org |
| + | * Make sure everyone has signed the Ethics Policy **BEFORE** using vCenter | ||
| + | * Upload slides to website BEFORE lecture | ||
| + | * Make sure attendance is posted | ||
| ### During Class | ### During Class | ||
| - | * Class lead welcomes class back | + | * Welcome the class back and start class off at 6:30pm |
| - | * House Keeping: is everyone in Mattermost, can log into vCenter | + | * We want to set good precedence of class starting right away for students |
| - | * Networking 101 Lecture | + | |
| - | * Break | + | * House Keeping: is everyone in Mattermost, can log into vCenter, etc |
| - | * Networking lecture | + | * Networking 101 Lecture (60 mins) |
| - | * Topology activity | + | * Break - 10 Mins |
| - | * break | + | * Networking Lecture (30 - 45 mins) |
| - | * explain homeworks and how they can see them, recap of last week just different assignment | + | * Topology Activity (20 - 30 mins) |
| - | * get everyone not caught up caught up and have people work on installing vCenter, keep them to 9pm minimum | + | * Break 10 Mins |
| + | * Explain homework's and how they can see them, recap of last week just different assignment | ||
| + | * Get everyone not caught up, caught up and have people work on installing pfSense | ||
| + | * Point them to the Wiki for installing the ISO and have them read the assignment prompt | ||
| + | * This is to help the students get used to Googling things and reading the doc's | ||
| + | * Keep them to 9pm, minimum | ||
| + | |||
| ### Pitfalls | ### Pitfalls | ||
| - | * Not teaching networking to the infrastructure | + | * Not teaching Networking to the infrastructure |
| * Networking in general... | * Networking in general... | ||
| + | * ... | ||
| - | # Windows | + | ## Windows |
| ### Disclaimer | ### Disclaimer | ||
| Line 207: | Line 216: | ||
| - | # Linux | + | ## Linux |
| ### Disclaimer | ### Disclaimer | ||
| Line 214: | Line 223: | ||
| - | ### Goals | + | ### Lecture Goals |
| * Understand how the Linux Operating System works internally | * Understand how the Linux Operating System works internally | ||
| * Gain understanding working with shells | * Gain understanding working with shells | ||
| Line 220: | Line 229: | ||
| * Learn some tools to use to troubleshoot networking | * Learn some tools to use to troubleshoot networking | ||
| - | ### Execution | + | |
| + | ### Preparation | ||
| * Two virtual machines for a CLI box and GUI | * Two virtual machines for a CLI box and GUI | ||
| + | |||
| + | |||
| + | ### During Class | ||
| * Linux lecture | * Linux lecture | ||
| * Attendance | * Attendance | ||
| * Start having the students work on the Linux assignment. | * Start having the students work on the Linux assignment. | ||
| * Goal is to just install the Operating Systems and assign static ip addresses | * Goal is to just install the Operating Systems and assign static ip addresses | ||
| - | * They will install services on them after the services lecture | + | * They will use different boxes for the Services lecture, and use Linux box they setup here to interact with those new servers |
| * Make sure every students network is fully operational, catch people up who are behind | * Make sure every students network is fully operational, catch people up who are behind | ||
| Line 236: | Line 249: | ||
| - | # Networking 102 (Typically Kevin) | + | ## Networking 102 (Typically Kevin) |
| ### Disclaimer | ### Disclaimer | ||
| Line 252: | Line 265: | ||
| * None | * None | ||
| - | # Services | + | ## Services |
| ### Disclaimer | ### Disclaimer | ||
| - | * Many students think Linux is magic, our job is to fix that. | + | * Students think Linux is magic, our job is to fix that. |
| - | * Many don't understand shells and Terminals | + | * Many don't understand Shells and Terminals |
| + | * Many are not Software Developers, so they might find it difficult to understand shipping from code to software on a box | ||
| ### Goals | ### Goals | ||
| - | * Understand how the Linux Operating System works internally | + | * Understand what a //service// actually is |
| - | * Gain understanding working with shells | + | * Gain enough conceptual understanding to understand a LAMP stack |
| - | * To gain confidence in controlling an Operating System through a shell and no GUI | + | * Learn some Linux commands and tools to find and troubleshoot services |
| - | * Learn some tools to use to troubleshoot networking | + | * Understand why services are so important - in the workplace and competitions |
| ### Tasks Before Class | ### Tasks Before Class | ||
| Line 272: | Line 286: | ||
| ### During Class | ### During Class | ||
| - | * Have class lead start class off at 6:30pm. | + | * Have class lead start class off at 6:30pm, sharp! |
| - | * How are assignments going? Do anyone need anything? | + | * How are assignments going? Does anyone need anything? |
| * Service Lecture | * Service Lecture | ||
| + | * The services lecture in the past was around 80-90 mins, aim for the first part to be about 60 mins | ||
| * 10 Minute Break! | * 10 Minute Break! | ||
| - | * Services Lecture | + | * Services Lecture (The last 20-30 mins) |
| * Attendance | * Attendance | ||
| * Start LAMP Assignment | * Start LAMP Assignment | ||
| + | * SecDev member to show the students how to make the DMZ work, so we can avoid `pfctl -d` | ||
| + | * If time, run through how to setup the database (You can either run through the install or make the VM for the students) | ||
| ### Pitfalls | ### Pitfalls | ||
| - | * None. | + | * TURN ON THE STUDENTS VM'S BEFORE CLASS SO WE DON'T BLOW UP VCENTER |
| + | * Make sure during the working sessions that SecDev is walking around and helping students | ||
| + | * Might be work it to use the laptops in the room instead of some students laptops | ||
| + | * Especially Mac users... (Assuming we are still in vCenter < 6.0, this becomes nil after) | ||
| - | # Firewalls | + | ## Firewalls (Basic) |
| ### Lecture Goals | ### Lecture Goals | ||
| Line 304: | Line 324: | ||
| ### Pitfalls | ### Pitfalls | ||
| - | # MBA For a Day + Resume | + | # Firewalls (Next Gen) |
| + | |||
| + | ### Lecture Goals | ||
| + | * Placeholder | ||
| + | |||
| + | ### Preparation | ||
| + | * Placeholder | ||
| + | |||
| + | |||
| + | ### During Class | ||
| + | * Placeholder | ||
| + | * Placeholder | ||
| + | |||
| + | |||
| + | ### Pitfalls | ||
| + | |||
| + | |||
| + | |||
| + | ## MBA For a Day + Resume | ||
| - | # Risk Management | + | ## Risk Management |