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

Resource bound condition keys not understood #145

Open
0xdabbad00 opened this issue Aug 18, 2020 · 0 comments
Open

Resource bound condition keys not understood #145

0xdabbad00 opened this issue Aug 18, 2020 · 0 comments

Comments

@0xdabbad00
Copy link
Collaborator

The following policy is mentioned in https://aws.amazon.com/blogs/security/securing-resource-tags-used-for-authorization-using-service-control-policy-in-aws-organizations/

			"Sid": "DenyModifyTagsIfResAuthzTagAndPrinTagNotMatchedIam",
			"Effect": "Deny",
			"Action": [
				"iam:TagRole",
				"iam:TagUser",
				"iam:UntagRole",
				"iam:UntagUser"
			],
			"Resource": [
				"*"
			],
			"Condition": {
				"StringNotEquals": {
					"iam:ResourceTag/access-project": "${aws:PrincipalTag/access-project}",
					"aws:PrincipalArn": "arn:aws:iam::123456789012:role/org-admins/iam-admin"
				},
				"Null": {
					"iam:ResourceTag/access-project": false
				}
			}
		},

Parliament creates findings of Unknown condition for action - Unknown condition iam:ResourceTag/access-project for action iam:TagRole for each of the actions.

Looking at https://docs.aws.amazon.com/IAM/latest/UserGuide/list_identityandaccessmanagement.html the condition key iam:ResourceTag/${TagKey} is associated with the resource, not the action, and ends up not being understood by Parliament.

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

1 participant