MSV uses two unique identifiers to distinguish actions in the library. These are:
- VID - Short for “Verodin Identifier/Validation Identifier.” This is the most commonly known identifier for an action. This identifier is unique for any action on any director. (Example: A101-123)
- ID - This is an identifier for a specific action (versioned) on a specific director. The same action will NOT have the same ID on separate directors.
Most API endpoints for doing things with actions (running, creating an evaluation, etc) use the ID, not the VID.
IDs can be found in one of the following manners:
- Query /manage_sims/actions.json - This pulls down the entire action library with a lot of information and has the VID and ID for each action. This is slow and can be resource intensive for the director.
- If you know the VID, query /manage_sims/actions/<<VID».json?lookup_type=vid - given <<VID» in all caps, this will return a JSON blob including the ID
There are a few endpoints that I will share that use the ID. These API endpoints may be useful when using the MSV API to interact with the action library or running jobs:
- GET /library/actions.json?id=<<ID» - Given an <<ID» returns a full detail of the action including file dependencies.
- POST /manage_sims/actions/<<ID»/run.json - Given <<ID» and a post body containing ‘attack_node_id_1’ (with the node ID of the source actor) and ‘target_node_id_1’ (with the node ID of the destination actor) will schedule a network actions to be executed.
I hope this helps when it comes to using the Security Validation API.