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
Generic REST Collector fails with GENERIC_REST_EXCEPTION_NULL_API_URL error when calling the Group Data operation in RSA I… Number of Views FileNotFoundException while creating an entitlement collector in RSA Identity Governance and Lifecycle Number of Views "CheckAccess" webservice API call not working correctly for accounts Number of Views How to call a stored procedure from the Generic Database AFX Connector in RSA Identity Governance & Lifecycle Number of Views Matching entitlements in RSA Identity Governance and Lifecycle are not displaying when Entitlement Rule is set to Ent Type… Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager 8.9 Setup and Configuration Guide RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings.
Don't see what you're looking for?
