Policy Transmission attributes not working as expected
Originally Published: 2011-08-29
Last Modified: 2023-09-22
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
Automatic certificate expiry notification does not seem to work as expected Number of Views RSA ID Plus Cloud Authentication Service access policy not working as expected for user immediately after attribute change Number of Views Self-Service Console Returns Error 404 Not Found When Accessed via Web-Tier in RSA Authentication Manager 8.x Number of Views SNMP queries and traps not working after configuring Authentication/Privacy passwords on RSA Authentication Manager 8.x Number of Views The approval workflow isn't working as expected when grouping by business source in the request form with the provisioning… Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to verify NTP server synchronization is not working in RSA Authentication Manager 8.x RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?
