Azure Credentials
Table of Contents
Self.Hosted 31.xx
Expand all | Collapse all
-
- Getting started
- System Requirements
- Cluster Context
-
- Prisma Cloud Container Images
- Kubernetes
- Deploy the Prisma Cloud Console on Amazon ECS
- Console on Fargate
- Onebox
- Alibaba Cloud Container Service for Kubernetes (ACK)
- Azure Container Service (ACS) with Kubernetes
- Azure Kubernetes Service (AKS)
- Amazon Elastic Kubernetes Service (EKS)
- IBM Kubernetes Service (IKS)
- OpenShift v4
-
- Defender Types
- Manage your Defenders
- Redeploy Defenders
- Uninstall Defenders
-
- Deploy Orchestrator Defenders on Amazon ECS
- Automatically Install Container Defender in a Cluster
- Deploy Prisma Cloud Defender from the GCP Marketplace
- Deploy Defenders as DaemonSets
- VMware Tanzu Application Service (TAS) Defender
- Deploy Defender on Google Kubernetes Engine (GKE)
- Google Kubernetes Engine (GKE) Autopilot
- Deploy Defender on OpenShift v4
-
- Agentless Scanning Modes
-
- Onboard AWS Accounts for Agentless Scanning
- Onboard Azure Accounts for Agentless Scanning
- Configure Agentless Scanning for Azure
- Onboard GCP Accounts for Agentless Scanning
- Configure Agentless Scanning for GCP
- Onboard Oracle Cloud Infrastructure (OCI) Accounts for Agentless Scanning
- Configure Agentless Scanning for Oracle Cloud Infrastructure (OCI)
- Agentless Scanning Results
-
- Rule ordering and pattern matching
- Backup and Restore
- Custom feeds
- Configuring Prisma Cloud proxy settings
- Prisma Cloud Compute certificates
- Configure scanning
- User certificate validity period
- Enable HTTP access to Console
- Set different paths for Defender and Console (with DaemonSets)
- Authenticate to Console with Certificates
- Configure custom certs from a predefined directory
- Customize terminal output
- Collections
- Tags
- Logon settings
- Reconfigure Prisma Cloud
- Subject Alternative Names
- WildFire Settings
- Log Scrubbing
- Clustered-DB
- Permissions by feature
-
- Logging into Prisma Cloud
- Integrating with an IdP
- Integrate with Active Directory
- Integrate with OpenLDAP
- Integrate Prisma Cloud with Open ID Connect
- Integrate with Okta via SAML 2.0 federation
- Integrate Google G Suite via SAML 2.0 federation
- Integrate with Azure Active Directory via SAML 2.0 federation
- Integrate with PingFederate via SAML 2.0 federation
- Integrate with Windows Server 2016 & 2012r2 Active Directory Federation Services (ADFS) via SAML 2.0 federation
- Integrate Prisma Cloud with GitHub
- Integrate Prisma Cloud with OpenShift
- Non-default UPN suffixes
- Compute user roles
- Assign roles
-
- Prisma Cloud Vulnerability Feed
- Scanning Procedure
- Vulnerability Management Policies
- Vulnerability Scan Reports
- Scan Images for Custom Vulnerabilities
- Base images
- Vulnerability Explorer
- CVSS scoring
- CVE Viewer
-
- Configure Registry Scans
- Scan Images in Alibaba Cloud Container Registry
- Scan Images in Amazon Elastic Container Registry (ECR)
- Scan images in Azure Container Registry (ACR)
- Scan Images in Docker Registry v2 (including Docker Hub)
- Scan Images in GitLab Container Registry
- Scan images in Google Artifact Registry
- Scan Images in Google Container Registry (GCR)
- Scan Images in Harbor Registry
- Scan Images in IBM Cloud Container Registry
- Scan Images in JFrog Artifactory Docker Registry
- Scan Images in Sonatype Nexus Registry
- Scan images in OpenShift integrated Docker registry
- Scan Images in CoreOS Quay Registry
- Trigger Registry Scans with Webhooks
- Configure VM image scanning
- Configure code repository scanning
- Malware scanning
- Windows container image scanning
- Serverless Functions Scanning
- VMware Tanzu Blobstore Scanning
- Scan App-Embedded workloads
- Troubleshoot Vulnerability Detection
-
- Compliance Explorer
- Enforce compliance checks
- CIS Benchmarks
- Prisma Cloud Labs compliance checks
- Serverless functions compliance checks
- Windows compliance checks
- DISA STIG compliance checks
- Custom compliance checks
- Trusted images
- Host scanning
- VM image scanning
- App-Embedded scanning
- Detect secrets
- OSS license management
-
- Alert Mechanism
- AWS Security Hub
- Cortex XDR alerts
- Cortex XSOAR alerts
- Email alerts
- Google Cloud Pub/Sub
- Google Cloud Security Command Center
- IBM Cloud Security Advisor
- JIRA Alerts
- PagerDuty alerts
- ServiceNow alerts for Security Incident Response
- ServiceNow alerts for Vulnerability Response
- Slack Alerts
- Splunk Alerts
- Webhook alerts
- API
Azure Credentials
This section discusses Azure credentials.
Authenticate with Azure using a certificate
You can authenticate with Azure using a certificate as a secret.
As with password authentication, the certificate is stored with the Azure service principal.
For more information, see the Microsoft docs here.
- Log into Compute Console.
- Go toManage > Cloud accounts
- ClickAdd account.
- InSelect cloud provider, chooseAzure.
- Enter a name for the credential.
- InSubtype, selectCertificate.
- InCertificate, enter your service principal’s certificate in PEM format.The certificate must include the private key. Concatenate public cert with private key (e.g., cat client-cert.pem client-key.pem).
- Enter a tenant ID.
- Enter a client ID.
- Enter a subscription ID.
- ClickNext.
- InScan account, disableAgentless scanning.
- ClickNext.
- ClickAdd account.
- Validate the credential.Your Azure credential is now available to be used in the various integration points in the product, including registry scanning, serverless function scanning, and so on. If authentication with a certificate is supported, it’s shown in the credential drop-down in the setup dialog. For example, the following screenshot shows the setup dialog for scanning Azure Container Registry:After setting up your integrations, you can review how and where the credential is being used by going toManage > Authentication > Credentials storeand clicking on the credential.
Create an Azure Service Principal
Create an Azure Service Principal so that Prisma Cloud Console can scan your Azure tenant for microservices.
To get a service key:
- Download and install the Azure CLI.
- Create a service principal and configure its access to Azure resources.$ az ad sp create-for-rbac \ --name <user>-twistlock-azure-cloud-discovery-<contributor|reader> \ --role <reader|contributor> \ --scopes /subscriptions/<yourSubscriptionID> \ --sdk-authThe--rolevalue depends upon the type of scanning:
- contributor = Cloud Discovery + Azure Container Registry Scanning + Azure Function Apps Scanning
- reader = Cloud Discovery + Azure Container Registry Scanning
Copy the output of the command and save it to a text file. You will use the output as theService Keywhen creating an Azure credential.{ "clientId": "bc968c1e-67g3-4ba5-8d05-f807abb54a57", "clientSecret": "5ce0f4ec-5291-42f8-gbe3-90bb3f42ba14", "subscriptionId": "ae01981e-e1bf-49ec-ad81-80rf157a944e", "tenantId": "d189c61b-6c27-41d3-9749-ca5c9cc4a622", "activeDirectoryEndpointUrl": "https://login.microsoftonline.com", "resourceManagerEndpointUrl": "https://management.azure.com/", "activeDirectoryGraphResourceId": "https://graph.windows.net/", "sqlManagementEndpointUrl": "https://management.core.windows.net:8443/", "galleryEndpointUrl": "https://gallery.azure.com/", "managementEndpointUrl": "https://management.core.windows.net/" } - Open Console, and go toManage > Authentication > Credentials Store.
- ClickAdd credential, and enter the following values:
- Enter a descriptiveNamefor the credential.
- In theTypefield, selectAzure.
- Enter theService Key.Copy and paste the contents of the text file you saved earlier when you created the service principal.
- Saveyour changes.
Storing the credential in Prisma Cloud
Store the service principal’s credentials in Console so that Prisma Cloud can authenticate with Azure for scanning.