Читать книгу Information Technology Security Risk Assessment A Complete Guide - 2020 Edition - Gerardus Blokdyk - Страница 8

Оглавление

CRITERION #2: DEFINE:

INTENT: Formulate the stakeholder problem. Define the problem, needs and objectives.

In my belief, the answer to this question is clearly defined:

5 Strongly Agree

4 Agree

3 Neutral

2 Disagree

1 Strongly Disagree

1. How will variation in the actual durations of each activity be dealt with to ensure that the expected Information technology security risk assessment results are met?

<--- Score

2. The political context: who holds power?

<--- Score

3. What knowledge or experience is required?

<--- Score

4. Are audit criteria, scope, frequency and methods defined?

<--- Score

5. What is the scope?

<--- Score

6. Are there different segments of customers?

<--- Score

7. What is in scope?

<--- Score

8. What information do you gather?

<--- Score

9. Is the Information technology security risk assessment scope complete and appropriately sized?

<--- Score

10. What system do you use for gathering Information technology security risk assessment information?

<--- Score

11. How do you catch Information technology security risk assessment definition inconsistencies?

<--- Score

12. Are resources adequate for the scope?

<--- Score

13. What would be the goal or target for a Information technology security risk assessment’s improvement team?

<--- Score

14. What scope to assess?

<--- Score

15. What is the definition of Information technology security risk assessment excellence?

<--- Score

16. How often are the team meetings?

<--- Score

17. Are the Information technology security risk assessment requirements complete?

<--- Score

18. What constraints exist that might impact the team?

<--- Score

19. What customer feedback methods were used to solicit their input?

<--- Score

20. Are task requirements clearly defined?

<--- Score

21. How was the ‘as is’ process map developed, reviewed, verified and validated?

<--- Score

22. What is out-of-scope initially?

<--- Score

23. Are the Information technology security risk assessment requirements testable?

<--- Score

24. Are all requirements met?

<--- Score

25. What is the scope of the Information technology security risk assessment work?

<--- Score

26. How does the Information technology security risk assessment manager ensure against scope creep?

<--- Score

27. What are the rough order estimates on cost savings/opportunities that Information technology security risk assessment brings?

<--- Score

28. Has/have the customer(s) been identified?

<--- Score

29. Scope of sensitive information?

<--- Score

30. When is the estimated completion date?

<--- Score

31. Do you all define Information technology security risk assessment in the same way?

<--- Score

32. Is the current ‘as is’ process being followed? If not, what are the discrepancies?

<--- Score

33. Why are you doing Information technology security risk assessment and what is the scope?

<--- Score

34. In what way can you redefine the criteria of choice clients have in your category in your favor?

<--- Score

35. What is in the scope and what is not in scope?

<--- Score

36. Has a Information technology security risk assessment requirement not been met?

<--- Score

37. Has your scope been defined?

<--- Score

38. What is the context?

<--- Score

39. How is the team tracking and documenting its work?

<--- Score

40. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?

<--- Score

41. Is the Information technology security risk assessment scope manageable?

<--- Score

42. When are meeting minutes sent out? Who is on the distribution list?

<--- Score

43. What gets examined?

<--- Score

44. What is out of scope?

<--- Score

45. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?

<--- Score

46. What are the requirements for audit information?

<--- Score

47. Does the scope remain the same?

<--- Score

48. Has the direction changed at all during the course of Information technology security risk assessment? If so, when did it change and why?

<--- Score

49. Is special Information technology security risk assessment user knowledge required?

<--- Score

50. How would you define Information technology security risk assessment leadership?

<--- Score

51. Have the customer needs been translated into specific, measurable requirements? How?

<--- Score

52. Have all of the relationships been defined properly?

<--- Score

53. How do you keep key subject matter experts in the loop?

<--- Score

54. If substitutes have been appointed, have they been briefed on the Information technology security risk assessment goals and received regular communications as to the progress to date?

<--- Score

55. Who are the Information technology security risk assessment improvement team members, including Management Leads and Coaches?

<--- Score

56. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?

<--- Score

57. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?

<--- Score

58. What critical content must be communicated – who, what, when, where, and how?

<--- Score

59. What sort of initial information to gather?

<--- Score

60. Do you have a Information technology security risk assessment success story or case study ready to tell and share?

<--- Score

61. What are the compelling stakeholder reasons for embarking on Information technology security risk assessment?

<--- Score

62. How have you defined all Information technology security risk assessment requirements first?

<--- Score

63. Are accountability and ownership for Information technology security risk assessment clearly defined?

<--- Score

64. What are the Information technology security risk assessment tasks and definitions?

<--- Score

65. Is it clearly defined in and to your organization what you do?

<--- Score

66. What specifically is the problem? Where does it occur? When does it occur? What is its extent?

<--- Score

67. How do you think the partners involved in Information technology security risk assessment would have defined success?

<--- Score

68. What are the record-keeping requirements of Information technology security risk assessment activities?

<--- Score

