docs(proof): security-baseline-new-accounts tested against a real org - #20
Merged
Merged
Conversation
Ran the member-baseline StackSet for real: applied via Terraform from the management account against a test OU, verified GuardDuty/Security Hub/Config came up in the target account, then tore it down and reverified everything was gone. Found and fixed two gaps the proof surfaced: - README's Prerequisites was missing cloudformation:ActivateOrganizations Access; CreateStackSet fails without it even with Organizations trusted access already enabled. - aws_cloudformation_stack_set_instance's region argument is deprecated in AWS provider v6; switched to stack_set_instance_region. See docs/PROOF.md for the claims/evidence table, what running it for real found, and what this run does not prove.
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.
Ran
member-baseline's StackSet for real against a real AWS Organization (management account applying to a test OU), verified GuardDuty/Security Hub/Config in the target member account via direct API reads (not just Terraform's output), then tore it down and reverified everything was gone.Two gaps the run surfaced, both fixed here:
CreateStackSetalso needscloudformation:ActivateOrganizationsAccessin the calling account, separate from the Organizations-side trusted access already documented. Failed withValidationError: You must enable organizations access to operate a service managed stack setuntil this was added.aws_cloudformation_stack_set_instance'sregionis deprecated in AWS provider v6; switched tostack_set_instance_region.Full claims/evidence table, what running it for real found, and what this run does not prove (new-account auto-deployment, multi-region, DELEGATED_ADMIN, GovCloud, failure/rollback, cost) is in
docs/PROOF.md, matching the format used inaws-orgseed's proof.