Ch 10 - Implementing Information Security Flashcards
Story or Vignette
Change control meeting –> well-prepared project plan, feeling confident Kelvin Urich (he made sure to print enough handouts with the tasks/sub/and action items) –> meeting gets started (Naomi) walking the CC group through the items, smoothly –> then it gets time for Kelvin to present on the security updates plan. Once he is finished chaos erupts.
Kelvin Urich arrives at the empty conference room for the change control meeting. He is feeling confident that the project plan that he has created for the security updates is complete and well-ordered. Part of his confidence comes from the fact that the technical review committee members had approved his ideas the week prior.
In the handouts, he made sure to include the tasks, subtasks, action items, and had assigned dates to every action step and personnel to each required task.
Naomi (the change control supervisor) gets the meeting started by talking those present through each change control item up for discussion. Most items received the response “as planned”, but occasionally there someone answered either “cancelled” or “will be rescheduled”. But for the most part, she received the expected response.
Naomi then gets to items pertaining to security which Kelvin is going to brief the change control group on. Kelvin presents his plan and once he is done it’s time for comments or questions.
Instantly many hands are raised. And Kelvin realizes that many are technical analysts who had not been on the technical review committee that approved his plan. Additionally, he noticed that half the room were busy pulling calendars, and digital assistants.
People begin complaining about the workload being dumped on them and some comment they can’t make this happen on schedule. The meeting basically turns into chaos.
Learning Objectives
- How does an org’s info. security blueprint become a project plan?
- What considerations must a project plan address?
- What is the significance of a project manager’s role in the success of an information security project?
- Be able to describe the need for project management when it comes to complex projects
- Describe technical strategies and models for implementing a project plan
- Anticipate and mitigate the non-technical problems that orgs. face in times of rapid change.
Project plan aka
blueprint for information security
Work Breakdown Structure (WBS)
a planning tool that breaks down the project into its major tasks which are then further divided into smaller tasks or subtasks/ action steps.
In the WBS planning tool,
What are the attributes of the major tasks that are accounted for?
- Work to be accomplished (activities & deliverables)
- Individuals/Skill-set assigned to perform the task.
- Start and end dates for the task
- Amount of effort required (in hours or work days)
- Estimated capital expenses
- Estimated non-capital expenses
- Identification of dependencies between and among tasks
Projectitis
, wherein the project manager spends more time documenting project tasks, collecting performance measurements, recording project task information, and updating project completion forecasts than in accomplishing meaningful project work.
Deliverable
A deliverable is a completed document or program module that can either serve as the beginning point for a later task or become an element in the finished project
RFP
Request for proposal
resource
skill set or person, often called a resource, needed to accomplish the task
Milestone
A milestone is a specific point in the project plan when a task that has a noticeable impact on the progress of the project plan is complete.
Predecessors and successors (tasks/action steps)
Tasks or action steps that come before the specific task at hand are called predecessors, and those that come after the task at hand are called successors.
Project scope
Project scope describes the amount of time and effort-hours needed to deliver the planned features and quality level of the project deliverables
Project Planning Considerations
- Financial Considerations - CBA - Cost-Benefit Analysis
- Priority considerations
- Time and Scheduling Considerations
- Staffing Considerations
- Procurement Considerations
- Organizational Feasibility Considerations
- Training and Indoctrination Considerations
- Scope Considerations
The Need for Project Management
- Supervised Implementation - choose the leader and from which community of interest (IT, CISO, CIO)
- Executing the Plan - negative feedback or cybernetic loop - measures progress periodically, and corrective action is taken for deviations. (effort/money, scheduling impact, quality/quantity of deliverable).
- Project Wrap-up - a final report and a presentation. The goal of the wrap-up is to resolve any pending issues, critique the overall project effort, and draw conclusions about how to improve the process for the future.
Technical Aspects of Implementation
- Conversion Strategies
- Prioritization among multiple components
- Outsourcing
- Technology governance