69. Does the team have regular meetings?

<--- Score

70. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?

<--- Score

71. What are the dynamics of the communication plan?

<--- Score

72. What is the scope of the Information technology security risk assessment effort?

<--- Score

73. What are the core elements of the Information technology security risk assessment business case?

<--- Score

74. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?

<--- Score

75. Have all basic functions of Information technology security risk assessment been defined?

<--- Score

76. Is the improvement team aware of the different versions of a process: what they think it is vs. what it actually is vs. what it should be vs. what it could be?

<--- Score

77. Has anyone else (internal or external to the group) attempted to solve this problem or a similar one before? If so, what knowledge can be leveraged from these previous efforts?

<--- Score

78. Do you have organizational privacy requirements?

<--- Score

79. Who approved the Information technology security risk assessment scope?

<--- Score

80. Has a project plan, Gantt chart, or similar been developed/completed?

<--- Score

81. Has a high-level ‘as is’ process map been completed, verified and validated?

<--- Score

82. How do you gather the stories?

<--- Score

83. What is the scope of Information technology security risk assessment?

<--- Score

84. Are there any constraints known that bear on the ability to perform Information technology security risk assessment work? How is the team addressing them?

<--- Score

85. What are (control) requirements for Information technology security risk assessment Information?

<--- Score

86. What sources do you use to gather information for a Information technology security risk assessment study?

<--- Score

87. What intelligence can you gather?

<--- Score

88. What is the worst case scenario?

<--- Score

89. How do you gather requirements?

<--- Score

90. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?

<--- Score

91. Who is gathering information?

<--- Score

92. Is Information technology security risk assessment required?

<--- Score

93. Is Information technology security risk assessment linked to key stakeholder goals and objectives?

<--- Score

94. How do you build the right business case?

<--- Score

95. Has the Information technology security risk assessment work been fairly and/or equitably divided and delegated among team members who are qualified and capable to perform the work? Has everyone contributed?

<--- Score

96. How do you manage changes in Information technology security risk assessment requirements?

<--- Score

97. Have specific policy objectives been defined?

<--- Score

98. Is there any additional Information technology security risk assessment definition of success?

<--- Score

99. What are the Information technology security risk assessment use cases?

<--- Score

100. Is there a clear Information technology security risk assessment case definition?

<--- Score

101. How and when will the baselines be defined?

<--- Score

102. Is there a critical path to deliver Information technology security risk assessment results?

<--- Score

103. Is scope creep really all bad news?

<--- Score

104. How do you manage scope?

<--- Score

105. Will a Information technology security risk assessment production readiness review be required?

<--- Score

106. What defines best in class?

<--- Score

107. Is Information technology security risk assessment currently on schedule according to the plan?

<--- Score

108. Has everyone on the team, including the team leaders, been properly trained?

<--- Score

109. Has a team charter been developed and communicated?

<--- Score

110. How did the Information technology security risk assessment manager receive input to the development of a Information technology security risk assessment improvement plan and the estimated completion dates/times of each activity?

<--- Score

111. Who is gathering Information technology security risk assessment information?

<--- Score

112. What Information technology security risk assessment services do you require?

<--- Score

113. How will the Information technology security risk assessment team and the group measure complete success of Information technology security risk assessment?

<--- Score

114. What was the context?

<--- Score

115. Who defines (or who defined) the rules and roles?

<--- Score

116. How are consistent Information technology security risk assessment definitions important?

<--- Score

117. Are different versions of process maps needed to account for the different types of inputs?

<--- Score

118. What are the boundaries of the scope? What is in bounds and what is not? What is the start point? What is the stop point?

<--- Score

119. How do you hand over Information technology security risk assessment context?

<--- Score

120. Is the scope of Information technology security risk assessment defined?

<--- Score

121. How would you define the culture at your organization, how susceptible is it to Information technology security risk assessment changes?

<--- Score

122. How do you manage unclear Information technology security risk assessment requirements?

<--- Score

123. What key stakeholder process output measure(s) does Information technology security risk assessment leverage and how?

<--- Score

124. What happens if Information technology security risk assessment’s scope changes?

<--- Score

125. Are roles and responsibilities formally defined?

<--- Score

126. What information should you gather?

<--- Score

127. What scope do you want your strategy to cover?

<--- Score

128. When is/was the Information technology security risk assessment start date?

<--- Score

129. Where can you gather more information?

<--- Score

130. How do you gather Information technology security risk assessment requirements?

<--- Score

131. Is the work to date meeting requirements?

<--- Score

132. What is a worst-case scenario for losses?

<--- Score

133. What baselines are required to be defined and managed?

<--- Score

134. Are required metrics defined, what are they?

<--- Score

Add up total points for this section: _____ = Total points for this section

Divided by: ______ (number of statements answered) = ______ Average score for this section

Transfer your score to the Information technology security risk assessment Index at the beginning of the Self-Assessment.

Information Technology Security Risk Assessment A Complete Guide - 2020 Edition

Подняться наверх