Create a product workload mapping for CrowdStrike products

Create a product workload mapping for your CrowdStrike products for accurately associating specific products with the types of workloads they manage.

Before you begin

You must create a CrowdStrike integration profile before creating a workload mapping. For more information, see Integrating with CrowdStrike.

Role required: sam_admin or sam_integrator

About this task

Workload mapping is essential for accurately associating specific products with the types of workloads they manage. For example, servers, desktops, and containers. This is because CrowdStrike provides consumption data for endpoints or workloads instead of consumption data for specific products. Workload mapping enables you to map workloads that are consumed against each product. Based on the workload mapping that you create, the consumption across workloads is aggregated for each product, preventing over- or under-counting. This new approach replaces previous methods and aligns with how CrowdStrike now tracks usage, ensuring accurate compliance.

Procedure

1. Navigate to Software Asset Workspace > License operations > User subscription > CrowdStrike product workload mappings.
2. Select New.
3. On the CrowdStrike Product Workload Mapping form, fill in the fields.

   Table 1. CrowdStrike Product Workload Mapping form

   Field	Description
   Integration profile	The integration profile for which the workload mapping is being created. This field is automatically populated when you navigate to the product workload mapping form from a particular integration profile.
   Workload	Endpoints are physical or virtual devices, such as a computer, server, laptop, desktop computer, mobile, cellular, container, pod, or virtual machine image. Endpoints are sometimes referred to as workloads. For example, containers public_cloud_with_containers servers_without_containers chrome_os
   Software model	Profile of the software, which includes publisher, version, and discovery map.
   License metric	License metric for the selected software model. Reserved Hourly Average Sensor: This metric counts the number of unique active endpoints per clock-hour and averages them over a rolling 28-day period. The count of Reserved Hourly Average Sensor Licenses resets at the start of each clock-hour. Sensor Subscription: This metric calculates license usage by averaging endpoint counts over four consecutive weeks. Weekly endpoint counts are based on the total number of endpoints consumed in the previous seven days.

4. Select Save.

Result

The mapping that you have created appears in the CrowdStrike product workload mapping list.

Related concepts

• Integrating with CrowdStrike