Prisma Cloud License Types

Prisma Cloud is available as a one-, two-, or three-year subscription in the following offerings:

The SCA and Secrets Scanning modules have a developer-base metering plan. To take advantage of these modules you must switch from a resource-block based metering plan to a developer-based plan. You can make this switch from the Settings > Application Security Configuration page on the Prisma Cloud administrative console. After you switch, the new plan will calculate your credit usage based on the number of developers using the IaC Security, SCA, and Secrets Scanning modules.

A Developer seat refers to an active Git committer, identified as such through their unique Git author email address. Anyone that made a contribution to a code repo protected by Prisma Cloud within the last 90 days can also be considered a Developer.

With the Enterprise Edition, you can optionally upgrade to a premium success plan that includes 24x7 access to customer success experts, custom workshops, implementation assistance, configuration and planning, and best practices guides.

Each of these offerings has a different capacity unit and unit price in Prisma Cloud Credits. The number of credits required to secure your assets can vary based on the offering and the size of your deployment. Refer to the Prisma Cloud Licensing and Editions Guide for details. Licensing is sold in increments of 100 credits and you estimate the number of units you need to monitor and protect.

License and Consumption Details

On the Prisma Cloud administrative console Settings > Licensing, you can easily view your active license plan, the average credit consumption trend, and details on how the average credits are being used by cloud type and each cloud account.

Only resources that are active (or running) count towards Prisma Cloud credit usage. Non-active (or dormant) resources do not count towards credit usage.

licensing fy23

The page is grouped in five sections:

Behavior on License Expiry

Prisma Cloud licenses are valid for the period of time associated with the license purchase. After your Prisma Cloud license expires, your access to the Prisma Cloud administrative console is disabled until you renew the license.

If the license is not renewed within the first 90-days of your license expiration (“Grace Period”), your Prisma Cloud tenant is completely deleted. It may take up to 30 days after the Grace Period to permanently delete the data you provided and stored in the Prisma Cloud console and/or API, except in the case of the Cloud Application Security module, it will take up to 365 days from the last date of scan to permanently delete your data.

Credit Allocation

Prisma Cloud credits are used towards the features that you have subscribed and are using to monitor your cloud assets and environments. On the Credit Allocation page you can distribute credits to specific account groups and receive notifications when the credit usage exceeds a specific threshold, you can . After your set up these allocation rules, the page displays the list of rules and the current status of the purchased versus used credits.

  1. Select "Settings > Licensing > Credit Allocation".

  2. Add Credit Allocation Rule.

    Enter the details for the rule. .. Name to identify the rule. .. Select the Account Groups for which you want to monitor credit usage. .. Enter the Total Credit Balance. This is the number of credits you want to allocate for the selected account groups. .. Enter a percentage value for the Average Usage Threshold.

    + When this threshold is met, say 75% of 1000 allocated credits, an alarm is generated. You can view this alarm in the Alarm Center, and also configure alarm notifications.

    1. Submit your changes.
  3. View the rules and credit usage violations

    For each rule, the following information is available for your review. You can select each rule to edit or delete it. Rule Name, Allocated Credits, Total Credit Usage, Average Credit Usage (%), Account Groups.

    license credit allocation