microsoft / microsoft/AzureTRE
Are Azure storage firewall rules from AML workspace service needed when n public IP? (NSG blocks)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 235
- Forks
- 192
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
Description
As a TRE Administrator I want to be confident no data is being exfiltrated. At present the AML workspace service bundle adds firewall rules for Azure storage as these are needed when configured for public access. In private configuration, network security groups block this traffic, but the firewall rules remain. It would be cleaner if the storage rules only appeared on the Firewall when absolutely necessary.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the AML workspace service bundle and the code that generates Azure Storage firewall rules. Compare private and public workspace configurations; done means unnecessary storage rules are omitted for private access while required rules remain for public access.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, python
- Domain
- cloud, networking, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100