What are the requirements for inter-component sharing data from RSA Web Threat Detection?
Originally Published: 2017-05-08
Article Number
Applies To
RSA Product/Service Type: Mitigator
RSA Version/Condition: 5.1, 6.x
Issue
Example Customer Question --
We moved the mitigator to a separate server. Since then, the reporting graph is not working and hourly alerts are not displayed on the Alerts tab within the UI. We are sharing the directories /silvertail/data/shared/eds, edsserver and alerts as well as the mitigator.rules across both servers (mitigator and analytical servers). Are we missing something that needs to be shared as this issue appeared when we moved the mitigator to a separate server?
Resolution
Share the var/opt/silvertail/data directory and subdirectories including
/data/alerts
/data/edsserver
/data/logs
/data/reports
/data/tasks
The requirements for an external directory, no matter what the hardware or infrastructure technology(e.g., NAS, FiberOptic,etc.) is that this directory must appear as a normal directory when doing a directory listing command in RHEL or CentOS Linux. You cannot use a symlink to point to one of the above locations.
Related Articles
Inter-site SSO fails on Internet Explorer (IE) 7 12Number of Views To have the list of implicit rules for reference 12Number of Views How to Install a Third Party Certificate into RSA enVision 262Number of Views How to Install a Third Party Certificate into enVision 12Number of Views Installer prerequisite fails on files that are not relevant to the RSA Governance & Lifecycle deployment 147Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA Authentication Manager Patch Updates How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Artifacts to gather in RSA Identity Governance & Lifecycle
Don't see what you're looking for?