-
-
Notifications
You must be signed in to change notification settings - Fork 42
Update the CIS AWS guide for version 1.3.0 #392
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Deploy preview for keen-clarke-470db9 ready! Built with commit 6e2d196 |
|
Great start @infraredgirl 🎉 I've added some bits to the sections you mentioned me in for the |
infraredgirl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, thanks @ina-stoyanova. Looks great, I added a couple of comments too.
|
Just pushed the 5.1 related documentation at 8dd1d15 |
|
This section is really long now: https://github.com/gruntwork-io/gruntwork-io.github.io/blob/ca410b41956807bc9f2cb1b71c9fbe2f839eb1ef/_posts/2019-10-17-how-to-achieve-cis-benchmark-compliance.adoc#deployment-walkthrough I wonder if it would help to have a mini-TOC right here, under this header with all the subsections linked? Also wanted to say, this is looking great! |
Co-authored-by: rho <13165182+rhoboat@users.noreply.github.com>
@rhoboat Similar to my other point, do you think the left side-bar negates the need for an additional ToC? |
|
I've added a few new comments. Aside from the feedback, it looks like the traceability matrix is the last thing to complete and then we're done. |
Co-authored-by: Rob Morgan <robbym@gmail.com>
|
I believe we are ready to open this up for approvals! |
| link:https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/tree/master/modules/vpc-app-network-acls[`vpc-app-network-acls` | ||
| module] and your NACL Rules for the VPC-Mgmt (which is being deprecated) using the | ||
| link:https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/tree/master/modules/vpc-mgmt-network-acls[`vpc-mgmt-network-acls` | ||
| module]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code examples plz!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@brikis98 @marinalimeira This one is a bit tricky... For the code examples, we need to:
- Possibly link to this section: https://www.gruntwork.io/guides/compliance/how-to-achieve-cis-benchmark-compliance/#wrapper_modules
- Explain how we extend the
vpc-appandvpc-mgmtmodules by creating new ones ininfrastructure-modules. - Explain how in the new
vpc-appandvpc-mgmtmodules we need to invoke thevpc-mgmt-network-aclsmodule. - Explain how to create a
terragrunt.hclfile that invokes our new VPC modules ininfrastructure-modules.
Is there an easier way to do this? Could we just do the last step?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the real solution is to add a VPC service to the CIS Service Catalog, which would include vpc-app and vpc-app-network-acls, and deploy that with one terragrunt.hcl. We have the ticket for this already: https://gruntwork.atlassian.net/browse/IAC-1643... But it's not part of the CIS v1.3 project.
So I guess it's a trade-off between:
- Updating this guide with a bunch of steps that will take some time to put together and will be deprecated soon.
- Doing the VPC service work now, and updating the guide to use that. But note that the VPC service would have to extend the existing VPC service in
terraform-aws-service-catalog, and not all our CIS customers have access to that yet, so that would be yet another yak to shave. - Doing some minimal version of (1). That is, we say vaguely something like, "You should use the
vpc-app-network-aclsmodule to meet the new CIS v1.3 requirements. Check out our VPC guide for how to deploy a VPC with thevpc-appmodule. Once that's deployed, add thevpc-app-network-aclsmodule as follows: . Deploy all this using Terragrunt: ."
It's not ideal, but (3) is probably the way to go, and we'll replace it fairly soon when the CIS Service Catalog work is done.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure if I am following... What is the difference between (2) and the cis-infra-live-acme + cis-infra-modules?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The old way:
- Customer has an
infra-modulesrepo with a bunch of Terraform code in it. - Customers'
infra-liverepo sets thesourceURL to their owninfra-modulesrepo.
The new way:
- Gruntwork has an
service-catalogrepo with a bunch of Terraform code in it. - Customers'
infra-liverepo sets thesourceURL to Gruntwork'sservice-catalogrepo.
The CIS Service Catalog project is moving us to the new way for CIS... But we're not there yet. So we're trying to decide if we want to do the work of showing customers the "old way" for this VPC NACL stuff, only to throw it away a little later (option 1)... Or if we can go straight to the new way (option 2). Or some minimal version of the old way, as a placeholder until we finish the Service Catalog stuff (option 3).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd vouch with respect for time and simplicity, that we go with the old way. And then as part of CIS Service Catalog work, we come back here to update this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I went to the Updating this guide with a bunch of steps that will take some time to put together and will be deprecated soon. direction!
Co-authored-by: Yevgeniy Brikman <brikis98@users.noreply.github.com>
- Use NOTE block to point to the upgrade guide - Link to appropriate deployment walkthrough sections instead of private repos - Add link to the s3-bucket service as usage example of private-s3-bucket module
brikis98
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, some minor wording / typo issues to fix, and this is good to go!
| To enable IAM Access Analyzer in your AWS Account or Organization, you need to do it separately for every region. | ||
|
|
||
| To enable this for your AWS account: | ||
| * use the examples provided as part of `learning-and-testing/landingzone`: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NIT: This * is not rendering as a bullet point: https://deploy-preview-392--keen-clarke-470db9.netlify.app/guides/compliance/how-to-achieve-cis-benchmark-compliance/#iam_access_analyzer_deployment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, this whole sentence should be removed, as CIS customers should NOT be using the acccount-baseline modules, as those don't take into account CIS requirements. Instead, they should solely use the iam-access-analyzer module as shown below.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ahaa! noted!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removed :) good shout!
brikis98
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ship it!
|
Thanks Jim! |
https://gruntwork.atlassian.net/browse/IAC-1605
Remaining work: