Martin44 (Customer) asked a question.
Not a question but an improvement opportunity. Would be great to have the RSA console keeping a kind of emergency token history so we would be able as an RSA admin to see easily if a user received many emergency token code in a row to prevent the abuse.
This seems to be related to SecurID or ID Plus and not to G&L.
If you would like to submit an improvement, you can navigate to this url (while being logged in) - Idea Exchange | RSA Community
(Thanks, @Boris.Lekumovich (RSA)!
@Martin44 (Customer),
The administration activity report has the ability to show you how often emergency access tokencodes were issued for a token.
With the real time administrator activity monitor running, I generated tokencodes. In the screenshot below, the row with a timestamp of 2026-03-09 10:55:09.143 is the first set of emergency tokens that I generated for the token assigned to my user. The row above at 2026-03-09 10:55:11.511 shows how I updated the token codes.
You can use the option to enter a user ID to scope your results down to a specific user. If you need historic data, go to Reporting > Reports > Add new and use the Administrator Activity template to create a report.
Hello Erica,
thanks for your comment, I placed my suggestion as Boris suggested to the correct place.
Just to clarify, the purpose of my improvement is not intended to see when an emergency token code is set to expire, this information can be found easily in the emergency token code interface. The purpose is to have a brief history of let's say the last 3 month assigned emergency token codes on a specific token directly on the RSA console exactly where you can assign emergency token code (manage Emergency token code). A report is definitely not the best thing to do when you're online with a user.
Thanks
@Martin44 (Customer) ,
Thank you for the clarification. If you want to see that data in the Security Console UI, then you are right to create an idea for PM. In the meantime, generating the admin activity report and filtering for a specific user ID or token is the best way to go.