-
Notifications
You must be signed in to change notification settings - Fork 178
Button to revoke access to previously authorised Airlock export request. #4543
Description
Is your feature request related to a problem? Please describe.
We had an instance where an Airlock request was accidentally approved due to a stray mouse click.
In response we edited Cosmos DB to change the status to rejected to prevent the data being downloaded.
Describe the solution you'd like
Two things can help.
Mitigate stray mouse clicks
A confirmation box, or a delay (~3-5s) in the GUI prior to committing the action for the Airlock reviewer to recognise a problem and correct it immediately.
In the case of the delay, a button should be available to edit the request before sending.
A confirmation box may be the easier solution.
Mitigate unintended data egress
A "revoke" button in the GUI for all authorised airlock requests.
This can be used by an Airlock reviewer to mitigate damage following a mistake or a change in circumstances requiring the data be pulled.
The option to revoke should exist for all time (without expiry) as mistakes may not be noticed immediately, or circumstances may change after some time.
I suggest "Revoked" (or similar) as the status, instead of re-using rejected, to be clear that the request was at some point available and may have been downloaded.
Once revoked, the URL links to download the files should be removed from the GUI and existing links invalidated.
Describe alternatives you've considered
All ideas have been presented.
Additional context
No.