LINT.IfChange
Keep in sync with
logs/proto/cloud_asset_inventory/iam_policy_analyzer_log.proto
IAM policy analysis query message.
JSON representation | |
---|---|
{ "scope": string, "resourceSelector": { object ( |
Fields | |
---|---|
scope |
Required. The relative name of the root asset. Only resources and IAM policies within the scope will be analyzed. This can only be an organization number (such as "organizations/123"), a folder number (such as "folders/123"), a project ID (such as "projects/my-project-id"), or a project number (such as "projects/12345"). To know how to get organization id, visit here . To know how to get folder or project id, visit here . |
resourceSelector |
Optional. Specifies a resource for analysis. |
identitySelector |
Optional. Specifies an identity for analysis. |
accessSelector |
Optional. Specifies roles or permissions for analysis. This is optional. |
options |
Optional. The query options. |
ResourceSelector
Specifies the resource to analyze for access policies, which may be set directly on the resource, or on ancestors such as organizations, folders or projects.
JSON representation | |
---|---|
{ "fullResourceName": string } |
Fields | |
---|---|
fullResourceName |
Required. The full resource name of a resource of supported resource types. |
IdentitySelector
Specifies an identity for which to determine resource access, based on roles assigned either directly to them or to the groups they belong to, directly or indirectly.
JSON representation | |
---|---|
{ "identity": string } |
Fields | |
---|---|
identity |
Required. The identity appear in the form of members in IAM policy binding. The examples of supported forms are: "user:mike@example.com", "group:admins@example.com", "domain:google.com", "serviceAccount:my-project-id@appspot.gserviceaccount.com". Notice that wildcard characters (such as * and ?) are not supported. You must give a specific identity. |
AccessSelector
Specifies roles and/or permissions to analyze, to determine both the identities possessing them and the resources they control. If multiple values are specified, results will include roles or permissions matching any of them. The total number of roles and permissions should be equal or less than 10.
JSON representation | |
---|---|
{ "roles": [ string ], "permissions": [ string ] } |
Fields | |
---|---|
roles[] |
Optional. The roles to appear in result. |
permissions[] |
Optional. The permissions to appear in result. |
Options
Contains query options.
JSON representation | |
---|---|
{ "expandGroups": boolean, "expandRoles": boolean, "expandResources": boolean, "outputResourceEdges": boolean, "outputGroupEdges": boolean, "analyzeServiceAccountImpersonation": boolean } |
Fields | |
---|---|
expandGroups |
Optional. If true, the identities section of the result will expand any Google groups appearing in an IAM policy binding. If Default is false. |
expandRoles |
Optional. If true, the access section of result will expand any roles appearing in IAM policy bindings to include their permissions. If Default is false. |
expandResources |
Optional. If true and For example, if the request analyzes for which resources user A has permission P, and the results include an IAM policy with P on a GCP folder, the results will also include resources in that folder with permission P. If true and For example, if the request analyzes for which users have permission P on a GCP project with this option enabled, the results will include all users who have permission P on that project or any lower resource. Default is false. |
outputResourceEdges |
Optional. If true, the result will output resource edges, starting from the policy attached resource, to any expanded resources. Default is false. |
outputGroupEdges |
Optional. If true, the result will output group identity edges, starting from the binding's group members, to any expanded identities. Default is false. |
analyzeServiceAccountImpersonation |
Optional. If true, the response will include access analysis from identities to resources via service account impersonation. This is a very expensive operation, because many derived queries will be executed. We highly recommend you use For example, if the request analyzes for which resources user A has permission P, and there's an IAM policy states user A has iam.serviceAccounts.getAccessToken permission to a service account SA, and there's another IAM policy states service account SA has permission P to a GCP folder F, then user A potentially has access to the GCP folder F. And those advanced analysis results will be included in Another example, if the request analyzes for who has permission P to a GCP folder F, and there's an IAM policy states user A has iam.serviceAccounts.actAs permission to a service account SA, and there's another IAM policy states service account SA has permission P to the GCP folder F, then user A potentially has access to the GCP folder F. And those advanced analysis results will be included in Default is false. |