Add Shared Responsibility Model to Secure Cloud Architecture #1178
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jmanico
approved these changes
Aug 1, 2023
|
@utilimatt Would you be willing to review this? |
|
Looks like Matt may not be able to review. Any other folks y'all have for review? |
|
BOOM |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Content
This PR covers issue #1173. Added a section explaining the 3 main levels of the shared responsibility model, and made a small tweak to the self-managed tooling section to reflect the new section.
Review
One thing I would like a specific eye on is ensuring I have correctly explained/covered the nuances between the "as a Service" model and fully managed vs self-managed systems. There is significant overlap, but "as a Service" covers the differences from the developer and security responsibility set, and the levels of management refer to specific product groupings by cloud companies (ex: DynamoDB is "fully managed", but could be considered PaaS or SaaS).
Additionally, any suggestions for specific pros/cons in each section are welcome. It's hard to identify pros/cons in a provider agnostic manner.
@utilimatt Would you be willing to review this?
Thanks y'all!