What are the basic requirements for RSA Web Threat Detection to capture our website's traffic?
Originally Published: 2016-11-02
Last Modified: 2023-10-06
Article Number
Applies To
RSA Product/Service Type: Forensics, SilverTap
RSA Version/Condition: 4.x, 5.x, 6.x
Issue
Example Scenario:
"Our website is currently built with singe page application design (SPA). We believe this is causing some difficulty for the system to track certain activities and site flow details within transactions."
Resolution
Once the system is configured to capture the website data, we can then create a transaction and create attributes which can have rules and alerts applied. This traffic can then be analyzed.
Please Note: If this basic answer does not provide a specific resolution to a current issue, please open up a case with RSA Customer Support.
Related Articles
Unable to authenticate on AD FS servers that are using different language than the default English-US when RSA Authenticat… 80Number of Views Unable to receive emails from RSA's customer support ticketing system and/or our ID Plus mail service 68Number of Views Converting a NCLOB to a VARCHAR2 in TO_DATE after error ORA-22835: Buffer too small for CLOB to CHAR or BLOB to RAW conve… 112Number of Views Error when downloading Authentication Manager files from my.rsa.com: Our records indicate you do not meet compliance requi… 33Number of Views AFX Connector fails with java.lang.NoClassDefFoundError in RSA Governance & Lifecycle 492Number 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?