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
RSA ID Plus Cloud Authentication Service access policy not working as expected for user immediately after attribute change 25Number of Views "Maintain" and "Maintain with Expiration" are not working as expected in multi-step review in RSA Governance & Lifecycle 14Number of Views The approval workflow isn't working as expected when grouping by business source in the request form with the provisioning… 30Number of Views Trusted Network policy attribute does not work correctly with applications configured after disabling Identity Confidence … 71Number of Views Automatic certificate expiry notification does not seem to work as expected 20Number of Views
Don't see what you're looking for?