Data Inventory
Table of Contents
Prisma Cloud Enterprise Edition
Expand all | Collapse all
-
- Prisma Cloud
- Prisma Cloud License Types
- Prisma Cloud—How it Works
- Get Prisma Cloud From the AWS Marketplace
- Get Prisma Cloud From the GCP Marketplace
- Access Prisma Cloud
- Prisma Cloud—First Look
- Prisma Cloud—Next Steps
- Enable Access to the Prisma Cloud Console
- Access the Prisma Cloud REST API
- Prisma Cloud FAQs
-
- Cloud Account Onboarding
-
- Onboard Your AWS Organization
- Onboard Your AWS Account
- Configure Audit Logs
- Configure Flow Logs
- Configure Data Security
- Configure DNS Logs
- Configure Findings
- Update an Onboarded AWS Organization
- Add AWS Member Accounts on Prisma Cloud
- Update an Onboarded AWS Account
- Update an Onboarded AWS Account to AWS Organization
- AWS APIs Ingested by Prisma Cloud
- Troubleshoot AWS Onboarding Errors
- Prisma Cloud on AWS China
- Manually Set Up Prisma Cloud Role for AWS Accounts
- Automate AWS Cloud Accounts Onboarding
-
- Connect your Azure Account
- Connect your Azure Tenant
- Connect an Azure Subscription
- Connect an Azure Active Directory Tenant
- Authorize Prisma Cloud to access Azure APIs
- Update Azure Application Permissions
- View and Edit a Connected Azure Account
- Troubleshoot Azure Account Onboarding
- Microsoft Azure API Ingestions and Required Permissions
-
- Prerequisites to Onboard GCP Organizations and Projects
- Onboard Your GCP Organization
- Onboard Your GCP Projects
- Flow Logs Compression on GCP
- Enable Flow Logs for GCP Organization
- Enable Flow Logs for GCP Project
- Update an Onboarded GCP Account
- Create a Service Account With a Custom Role
- GCP API Ingestions
- Cloud Service Provider Regions on Prisma Cloud
-
- Prisma Cloud Administrator Roles
- Create and Manage Account Groups on Prisma Cloud
- Create Prisma Cloud Roles
- Create Custom Prisma Cloud Roles
- Prisma Cloud Administrator Permissions
- Manage Roles in Prisma Cloud
- Add Administrative Users On Prisma Cloud
- Add Service Accounts On Prisma Cloud
- Create and Manage Access Keys
- Manage your Prisma Cloud Profile
-
- Get Started
- Set up ADFS SSO on Prisma Cloud
- Set up Azure AD SSO on Prisma Cloud
- Set up Google SSO on Prisma Cloud
- Set up Just-in-Time Provisioning on Google
- Set up Okta SSO on Prisma Cloud
- Set up Just-in-Time Provisioning on Okta
- Set up OneLogin SSO on Prisma Cloud
- Set up Just-in-Time Provisioning on OneLogin
- View and Forward Audit Logs
- Define Prisma Cloud Enterprise and Anomaly Settings
- Add a Resource List on Prisma Cloud
- Adoption Advisor
-
- Prisma Cloud Alerts and Notifications
- Trusted IP Addresses on Prisma Cloud
- Enable Prisma Cloud Alerts
- Create an Alert Rule for Run-Time Checks
- Configure Prisma Cloud to Automatically Remediate Alerts
- Send Prisma Cloud Alert Notifications to Third-Party Tools
- View and Respond to Prisma Cloud Alerts
- Suppress Alerts for Prisma Cloud Anomaly Policies
- Generate Reports on Prisma Cloud Alerts
- Alert Payload
- Prisma Cloud Alert Resolution Reasons
- Alert Notifications on State Change
- Create Views
-
- Prisma Cloud Integrations
- Integrate Prisma Cloud with Amazon GuardDuty
- Integrate Prisma Cloud with Amazon Inspector
- Integrate Prisma Cloud with Amazon S3
- Integrate Prisma Cloud with AWS Security Hub
- Integrate Prisma Cloud with Amazon SQS
- Integrate Prisma Cloud with Azure Service Bus Queue
- Integrate Prisma Cloud with Cortex XSOAR
- Integrate Prisma Cloud with Google Cloud Security Command Center (SCC)
- Integrate Prisma Cloud with Jira
- Integrate Prisma Cloud with Microsoft Teams
- Integrate Prisma Cloud with PagerDuty
- Integrate Prisma Cloud with Qualys
- Integrate Prisma Cloud with ServiceNow
- Integrate Prisma Cloud with Slack
- Integrate Prisma Cloud with Splunk
- Integrate Prisma Cloud with Tenable
- Integrate Prisma Cloud with Webhooks
- Prisma Cloud Integrations—Supported Capabilities
-
- What is Prisma Cloud IAM Security?
- Enable IAM Security
- Investigate IAM Incidents on Prisma Cloud
- Cloud Identity Inventory
- Create an IAM Policy
- Integrate Prisma Cloud with IdP Services
- Integrate Prisma Cloud with Okta
- Integrate Prisma Cloud with AWS IAM Identity Center
- Remediate Alerts for IAM Security
- Context Used to Calculate Effective Permissions
Data Inventory
The new Data Inventory ( ) provides information on the number of S3 storage buckets being monitored and summary data cards that provide status on how objects are exposed—public, sensitive, or malware, along with a detailed inventory view of objects across accounts, account groups, buckets and regions. It also provides a number of filters such as Time Range, Bucket Name, Bucket Exposure, Object Profile, Object Pattern to find the specific buckets or objects they are interested in.
Inventory
Data

