A missing, outdated, or invalid local web browser cache causes this issue. The SIEM GUI isn’t served up to the user through HTTP gets. Pages aren’t rendered through delivery of HTML data to the user session.
When a user connects to SIEM for the first time, a local copy of the SIEM GUI is installed in the browser. When connecting to the ESM, all communication with the server is done via SIEM API calls rather than HTTP.
It isn’t uncommon for the SIEM GUI package to be updated when upgrading the ESM. Upon the next connection, a new copy of the updated GUI is downloaded to the browser. Sometimes the GUI isn’t updated with the new copy, which causes the GUI to encounter render problems.