Private Cloud Emergency Response

Private Cloud Emergency Response

In your infrastructure, there could be some critical issues that should resolve as soon as possible, because these issues could have negative effect on production, operation, organization, etc. They could call as emergency situation that should response in shortest time and should prepare for these scenarios. Some examples of these are:

  • Security incidents such as 0-day vulnerability, malware outbreak, hacking, etc.
  • Software failure, including operating system failure, application failure, etc.
  • Hardware failure, including hardware breakdown, external issues cause hardware failure.
  • Communication failure, between main server and other servers in different branches.
  • Natural disasters such as earth quick, flood, etc.

You could think of any other example that would put your organization in critical stage. When you build your private cloud, you have to think about these cases and prepare for response to emergency incidents. This could call as Private Cloud Emergency Response.

You could assign special group for this case or just train your IT team to prepare for this. Having a good emergency response planning would help you to back things to normal quickly, if it was case of emergency incidents.

These are phases that suggest getting emergency response team to be prepared:

1)Private Cloud Assessment: In this phase, you will look into your organizations’ structure and your private cloud configuration. Then you should get detail information of configuration and connection of all clients and servers, security and access rights, physical location of clients and servers and everything that helps you to understand your private cloud. These information will use in planning phase.


2)Emergency Cloud Planning: In this phase you should look into all possible incidents that could occur in your organization. Everything that would cause a significant effect in your organization and is related to private cloud configuration. Some example:


  • Due to earth quick in head quarter, all communication between servers in branches could cut off.
  • Some servers and PCs get into fire and data been lost.
  • The main server shutdown due to malware and other servers couldn’t work correctly due to that.

 These are example of some incidents that would affect majority or entire organization. You have to list down all possible cases and then list down possible responses for them.

3)Emergency Cloud Response: After you look into possible incidents, then you should think about response to those incidents. These responses should be quick and feasible. Some example of these responses:


  • Look for alternative communication solutions and also configure servers to be able to operate as standalone in case of communicate cut off.
  • Always backup data in multiple locations and get ready to restore them when they needed.
  • Consider to have alternative servers and configure fail over clusters that if main server or other servers been shutdown, they could operate temporary.


Always consider to review your incident and responses regularly and discuss with management, employee and other people in your organization to improve your list. And also train people to apply those responses in case of incident.



Leave a Comment
  • Please add 7 and 6 and type the answer here:
  • Post
Wiki - Revision Comment List(Revision Comment)
Page 1 of 1 (1 items)
Wikis - Comment List
Posting comments is temporarily disabled until 10:00am PST on Saturday, December 14th. Thank you for your patience.
Page 1 of 1 (2 items)