-
Notifications
You must be signed in to change notification settings - Fork 982
Not possible to enable Security Command Center Enterprise #2338
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
Comments
Just disable the policy, enable SCC Enterprise, then re-enable it. The policy is either on or off, and it should be on on a new install. |
@ludoo thanks for the quick answer! Is this procedure documented somewhere? How can I be sure nothing breaks after re-enabling it? Best regards, |
Organization policies are not retroactive, this is the usual (hacky) way of dealing with a temporary exception. Another way would be to add the SCC service account to one of your Cloud Identity groups (I personally have never tried this but it should work). I don't think there's explicit documentation for SCC, but temporary disablement is mention elsewhere in our documentation for similar use cases, AFAIR. |
okay, thank you! :) |
Thanks for flagging Markus, I'll leave this open so we can properly document it in our stage docs. |
Describe the bug
It looks like enabling SCC-E requires special handling for
allowed_policy_member_domains
. Using the recommended settings in FAST whereiam.allowedPolicyMemberDomains
is properly enforced, it is not possible to enable SCC-E. The activate button shows an error:To Reproduce
Try to Activate SCC-E when the framework is enforcing
iam.allowedPolicyMemberDomains
.Expected behavior
The framework should enable activating SCC-E using recommended security best practices.
Ideally, there are step-by-step instructions for the setup, and the framework includes the required Terraform code to allow organizations to fully utilize SCC-E.
Result
See previous image.
The text was updated successfully, but these errors were encountered: