A Simulator, also known as a node or agent, is deployed within a network that executes simulated breach and attack scenarios. It collects data from these simulations to assess security postures and identify vulnerabilities.

Return the list of all nodes(agents), both active and inactive

Create a new remote node, for use when the node can't access it self to the system and the connection needs to be initiated from the system to the node

Update a node. Only the details provided will be updated.

Deletes a node from the system

Return the list of all nodes(agents), both active and inactive

Return the nodes aggregations by specific column

Return the list of simulation users available on a given node

List the proxies associated with/connected to a simulator (aka node/agent)

Return the list of assets available on a given node

Add a simulation user to an existing node

Add a proxy to a simulator (aka node/agent)

Add an asset to an existing node. Once the asset is in the node the system will try to exfiltrate the asset from there

Delete a proxy association from a node

Delete a proxy association from a node

Delete an asset from a node will stop running exfiltrations from the node with the asset

Enables an Advanced Action for a node. This will allow running attacks tagged with this Advanced Action"

Disables an Advanced Action for a node. This will prevent running attacks tagged with this Advanced Action

Return the currently used secret, if one does not exist, create a new random secret and return it.

Create a new random secret.

A Proxy in SafeBreach facilitates connectivity for simulators that require indirect access to the platform, typically in segmented or remote environments.

Virtual Nodes are Mailboxes, Cloud Attacks (cloud integration), Web Applications used as attack entities