-
Notifications
You must be signed in to change notification settings - Fork 27
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
Organization UseCase - Reduce IAM privileges scope of SysdigSecureForCloudRole #77
Comments
hey @Chili-Man, thanks for pointing that out. organizational setup is the most complicated one and we may need to clarify / pin permissions better. just updated the org example readme to clarify its usage better, but as stated, it's just the default suggestion.
let us know if we can clarify it better or got any better alternative suggestion |
@wideawakening I was just thinking/considering the same thing as OP and I would love if you could document a permission set that can be used to create a role for |
will be digging more into this topic soon. https://github.com/sysdiglabs/terraform-aws-secure-for-cloud#required-permissions |
I'm not sure why Sysdig Secure needs to have full admin access to every single AWS account to run the cloud-connector (for the organizational setup). Looking through the modules, it really doesn't seem that it needs access to everything, which is concerning since the ECS tasks assume this role. The principle of least privilege should be applied to this particular role and just scoped to the AWS IAM permissions it needs.
The text was updated successfully, but these errors were encountered: