How can we prevent a user who made a Dual Control access request from deleting their request?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

How can we prevent a user who made a Dual Control access request from deleting their request?

L1 Bithead

During testing of the Dual Control functionality, we had a user make a request that was subsequently approved. The user then accessed the password, used the PSM Connection Component, etc. After this, the user subsequently Deleted his access request.

 

When this occurred the history of why the request was made and granted was lost. This makes it almost impossible to use this as a control that would be acceptable to an Auditor.

 

Is there a way to prevent a user from deleting their request and/or generate a report of requests and approvals?

 

Thanks.

1 accepted solution

Accepted Solutions

L4 Transporter

Hi @Ray Sundland​ 

 

As Isoto has mentioned, it's not possible to restrict this, from what has been described, the cancelled request was requested to have multiple access during a given time frame, when this happens the request is still visible to the requester who can then cancel once approved.

 

In this scenario, the reasoning for the request is not lost and can be reported on....

 

You can visually see this on the accounts activity or you can pull an Activity Report from Reports and filter this by the platform and account and then limit the Activities to "Use Password"

 

Additionally, if you have SIEM integration, it will be reported also.

 

Hope this helps

 

Thanks

 

Michael

View solution in original post

3 REPLIES 3

L1 Bithead

Hi @Ray Sundland​ 

 

I don't think it's currently possible to restrict a user's ability to delete requests they created. This also allows the user to generate a new request if the previous one had errors and not wait for another user to reject it first.

 

What you could do is try to replicate the scenario of generating a request, approving it, and then deleting it. Then, generate the Activity Logs report to verify that all the request information is stored for audit purposes.

L4 Transporter

Hi @Ray Sundland​ 

 

As Isoto has mentioned, it's not possible to restrict this, from what has been described, the cancelled request was requested to have multiple access during a given time frame, when this happens the request is still visible to the requester who can then cancel once approved.

 

In this scenario, the reasoning for the request is not lost and can be reported on....

 

You can visually see this on the accounts activity or you can pull an Activity Report from Reports and filter this by the platform and account and then limit the Activities to "Use Password"

 

Additionally, if you have SIEM integration, it will be reported also.

 

Hope this helps

 

Thanks

 

Michael

L1 Bithead

Thanks for the info. Didn't even think to look under Activities.

  • 1 accepted solution
  • 162 Views
  • 3 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!