📄 AWS compensating controls V2#40
Draft
JFWooten4 wants to merge 1 commit into
Draft
Conversation
github-project-automation
Bot
moved this to To Draft
in Regulation S-P: File No. S7-05-23 Adoption
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This extends #14 with a standalone page for all vendors, pending addressing classification after blocktransfer/website#9. AWS is the main one and only, provided success in
177942530200190after #18 (comment).They have very thorough public documentation of security controls, which I think will be fine to reference in general for completion of 17 CFR § 248.30(a)(5)(i)(A).