As of now, it's not natively supported, but I do have a workaround that will solve your use case.
It's possible to create a custom "Entity Selection Scope" and use it inside the actions. It can be dynamic and resolved during the playbook execution.
Here are the examples of configuration:
Real use case example, I've created a test case that has 4 entities and the goal is to run the action only on 1 entity (ENTITY4):
This is how it's possible to solve the use case of creating a custom scope for blocks for remediation and ensure that the actions are only executed on a specific subset of entities. Let me know, if it makes sense.
As of now, it's not natively supported, but I do have a workaround that will solve your use case.
It's possible to create a custom "Entity Selection Scope" and use it inside the actions. It can be dynamic and resolved during the playbook execution.
Here are the examples of configuration:
Real use case example, I've created a test case that has 4 entities and the goal is to run the action only on 1 entity (ENTITY4):
This is how it's possible to solve the use case of creating a custom scope for blocks for remediation and ensure that the actions are only executed on a specific subset of entities. Let me know, if it makes sense.