|
Josh Hale -- jhale
Critical Systems Still waiting to hear from Jen No way to get the mainframe - ¼ million dollars What are critical things we want to look at? Non-mainframe won't work Chart of systems connecting everything? Crawler? Not feasible Doug will contact Jen & Mike to find out about that Who else to include? Not Networking people We're good at this point Apps Back-end, drupal, registrar, application to ISU, etc. Should be able to stand up 80% (in general) of ISU's infrastructure Scenario engaging multiple teams (Web dev, DNS, etc.) Scenario development, tabletop exercise for Blue Team training ISEFlow: Documentation? Talk to Jeff Play with config file, don't need to modify it Each subnet is a building, so topology, it is a giant star Config files to replicate ISU, work on private networks, talk with Jeff, builds routable Internet Config file same as CDC's ISERink has its own DNS server, so anything we steal is going to have to be in that DNS (199.116.?.?) We'll have to change IP address of DNS server Replicate that piece of infrastructure, b/c it'll by default point to DNS servers Could also replicate root server or use proxy for it Doug will push on Jen to see what she's thinking Front end services critical to university, everything w/netid is standalone Access plus is front door to mainframe Netreg mess 3270 mainframe app Particular scenarios? Environmental/Physical Disaster, Human Element, Technical Failure, Political Threat/Sabotage, Advanced Persistent Threat Sit with CIO and draw different people into game Some simply cyber Access Control ISU Alert Name, logo Scheduling for next month and December? How frequent? What does Doug want us to do by next meeting in 1-2 weeks? Get familiar with ISERink with Jeff How many VMs from Jen? Doug Continue to work w/Mike keep him in the loop roadmap of what is accomplished reach out and let him know what's happening December 2nd next meeting
0 Comments
Duration: 3 hr
Attendance: All but Kristin Clemons Agenda: - System Design Document Notes: - Discussed the content of what needs to go in the system design document - Worked on system design document Next Meeting Plan: - Possibly meet again if needed to complete system design document - Meet with advisor 10/28/15 at 9 AM Duration: 1 hr
Attendance: All but Kristin Clemons Agenda: - Logo - System Design Document - Web Application page layout Notes: - Discussed the look of the Logo (Font, Elements) - Discussed the content of what needs to go in the system design document - Discuseed layout of Web Application and the elements of the Web Application - Discussed obtaining a server to practice with ISERink - Obtaining ISERink NSF Grant documentation from advisor Next Meeting Plan: - Meet later this week to finish system design document (Thursday 10/22/15) - Schedule meeting with advisor Duration: 1.5 Hours Attendance: All
Notes
Meet with Adviser to discuss scope of project and expected deliverables, and obtain a more thorough understanding of the project. Duration: 1 Hour Attendance: All but Kristin Clemens
Agenda
Meet with Adviser to discuss scope of project and expected deliverables, and obtain a more thorough understanding of the project. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
RSS Feed