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 Via Lifecycle and Governance WildFly cluster not connecting as expected Number of Views "Maintain" and "Maintain with Expiration" are not working as expected in multi-step review in RSA Governance & Lifecycle Number of Views 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 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
RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA RADIUS Server service failed to start in the RSA Authentication Manager 8.1 Operations Console Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Release Notes: Cloud Access Service and RSA Authenticators
Don't see what you're looking for?
