Cloud Incident Response

• • This document will serve as a base directory for the incident response. Will tell 'What' needs to be done and not the 'How' part. Significant 'How' part will be stated as a reference to another document or as an Appendix. Very strategic framework level for the main document.
  • We can include non-IT security events but not on the BCDR aspect. We can give insights on the security incident related causes 
  • The co-chairs & members decided to stick to the current scope  in the framework. 
  • Need to be aligned with other documents from CSA - such as Guidance v4, CCM
  • Suggestions to include new areas - can be done in phase 2 and details can be added as appendix.
  • Target to complete the document by 22 Feb so that it can be sent out for copyediting & publication (to be released in first week of April)

• Michael Roza will target to resolve maximum comments and try to complete the document this weekend. 
• Ricci to do a write-up on the expectations of CSC from CSP under the Preparation Phase. (This is to help new CSC to know what to ask from CSP and also for CSP to provide for CIR.)
• To schedule another meeting at 3/ 4 pm SGT in two weeks' time. 

• • This document will serve as a base directory for the incident response. Will tell 'What' needs to be done and not the 'How' part. Significant 'How' part will be stated as a reference to another document or as an Appendix. Very strategic framework level for the main document.
  • We can include non-IT security events but not on the BCDR aspect. We can give insights on the security incident related causes 
  • The co-chairs & members decided to stick to the current scope  in the framework. 
  • Need to be aligned with other documents from CSA - such as Guidance v4, CCM
  • Suggestions to include new areas - can be done in phase 2 and details can be added as appendix.
  • Target to complete the document by 22 Feb so that it can be sent out for copyediting & publication (to be released in first week of April)

• Michael Roza will target to resolve maximum comments and try to complete the document this weekend. 
• Ricci to do a write-up on the expectations of CSC from CSP under the Preparation Phase. (This is to help new CSC to know what to ask from CSP and also for CSP to provide for CIR.)
• To schedule another meeting at 3/ 4 pm SGT in two weeks' time. 

• • This document will serve as a base directory for the incident response. Will tell 'What' needs to be done and not the 'How' part. Significant 'How' part will be stated as a reference to another document or as an Appendix. Very strategic framework level for the main document.
  • We can include non-IT security events but not on the BCDR aspect. We can give insights on the security incident related causes 
  • The co-chairs & members decided to stick to the current scope  in the framework. 
  • Need to be aligned with other documents from CSA - such as Guidance v4, CCM
  • Suggestions to include new areas - can be done in phase 2 and details can be added as appendix.
  • Target to complete the document by 22 Feb so that it can be sent out for copyediting & publication (to be released in first week of April)

• Michael Roza will target to resolve maximum comments and try to complete the document this weekend. 
• Ricci to do a write-up on the expectations of CSC from CSP under the Preparation Phase. (This is to help new CSC to know what to ask from CSP and also for CSP to provide for CIR.)
• To schedule another meeting at 3/ 4 pm SGT in two weeks' time. 

• • This document will serve as a base directory for the incident response. Will tell 'What' needs to be done and not the 'How' part. Significant 'How' part will be stated as a reference to another document or as an Appendix. Very strategic framework level for the main document.
  • We can include non-IT security events but not on the BCDR aspect. We can give insights on the security incident related causes 
  • The co-chairs & members decided to stick to the current scope  in the framework. 
  • Need to be aligned with other documents from CSA - such as Guidance v4, CCM
  • Suggestions to include new areas - can be done in phase 2 and details can be added as appendix.
  • Target to complete the document by 22 Feb so that it can be sent out for copyediting & publication (to be released in first week of April)

• Michael Roza will target to resolve maximum comments and try to complete the document this weekend. 
• Ricci to do a write-up on the expectations of CSC from CSP under the Preparation Phase. (This is to help new CSC to know what to ask from CSP and also for CSP to provide for CIR.)
• To schedule another meeting at 3/ 4 pm SGT in two weeks' time. 

• • This document will serve as a base directory for the incident response. Will tell 'What' needs to be done and not the 'How' part. Significant 'How' part will be stated as a reference to another document or as an Appendix. Very strategic framework level for the main document.
  • We can include non-IT security events but not on the BCDR aspect. We can give insights on the security incident related causes 
  • The co-chairs & members decided to stick to the current scope  in the framework. 
  • Need to be aligned with other documents from CSA - such as Guidance v4, CCM
  • Suggestions to include new areas - can be done in phase 2 and details can be added as appendix.
  • Target to complete the document by 22 Feb so that it can be sent out for copyediting & publication (to be released in first week of April)

• Michael Roza will target to resolve maximum comments and try to complete the document this weekend. 
• Ricci to do a write-up on the expectations of CSC from CSP under the Preparation Phase. (This is to help new CSC to know what to ask from CSP and also for CSP to provide for CIR.)
• To schedule another meeting at 3/ 4 pm SGT in two weeks' time. 

• • This document will serve as a base directory for the incident response. Will tell 'What' needs to be done and not the 'How' part. Significant 'How' part will be stated as a reference to another document or as an Appendix. Very strategic framework level for the main document.
  • We can include non-IT security events but not on the BCDR aspect. We can give insights on the security incident related causes 
  • The co-chairs & members decided to stick to the current scope  in the framework. 
  • Need to be aligned with other documents from CSA - such as Guidance v4, CCM
  • Suggestions to include new areas - can be done in phase 2 and details can be added as appendix.
  • Target to complete the document by 22 Feb so that it can be sent out for copyediting & publication (to be released in first week of April)

• Michael Roza will target to resolve maximum comments and try to complete the document this weekend. 
• Ricci to do a write-up on the expectations of CSC from CSP under the Preparation Phase. (This is to help new CSC to know what to ask from CSP and also for CSP to provide for CIR.)
• To schedule another meeting at 3/ 4 pm SGT in two weeks' time. 

Hi Michael,

Thank you for your updates to the document.

I'll run through the document and update/add wherever I can (5.1 until 6.0).

• • This document will serve as a base directory for the incident response. Will tell 'What' needs to be done and not the 'How' part. Significant 'How' part will be stated as a reference to another document or as an Appendix. Very strategic framework level for the main document.
  • We can include non-IT security events but not on the BCDR aspect. We can give insights on the security incident related causes 
  • The co-chairs & members decided to stick to the current scope  in the framework. 
  • Need to be aligned with other documents from CSA - such as Guidance v4, CCM
  • Suggestions to include new areas - can be done in phase 2 and details can be added as appendix.
  • Target to complete the document by 22 Feb so that it can be sent out for copyediting & publication (to be released in first week of April)

• Michael Roza will target to resolve maximum comments and try to complete the document this weekend. 
• Ricci to do a write-up on the expectations of CSC from CSP under the Preparation Phase. (This is to help new CSC to know what to ask from CSP and also for CSP to provide for CIR.)
• To schedule another meeting at 3/ 4 pm SGT in two weeks' time.