What are the basic requirements for RSA Web Threat Detection to capture our website's traffic?
Originally Published: 2016-11-02
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
Error message "Our process does not support use of public accounts" when registering for an RSA Community or myRSA account Number of Views Unable to receive emails from RSA's customer support ticketing system and/or our ID Plus mail service Number of Views Unable to authenticate on AD FS servers that are using different language than the default English-US when RSA Authenticat… Number of Views Error when downloading Authentication Manager files from my.rsa.com: Our records indicate you do not meet compliance requi… Number of Views Envision: Why are we writing to the master database when collecting Microsoft SQL database logs Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory Troubleshooting AFX Connector issues in RSA Identity Governance & Lifecycle RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.9 Release Notes (January 2026)
Don't see what you're looking for?
