A user is reporting that a rule is not working as expected when a transaction is completed. The rule appears to not fire even though all the conditions are met. The user also reports that they only have difficulty getting the rule to fire when attempting the transaction at work; when they try a transaction from home, the rule fires as expected. The rule itself has no conditions based on location or IP address so the user believes being in a different location should not make any difference.
The rule is not firing because the IP address of the user is on a RSA internal aggregator list. Aggregators are tools a user enrolls in to perform tasks for a user (such as in this case online banking,) using the aggregator's characteristics such as IP address. Since the aggregator's login does not give sufficient characteristics of the user to do a acceptable authentication, the system will skip all rules that have been set up. The rule is firing at home because the aggregator is not being used at home.
There is no "resolution" as the above describes AA hosted expected behavior.