What are the requirements for inter-component sharing data from RSA Web Threat Detection?
Originally Published: 2017-05-08
Last Modified: 2023-10-06
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
SAML 2.0 Requirements for Service Providers - Metadata 10Number of Views F5 BIG-IP APM - SAML My Page Configuration - RSA Ready Implementation Guide 24Number of Views SAML 2.0 Requirements for Service Providers - Supported RequestedAuthnContext Examples 14Number of Views RSA Validation Manager services do not start after fixing disk space issues 42Number of Views SecurID Internal Database Password Algorithm 79Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities IDR SSO - Step 3: Deploy the Identity Router RSA Authentication Manager 8.9 Setup and Configuration Guide
Don't see what you're looking for?