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
FileNotFoundException while creating an entitlement collector in RSA Identity Governance and Lifecycle Number of Views Generic REST Collector fails with GENERIC_REST_EXCEPTION_NULL_API_URL error when calling the Group Data operation in RSA I… Number of Views RSA Via Lifecycle and Governance 7.0 Global Roles do not show under matching entitlements when entitlement rule is set to … Number of Views "CheckAccess" webservice API call not working correctly for accounts 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 8.8 Setup and Configuration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) Test connection fails from the RSA ID Plus Cloud Access Service and Identity Router to the SecurID Authentication Manager Details on RSA SecurID tokens and RSA Authentication Manager licenses RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows
Don't see what you're looking for?
