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

New Edges: AWS Glue and DataPipeline #96

Open
ncc-erik-steringer opened this issue Sep 13, 2021 · 0 comments
Open

New Edges: AWS Glue and DataPipeline #96

ncc-erik-steringer opened this issue Sep 13, 2021 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@ncc-erik-steringer
Copy link
Collaborator

Pulling in some lessons learned from the "iam-vulnerable" project: https://github.com/BishopFox/iam-vulnerable .

TODO:

  1. Apply the following Terraform files and verify the noted permission combinations lead to Edges.
    1. https://github.com/BishopFox/iam-vulnerable/blob/main/modules/free-resources/privesc-paths/privesc18-PassExistingRoleToNewGlueDevEndpoint.tf
    2. https://github.com/BishopFox/iam-vulnerable/blob/main/modules/free-resources/privesc-paths/privesc19-UpdateExistingGlueDevEndpoint.tf
    3. https://github.com/BishopFox/iam-vulnerable/blob/main/modules/free-resources/privesc-paths/privesc21-PassExistingRoleToNewDataPipeline.tf
  2. Create a new edge checker object for Glue and for DataPipeline, maintaining with/without connectivity separation as in LambdaEdgeChecker when appropriate.
@ncc-erik-steringer ncc-erik-steringer added the enhancement New feature or request label Sep 13, 2021
@ncc-erik-steringer ncc-erik-steringer self-assigned this Sep 13, 2021
wdahlenburg pushed a commit to wdahlenburg/PMapper that referenced this issue Sep 5, 2022
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