The other option that we leave for the user is deciding in what assets every test will be run. One option would be to run all tests in all assets, but in most cases it makes more sense to restrict some tests to “low-value” assets (those that might be easily accessed but that have less valuable information) and some other tests to the “high-value” assets.For instance, it would make sense to execute the Lateral Movement test only in low-value assets (from which an attacker would try to access more protected assets from that source), while the Collection, Command and Control, and Exfiltration tests would be best run on high-value assets due to the likelihood of being targeted for their content.To configure the assets for a test, you only have to click on the three dots on the right side of it, and a dropdown will be displayed with the “Manage Assets” option: