Policy Transmission attributes not working as expected
Originally Published: 2011-08-29
Article Number
Issue
transmission attribute "is NOT" matches but event/incident is still being generated
Resolution
Select one of "From Sender", "To Recipient", "From IP", etc. using "is" or "is Not"
If additional attributes are required click on "New Rule" and add the attribute there
For example, to exclude certain trusted senders and recipients:
Add an Allow rule with From Sender and a list of trusted senders
Add an Allow rule with To Recipient and a list of trusted recipients
Place these 2 rules before the rule containing the content blades
Related Articles
"Maintain" and "Maintain with Expiration" are not working as expected in multi-step review in RSA Governance & Lifecycle 14Number of Views Automatic certificate expiry notification does not seem to work as expected 20Number of Views RSA Via Lifecycle and Governance WildFly cluster not connecting as expected 123Number of Views Terminated users are not displayed while manually mapping accounts in RSA Identity Governance & Lifecycle 7.1.0 45Number of Views Local Entitlement stays in pending verification state in RSA Governance & Lifecycle 106Number of Views
Trending Articles
Troubleshooting RSA SecurID Access Identity Router to RSA Authentication Manager test connection failures RSA SecurID Software Token 5.0.2 Downloads for Microsoft Windows RSA Authentication Manager 8.9 Release Notes (January 2026) Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.8 Setup and Configuration Guide
Don't see what you're looking for?