Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
syssec:semester_startup [2019/04/04 20:19] vnbruno ↷ Page moved from misc:semester_startup to syssec:semester_startup |
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 132: | Line 128: | ||
| - | # Networking 101 | + | ## Networking 101 |
| ### Disclaimer | ### Disclaimer | ||
| Line 182: | Line 178: | ||
| - | # Windows | + | ## Windows |
| ### Disclaimer | ### Disclaimer | ||
| Line 220: | Line 216: | ||
| - | # Linux | + | ## Linux |
| ### Disclaimer | ### Disclaimer | ||
| Line 253: | Line 249: | ||
| - | # Networking 102 (Typically Kevin) | + | ## Networking 102 (Typically Kevin) |
| ### Disclaimer | ### Disclaimer | ||
| Line 269: | Line 265: | ||
| * None | * None | ||
| - | # Services | + | ## Services |
| ### Disclaimer | ### Disclaimer | ||
| Line 309: | Line 305: | ||
| - | # Firewalls (Basic) | + | ## Firewalls (Basic) |
| ### Lecture Goals | ### Lecture Goals | ||
| Line 346: | Line 342: | ||
| - | # MBA For a Day + Resume | + | ## MBA For a Day + Resume |
| - | # Risk Management | + | ## Risk Management |