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 RSA Via Lifecycle and Governance WildFly cluster not connecting as expected 123Number of Views RSA Governance & Lifecycle Dashboards and Reports Recommended Practice Workshop 10Number of Views Automatic certificate expiry notification does not seem to work as expected 20Number of Views Special characters in email subject lines do not display as expected in RSA Identity Governance & Lifecycle 44Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.9 Release Notes (January 2026) An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?