microsoft / microsoft/AzureTRE
Restrict access to all Apache Guacamole endpoints to specific address ranges
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 235
- Forks
- 192
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
Customer wants to secure public access to his workspace
He needs to edit Firewall, App Gateway and guacamole app service configuration.
Following best practice to make changes to the solution, this implies to create 3 new forked templates that he has to manage.
IF TRE was making incoming traffic to App Gateway and Guacamole go through Azure Firewall, this would allow customers more flexibility and the ability to make the platform completely secure with changes only on the firewall level.
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 reviewing the Firewall, App Gateway, and Guacamole app service configuration described in the issue. Determine whether incoming traffic to App Gateway and Guacamole can be routed through Azure Firewall, with address-range restrictions managed there rather than through three forked templates; done means the resulting access model is defined and secure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100