microsoft / microsoft/AzureTRE

Allow Airlock Review VMs to access previous airlock requests.

Open
#5,077 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
235
Forks
192
Avg merge
1d 23h
Merged PRs (30d)
13

Description

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Often when reviewing airlock requests, we need access to previously accepted or rejected airlock requests.
E.g. Sometimes we have plots where the underlying data was provided in a previous requests.
We also check against issues with different groupings of the same data, that may be differenced to reveal information about a group smaller than our disclosure threshold.

Describe the solution you'd like
A clear and concise description of what you want to happen.

I want to be able to, on demand, load in / mount data from previous airlock requests in the same workspace.
This includes at least approved, rejected and cancelled.
Cancelled requests are needed as sometimes, partly due to lack of the requested feature, I leave requests open whilst I follow up with some questions, and sometimes those are cancelled by the researchers.

I do not know the best way to achieve this, as the review VM is not operated within the workspace of the request AFAIU.
Perhaps moving the review VMs into the requesting workspace, or applying firewall rules to allow pulling from previous reviews via the SAS URL, although there would need to be a mechanism to list SAS URLS for cancelled / rejected requests.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files, tests, or entry points are named. Start by tracing how Airlock requests and review VMs are provisioned and how approved, rejected, and cancelled request data is exposed; define the access boundaries and an on-demand workflow for loading prior requests into the same workspace.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, python
Domain
cloud, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.