-
Notifications
You must be signed in to change notification settings - Fork 290
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
Assumable role for Cortex XSIAM #8111
Conversation
|
|
…rtex made uuid sensitive, stored account ID as ssm parameter aded checkov skip
e6dd5b0
to
d461ab3
Compare
|
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.
Looks good , lets give it a go!
A reference to the issue / Description of it
#7607
How does this PR fix the problem?
Creates an assumable role that can be used by Palo Alto Cortex XSIAM in line with their documented guidelines. I deliberately haven't attached the
Security Audit
managed policy as this isn't currently being used by the Cortex user, and provides access to the account which we may not prefer to offer.How has this been tested?
Tested with CI pipeline. I expect that this will fail because - at present - there is no value for the account ID SSM parameter. This will be added manually once the parameter has been created
Deployment Plan / Instructions
Deploy through CI. Potentially re-run after populating SSM parameter.
Checklist (check
x
in[ ]
of list items)Additional comments (if any)
{Please write here}