> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/content-collections/administration/configure-iam-security/investigate-iam-incidents-on-prisma-cloud.md).
# IAM Investigations on Prisma Cloud
Prisma Cloud ingests various services and associated user data from AWS, Azure, and GCP that you can leverage to investigate the relationships between the entities in your cloud environments and the permissions that allow access to your cloud assets. **Investigate** view enables you to use [permissions queries](https://github.com/PaloAltoNetworks/pc-docs-md/tree/main/enterprise-edition/content-collections/search-and-investigate/permissions-queries/permissions-queries.md) to trace the interconnections, visualize how the permissions are granted, know what actions are allowed and when the permissions were used, so that you can discover over-privileged accounts and assess the access risk across multi-cloud deployments. You can view results of the query in a graph view or a table view.
The graphical view provides a high-level overview of the different permissions or scope of access granted to cloud identities, and see the relationship between the Source, Granter, and Destination. You can use this view to modify your RQL query and find answers to who has access, to what, and how it is granted or inherited.
When you have narrowed the permissions (IAM) query, the tabular view provides more granular details to help you track and resolve identity and access challenges.
1. Select **Investigate > Search**.
2. Select **Permissions** from **Query Type** dropdown and enter a permissions query.
For example, query `config from iam where source.public = true AND dest.cloud.service.name = 'S3' AND dest.cloud.resource.type = 'bucket'` checks for S3 buckets in your account that are accessible from the Internet.
3. Select the **Table** (default) view.
* **Source**—Asset with permissions such as IAM user, IDP user, EC2 instance, Microsoft Compute Virtual Machine, and Lambda function.
* **Granted By**—Group, role, or policy that grants permissions to the source to interact with the destination.
* **Cloud Account(s)**—The cloud account and region associated with the IAM entity.
* **Action**—The operations that the entity can perform, based on the permissions granted.
* **Destination**—Cloud assets that had an action occur on it, or is the target of the action.
* **Last Access**—This is a proprietary algorithm that is calculated in two steps. It step one, it combines services from various cloud entities such as users, service accounts, groups, roles, and binding to compute the net effective permissions of cloud types. In step two, it then matches the actual usage (last access) to show when the permission was actually used.
* **Actions**—JSON associated with the query. The JSON displays the list of permissions available for the IAM user; this is the snippet of the asset configuration as defined in the cloud service.
For each result, select the icon under the **Actions** column to **View Permission Details** as a JSON snippet from the asset configuration.
To analyze your permissions offline, download the permissions details in a CSV format by clicking **Download**.
4. You can also view as **Graph**.
5. **Save** your query.
You can choose to save the searches that you have created for investigating incidents in **My Saved Searches** and use the queries to create a custom policy.
## Graph View Components
Graph View includes three columns—Sources, Granters, and Destination as shown in the image below.
Each column includes a container that nests the services or entities that belong to the specific container. You can drill down a logical container to see the list of identities included within. Containers are comprised of the following categories:
* **Sources**—Groups the Service Type logical containers.
The following table lists the standard service types for each Cloud Service Provider. The list is dynamic and varies according to the data available and ingested for your environment.
| **CSP** | **Service Types** |
| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **AWS** |
Lambda ECS Elasticbeanstalk IAM - includes AWS users STS EC2 Azure AD (IDP) Okta (IDP)
|
| **Azure** |
Azure Active Directory - Azure users (also includes Okta)
NOTE: The Okta service replicates Okta users into Azure AD, as a resultyou cannot view Okta users separately on Prisma Cloud IAM Security.
|
* **Granters**—Groups the Entity Type logical containers.
The following table lists the standard entity types for each cloud service provider. The list is dynamic and varies according to the data available and ingested for your environment.
| **CSP** | **Entity Types** |
| --------- | -------------------------------------------------------------------------------------------------------------------- |
| **AWS** |
Role Group Direct— User Resource—Resource-based permissions (granted by resource-based policies)
|
| **Azure** |
Direct— User User Assigned System Assigned Group
|
| **GCP** |
Direct— User Service Account Group
|
* **Destination**—Groups the Service Type logical containers. Similar to the source, the list of destinations vary based on your environment.
Graph View includes the following limitations:
* The RQL attribute **action.lastaccess.days**.
* The Destinations column is limited to 300 entries. If your query returns more than 300 results for the Destination, filter your results to 300.
* Queries time out after 1 minute.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.prismacloud.io/content-collections/administration/configure-iam-security/investigate-iam-incidents-on-prisma-cloud.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.