1. Home
    2. Prisma
    3. Prisma Cloud
    4. Prisma Cloud Compute Edition Administrator’s Guide
    5. Compliance
    6. Cloud discovery

    Cloud discovery

    It’s difficult to ensure that all your apps running on all the different types of cloud services are being properly secured. If you’re using multiple cloud platforms, you might have many separate accounts per platform. You could easily have hundreds of combinations of providers, accounts, and regions where cloud native services are being deployed.
    Cloud Platforms discovery helps you find all cloud-native services being used in AWS, Azure, and Google Cloud, across all regions, and across all accounts. Cloud Provider discovery continuously monitors these accounts, detects when new services are added, and reports which services are unprotected. It can help mitigate your exposure to rogue deployments, abandoned environments, and sprawl.
    Cloud Platforms discovery offers coverage for the following services.
    Registries:
    • AWS
    • Azure
    • Google Cloud
    Serverless functions:
    • AWS
    • Azure
    • Google Cloud
    1
    Managed platforms:
    • AWS ECS
    • AWS EKS
    • Azure Kubernetes Service (AKS)
    • Azure Container Instances (ACI)
    • Google Kubernetes Engine (GKE)
    Virtual machines:
    • AWS EC2 instances
    • Azure VMs
      1
    • Google Cloud Platform (GCP) Compute Engine VM instances
      1
    1
    Auto-defend is currently not yet available for these services. Auto-defend utilizes rule-based policies to automatically deploy Prisma Cloud to protect resources in your environment.

    Minimum permissions

    Prisma Cloud needs one set of minimum permissions to discover and itemize all the resources in your account. After finding those resources, Prisma Cloud typically needs an additional set of permissions to protect them (e.g. retrieve those resources and inspect them for vulnerabilities and compliance issues.
    For example, the service account for cloud discovery uses the ecr:DescribeRepositories permission to list all ECR repositories in your AWS accounts. If you find a repository that’s not being scanned, and you want to configure Prisma Cloud to scan it, Prisma Cloud needs another service account with deeper permissions that lets it auth with the ECR service and download images from the repository (e.g., ecr:GetAuthorizationToken, ecr:BatchGetImage, etc). The permissions required for cloud discovery to scan your accounts are documented here. Permissions required to enable protection (e.g. scanning a repo) are documented in each protection feature’s respective article.

    AWS

    For AWS, Prisma Cloud requires a service account with following minimum permissions policy:
    {
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "PrismaCloudComputeCloudDiscovery",
            "Effect": "Allow",
            "Action": [
                "ec2:DescribeImages",
                "ec2:DescribeInstances",
                "ec2:DescribeRegions",
                "ec2:DescribeTags",
                "ecr:DescribeRepositories",
                "ecs:DescribeClusters",
                "ecs:ListClusters",
                "ecs:ListContainerInstances",
                "eks:DescribeCluster",
                "eks:ListClusters",
                "lambda:GetFunction",
                "