question archive Shared Responsibility Model According to the AWS Shared Responsibility Model, you are responsible for the security and reliability of any data or applications you run on the AWS infrastructure
Subject:WritingPrice:2.86 Bought7
Shared Responsibility Model
According to the AWS Shared Responsibility Model, you are responsible for the security and reliability of any data or applications you run on the AWS infrastructure.
Reflect on the model, describe it and then discuss the pros and cons of a Shared Responsibility Model.
Reflect on the model and describe it:
The AWS Shared Responsibility Model describes how the various responsibilities are divided between the client and the Amazon. In this model it is defined as the Amazon is responsible for protecting the infrastructure that run all the services that include the software, hardware and other requirements that are being used for running the infrastructure and security features. In this model, it is also defined that the user is responsible for the security in the cloud based on the configuration the user chooses because it is the user who decide how they want to protect the data and how the data will be used for their benefit. According to that, the user is prompted about the security features and the security protocols where the user is responsible for the security and management task by managing their configuration work.
PROS:
1. It promotes the understanding of the best practices and standards between both the provider and its customers.
2. Services can be managed based on policies and the best possible technology present in the industry.
3. It becomes easier to set up a positional access system since the provider would have already set up such system that can be configured to suit the needs of the customer.
4. It promotes an all-in approach where everybody has to play a part in maintaining the security that prevents all possible forms of shortcomings. The customer can train its employees while the company can adjust its security system to suit their needs.
CONS:
1. Different vendors can have a slightly different approach or policies to this and therefore, the consideration for undressing each difference exists.
2. Since the approach is all-in it can also mean that there would either be a tight access control which might create problems in the future or on the other end of the spectrum, nothing would mean that all of the data is available to all the individuals connected to the customer's network at all times, which will not be an ideal situation.
3. The cost of maintaining the shared system has to be borne by the customers where they need to train their employees to better interact with the systems in place to prevent any leaks based on human error, as much as possible.