ISOL 533 - Information Security and Risk Management University of the Cumberlands RISK ASSESSMENT PLAN EXECUTIVE SUMMARY RISKS – THREATS – WEAKNESSES WITHIN EACH DOMAIN COMPLIANCE LAWS AND REGULATIONS < Summarize your Compliance Laws and Regulations from your ‘Part-I Task-1’ Risk Management Plan > ISOL 533 - Information Security and Risk Management University of the Cumberlands R-T-W Risk: Threat: Weakness: Risk: Threat: Weakness: Risk: Threat: Weakness: Risk: Threat: Weakness: Risk: Threat: Weakness: Risk: Threat: Weakness: Risk: Threat: Weakness: Risk: Threat: Weakness: Risk: Threat: Weakness: Risk: Threat: Weakness: Risk: Threat: Weakness: Risk: Threat: Weakness: Risk: Threat: Weakness: Risk: Threat: Weakness: Risk: Threat: Weakness: Risk: Threat: Weakness: Table 1 RISK ASSESSMENT PLAN Domain Impacted Risk Impact / Factor ISOL 533 - Information Security and Risk Management University of the Cumberlands Figure 1 RISK ASSESSMENT PLAN Risk Assessment Checklist Category Risk Organizational Project lacks Executive-level Sponsor 1 Budget reduces team’s capacity 3 Management insist on decisions that lengthen schedule 5 Inefficient team structure reduces productivity 7 Review/decision cycle slower than expected 9 Vendor tasks take longer than expected 1 Hiring resources takes longer than expected 3 Work from a prior project not be completed on time 5 Low motivation reduces productivity 7 Lack of skills increases defects 9 Personnel with critical skills unavailable 1 Personnel need extra time to learn unfamiliar tools 3 Contractors leave before the project completion 5 Conflicts between team result in errors and extra rework 7 Facilities not be available on time 9 Facilities inadequate 1 Development tools may not be in place by the desired time 3 Development tools may not work as expected 5 Staff Development Environment Impact User Contractor External Schedule Learning curve for new tools longer than expected 7 User requirements are unstable 9 User review/decision cycles slower than expected 1 Users may not participate in review cycles 3 Users may not accept the end product 5 Users may have expectations than cannot be met 7 Contractor may not deliver work when promised 9 Contractor may deliver low quality products 1 Contractor may have other high-priority work 3 Product depends on government regulations 5 Product depends on draft technical standards 7 Specifications poorly defined 9 Additional requirements added 1 Error-prone modules may require more testing 3 Components may not be easily integrated 5 Schedule, resources, and product definition unclear 7 Schedule is over-optimistic 9 Schedule omits necessary tasks 1 Excessive schedule pressure may reduce productivity 3 Schedule includes several tasks that have multiple predecessors 5 Schedule includes milestones that have not been clearly defined 7 Likelihood 1 3 5 7 9 1 1 3 4 6 3 3 6 6 9 1 1 1 Difficulty of Detection 1 1 9 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7