When you are running security content you may want to show different routing based on source. For example:
- Actor A: public address
- Actor B: private address
- Actor A & Actor B communicating with Actor C
To allow for this, you can add virtual addresses. Using the above scenario, you would create two virtual addresses, one with Actor A and one with Actor B as the Source. The Destination would be set to Actor C, and you would define one or more of the addresses, depending on the purpose of the security content you want to run.
NOTE: Protected Theaters and Protected Actors cannot be used as a virtual address.
Let's provide a specific example. You have an external AWS Actor communicating with an Actor hosted in a DMZ within a network. An Actor can have a private address that all Actors and Directors inside the Network can talk to. However, to test traffic from that external AWS Actor communicating with the DMZ Actor the network, a different IP address would be required. By configuring a Virtual IP Address, a single Actor can be addressed in multiple ways depending on the source location.
To add a virtual address
- Go to Settings > Director Settings. The Systems Settings page opens.
- Select Virtual Addresses.
- Click Add Actor Virtual Address.
- Populate the form
- Select one or more Source Actors (the external AWS Actor from our example above)
- Select the Destination Actor (the DMZ Actor from our example above)
- Enter a Test Address, a Monitor Address, or both (Management Address is not necessary unless the source is the Director)
- Click Create Actor Virtual Address.