Skip to content
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

ADA-CP 2.2.1: Ensure a support role has been created to manage incidents with AWS Support #1654

Open
rdegraaf opened this issue Jul 15, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@rdegraaf
Copy link

Is your feature request related to a problem? Please describe.

The App Defense Alliance Cloud Profile requires a check that an incident-management Role has been registered with AWS Support.

Describe the solution you'd like

Implement the check documented at https://github.com/appdefensealliance/ASA-WG/blob/main/Cloud%20App%20and%20Config%20Profile/Cloud%20App%20and%20Config%20Test%20Guide.md#221-ensure-a-support-role-has-been-created-to-manage-incidents-with-aws-support.

Describe alternatives you've considered

None.

Additional context

@rdegraaf rdegraaf added the enhancement New feature or request label Jul 15, 2024
@rdegraaf
Copy link
Author

Looks like there is already such a rule ("iam-no-support-role") in the "detailed" ruleset, but:

  1. It doesn't work. The rule is not triggered on an account that does not have the AWSSupportAccess permission policy attached to anything -- presumably because ScoutSuite only enumerates AWS-managed permission policies when they are attached to something within the account.
  2. It only requires that the permission policy be attached to something, as opposed to specifically a Role as is required by CIS and ADA.

@rdegraaf
Copy link
Author

Fixed in https://github.com/rdegraaf/ScoutSuite/tree/ada-cp-aws. MR to come once I have a few more rules implemented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant