About Fortify ScanCentral SAST sensor pools
If your Application Security server is integrated with Fortify ScanCentral SAST, and you are an Administrator, Manager, or Security Lead, you can create groups of sensors, or sensor pools based on any criteria, which you can then target for scan requests.
Sensor pools give you more control over the sensors used for scan requests. The following are examples of how you might use sensor pools:
Create pools based on sensor computing power (physical memory size) and assign scan requests that require a lot of memory to those pools.
Create pools based on teams or business units in your organization. This ensures that your resources are distributed, and no team can consume all sensors and block scan requests submitted by other teams.
If a scan request is associated with an application version, the Controller queries Application Security for available sensor pools. If the scan request is not associated with an application version, Fortify ScanCentral SAST clients can request a specific sensor pool for a scan request.
By default, sensors are removed 168 hours (7 days) after they become inactive. For details on how to change this default value, see the OpenText™ Fortify ScanCentral SAST Installation, Configuration, and Usage Guide.
Pre-defined sensor pools
Application Security provides two pre-defined sensor pools: the unassigned sensor pool and the default pool. The unassigned sensor pool, which contains all newly-registered sensors, serves as a shared sensor pool for other pools. If when you create a sensor pool the Use unassigned sensors check box is selected, the default sensor pool uses sensors from the unassigned sensor pool. It contains scan requests that were not assigned to a specific sensor pool.
See Also
Creating Fortify ScanCentral SAST sensor pools