- The Data Inventory page displays 6 data cards:
- Total Buckets
- Total number of buckets discovered in AWS (except empty buckets)
- Public Buckets
- Total number of buckets identified as public based on exposure
- Total Objects
- Total number of files discovered in buckets
- Public Objects
- Total objects with exposure public.
- Sensitive Objects
- Total number of objects containing sensitive data such as Financial Information, Healthcare, PII and Intellectual Property
- Malware Object
- Total number of objects identified by Wildfire as Malware. The Inventory table at the bottom of this page represents a hierarchical view of data grouped by account name, service name and region name. There are 4 views available on this table with the default view under cloud type followed by service name followed by bucket view followed by object view.* View 1 (Cloud View)
- View 2 (Service View)
- View 3 (Bucket View)
- View 4 (Object View)

The Object View above includes the following information
- Object Name
- Name of the file as discovered in the bucket
- Object Exposure
- Private, public, or conditional
- Data ProfileScanned content is classified under one of the following profiles: Financial Information, Healthcare, PII, or Intellectual Property. If an object belongs to any of the above categories, it is identified as sensitive data. The status of a scan can be one of the following:
- Scanning—Object is submitted successfully.
- Failed—Object could not be submitted for scanning.
- Not Sensitive—The object does not contain sensitive information for the data profiles and data patterns used to scan.
- Not Supported—File type is not supported for scanning. See Supported File Sizes and Types—Prisma Cloud Data Security.
- Too Large—File size is greater than 20MB.
- Data Patterns
- Data Profiles include one or more data patterns. For example, the PII data profile includes the Driver’s License #, SSN, Tax Identification Number, among other patterns.
- Snippet StatusDisplays the three states that your snippet scan can be in. In order to view the masked data your Snippet Status must showAvailable.
- Not Available—Indicates that theSnippet Maskingoption you selected has not been applied to your data. ClickGenerate Snippetsto apply the mask.
- In Progress—The state that Prisma Cloud be in after you clickGenerate Snippetsand are applying theMasking Optionto your sensitive data.
- Available—The masked data is ready to be viewed. ClickAvailableto view it.
- Snippet Last Scanned
- Provides details of when the scan last occurred.
- MalwareFor malware you can review the following information
- Malware Scan Timestamp—The time when Prisma Cloud received the verdict from WildFire.
- Malware Scan Status:
- Scanning—Object is submitted successfully.
- Failed—Object could not be submitted for scanning.
- Not Supported—File type is not supported for scanning. See Supported File Sizes and Types—Prisma Cloud Data Security.
- Too Large—File size is greater than 20MB.
- Scanned-Malware—The object is identified as malware.
- Scanned-Not Malware—The object is benign.
- User
- Owner of the object
- Bucket Name
- Name of the bucket that the object belongs to
- Account Name
- Name of the account that the object belongs to
- Region Name
- Name of the region that the object belongs to
- Service Name
- Name of cloud storage service (e.g. S3)
- Last Modified
- Object creation time or last updated time in S3.