When creating a custom role, which Scanning Permissions can you assign?

When creating a custom role in the context of the Assured Compliance Assessment Solution (ACAS), the ability to assign specific scanning permissions is crucial for managing and controlling how users interact with scanning tasks. The correct choice, which is to create scans, reflects a fundamental capability necessary for users assigned this role.

By providing the permission to create scans, you enable users to initiate and configure scanning tasks that can assess compliance and vulnerabilities within the system. This foundational ability empowers users to execute their responsibilities effectively by actively engaging in the scanning process rather than merely overseeing it.

The other choices—creating plugin scans, creating passive scans, and setting user roles—represent more specialized functionalities or administrative capabilities that may not be included in the basic scanning permissions. While these options may be important in certain contexts, the primary action of creating standard scans is essential for users tasked with compliance assessment and system security, making it the appropriate choice for a custom role focused on operational scanning tasks.