Skip to content

Docs: add draft security guidance for BSOs - #118

Merged
carlosmartinez merged 3 commits into
mainfrom
docs/security-guidance-for-bsos
Jun 3, 2026
Merged

Docs: add draft security guidance for BSOs#118
carlosmartinez merged 3 commits into
mainfrom
docs/security-guidance-for-bsos

Conversation

@carlosmartinez

Copy link
Copy Markdown
Contributor

Draft covering network controls, identity/access, filesystem permissions, Rubie/Relay communications, Azure Arc deployment, logging, change management, incident response, and compliance references – intended for hospital IT and information security teams hosting a Rubie Gateway VM.

Jira link

https://nhsd-jira.digital.nhs.uk/browse/DTOSS-13030

Review notes

@josielsouzanordcloud - does this conform to your understanding of reality?

Review checklist

  • Check database queries are correctly scoped to current_provider

Draft covering network controls, identity/access, filesystem permissions, Rubie/Relay communications, Azure Arc deployment, logging, change management, incident response, and compliance references – intended for hospital IT and information security teams hosting a Rubie Gateway VM.
Comment thread docs/security-guidance-for-bsos.md Outdated
Comment thread docs/security-guidance-for-bsos.md Outdated
- Rubie API FQDN (e.g. `manbrs-*.azurewebsites.net` — confirm against the deployed environment).
- Azure Arc control-plane endpoints — see [Microsoft's published list](https://learn.microsoft.com/azure/azure-arc/servers/network-requirements).
- OS update endpoints (Microsoft Update / distro repositories).
- GitHub release endpoints (`github.com`, `*.githubusercontent.com`) — used by Arc to fetch new gateway versions. **[TBC with DevOps: depends on whether release assets are pulled by the Arc agent on the VM, or repackaged Azure-side and pushed via the Arc control plane.]**

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😅 We're assuming that they have an FQDN and IP allow-list capability. This seems really broad though and would allow bad actors to host malware on GitHub before installing it. Attackers can run Command & Control services on GitHub domains.

Ideally things would come from Arc, but I guess similar concerns.

Comment thread docs/security-guidance-for-bsos.md
@jabley

jabley commented May 28, 2026

Copy link
Copy Markdown
Contributor

Nice work!

@carlosmartinez
carlosmartinez merged commit 145ce86 into main Jun 3, 2026
9 checks passed
@carlosmartinez
carlosmartinez deleted the docs/security-guidance-for-bsos branch June 3, 2026 09:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants