The UAT environment is constantly updated to mirror production. This includes policies, hierarchy, user attributes, settings, communication surveillance policy roles, policy classes, security models, user roles, and patches that have been applied to production.
From the development environment, the changes are then moved into UAT. This is done by copying and pasting the changes from the Notepad++ document.
The configuration file is updated to reflect the date range that was covered by the refinement queue.
To ensure the most accurate test of the changes, all of the policies or rules that are enabled in production are enabled in UAT. This is to see how the policies behave together.
Once it’s been confirmed that there are no errors present, the captured events are reviewed to determine the quality of what the policies have captured.