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

IAM Results mis-reporting role policies #154

Open
nmarchini opened this issue Jan 27, 2021 · 1 comment
Open

IAM Results mis-reporting role policies #154

nmarchini opened this issue Jan 27, 2021 · 1 comment

Comments

@nmarchini
Copy link

v0.2.5

I have run Cloudsplaining against an AWS account and the default.json contains one of the admin roles in the account. It shows that the following Attached Managed Policies are part of the Role.

"AttachedManagedPolicies": [
                {
                    "PolicyName": "AdministratorAccess",
                    "PolicyArn": "arn:aws:iam::aws:policy/AdministratorAccess"
                }
            ],

When I look at the iam-results-default.json document it shows the same role but reports that the role has no policies at all.

            "create_date": "2020-07-22 12:33:57+00:00",
            "role_last_used": "2021-01-21 10:43:07+00:00",
            "id": "XXXXXXXXXXXXXXXXXXXXX",
            "name": "XXXXXXXXX",
            "inline_policies": {},
            "instance_profiles": [],
            "instances_count": 0,
            "path": "/",
            "customer_managed_policies": {},
            "aws_managed_policies": {},
            "is_excluded": false

The result is that is shows in the output report as not being an issue even though is has full admin access to the account.

Screenshot 2021-01-26 at 22 34 21

@kmcquade
Copy link
Collaborator

@nmarchini - I included AdministratorAccess in the default exclusions config because otherwise it would slow things down. https://github.com/salesforce/cloudsplaining/blob/master/cloudsplaining/shared/default-exclusions.yml#L7. I recognize that's a gap. If that speed compromise is okay with you, I suggest in the meantime using a custom exclusions file and removing AdministratorAccess fro the exclusions list.

@verkaufer - perhaps this is a good opportunity for the escape hatch that we discussed?

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

No branches or pull requests

2 participants