Configuring realms


Realms define security perimeters within the network that do not overlap. Each device belongs to a single realm. When you initially install The referenced document [xwiki:Automation-DevSecOps.Network-Automation.TrueSight-Network-Automation.tsna251.TrueSight Network Automation 25\.1._Inclusion-Library._Common-terminology.WebHome] was not found., all devices belong to a single realm called Default. You can create new realms to define additional security perimeters.

Realms are not exposed on the user interface until more than one realm is defined.

Realms enable a single application instance to securely manage networks belonging to multiple tenants. For example, a realm could represent:

  • A customer's network managed by a service provider
  • A network managed by a specific IT group
  • A production and lab network managed by different teams
  • A set of devices (for example, all firewalls) managed by a specific IT group (for example, Security)

Users are granted access to realms based on their assigned roles. For example, one role could have full access to a realm; another role only has reporting rights for the realm; and another role has no access to the realm.

   

Realms.png

To configure realms in your networking environment, see Adding-or-editing-a-realm. For information about managing realms, see Managing-realms.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*