Closed josh-ho closed 4 years ago
Hi @josh-ho , the BFS tool is a defensive tool, so that role is actually the role you should have, not the role the starting service account should have. So grant yourself that role, and then point it at any service account you want as the --source
(the source does not need the analyze permission) and it will use your permissions to pull the permissions of the source and see if it's possible to move from the source to other identities through the permissions the source has
Also note that role you give yourself needs to be applied at the org level, not the project level
Oh I see, ok I'll try adding the role to myself first. Thanks
Just getting back, applying the role on my user account on the org resolved the issue. Thanks 👍 closing issue.
When trying to run
python bfs.py --org_id <orgId> --source <serviceAccountEmail>
the service account that I am using has thecloudasset.assets.analyzeIamPolicy
permission via theroles/cloudasset.viewer
role. I receive an error:After debugging I noticed that the google call to analyze the IAM Policy is returning a 403 error:
Request denied by Cloud IAM
Are there any other permissions that are needed on the service account to get it to work. Thanks