Master this deck with 22 terms through effective study methods.
Generated from uploaded pdf
The immediate response involved initiating a covert project called Phoenix, led by German as the project manager, to address the security breach.
The high-level objectives included determining the extent of the intrusion and developing a remediation plan to address system deficiencies.
Going dark was necessary to turn off UVA's Internet connection for several days to allow rebuilt servers to come online, remove compromised accounts, and prevent attackers from moving to other systems.
German was responsible for managing the project team structure, leveraging Evans's support and experience in managing major IT projects.
Hogan cited the quote 'Failure is not an option' from Apollo 13 to underscore the critical nature of their mission.
A total of 176 people were involved in the Phoenix Project, making it challenging to maintain agility and secrecy.
New team members had to be sworn to secrecy before being briefed on the project, and all communication was conducted outside of UVA's systems using Google Gmail and Google Docs.
The meeting site was a repurposed vacant building situated in a relatively private area close to the main ITS offices.
The meeting facility functioned as a 'war room' equipped with all requisite technology, whiteboards, and a continuous supply of refreshments.
The first meeting was significant as it briefed team leaders on the mission's importance and set the tone for the project's urgency and seriousness.
The first decision was to schedule a go-dark phase to facilitate the remediation process.
The team leaders operated as a 'team of teams,' following a well-orchestrated plan and schedule while remaining agile to respond to new information.
Evans played a crucial role by providing support, managing the project, and ensuring that the team was organized and focused on the mission.
The large number of participants made it challenging to maintain both agility and secrecy, requiring strict protocols for communication and information sharing.
The preliminary investigation aimed to assess the intrusion's extent before the more in-depth assessment initiated by the Phoenix Project.
The ultimate goal of the remediation plan was to address system deficiencies and ensure the security of UVA's IT infrastructure.
The team ensured effective communication by using external tools like Google Gmail and Google Docs to prevent detection by attackers.
'Go-dark' referred to the decision to disconnect from the Internet to secure systems and prevent further intrusion during the remediation process.
Strategies included creating a structured project team, assigning team leads, and holding daily meetings to coordinate efforts and address challenges.
Being 'read-in' was important to ensure that team members were fully briefed on the project details while maintaining confidentiality and security.
Technology played a critical role in facilitating communication, collaboration, and project management, especially in a secure environment.
The project team adapted by maintaining agility in their operations, allowing them to respond quickly to emerging information and challenges.