microsoft / microsoft/finops-toolkit

Security improvements

Open
#1,156 3 comments 3 reactions 1 assignee View on GitHub

@MSBrett is already working on this.

Since Dec 4, 2024.

OKR: 1.1 Security Tool: FinOps hubs Type: Feature 💎
Dominant language
PowerShell
Stars
603
Forks
249
Avg merge
7d 11h
Merged PRs (30d)
11

Description

📝 Scenario

This feature request outlines a set of security enhancements that can be implemented by the FinOps Toolkit team, along with actionable recommendations for customers to strengthen the security of their deployments.

📋 Tasks

FinOps Hubs security improvements
Network
  • 1. Implement end-to-end support for private endpoint connections:
    • 1.1 Azure Data Explorer
    • 1.2 Azure Data Factory
    • 1.3 Key Vault
    • 1.4 Power BI
    • 1.5 Storage Account
Key Vault
Storage Account
  • 4. Adopt client-side encryption for Storage
General
  • 1. Review the list of suggested permissions on the deployment page and ensure these follow the least privilege principle. Recommend customers adopt the "just enough administration" approach.
  • TBD: Create a custom role to deploy FinOps Hubs ?
Actions to be documented for customers
Storage
  • Enable Microsoft Defender for Storage to monitor anomalies and threats.
Key Vault
  • Configure Private Link at the Power BI tenant level to restrict data access to private networks.
  • Enable Microsoft Defender for Key Vault to enhance threat protection.
Power BI
General
  • Recommend customers adopt the "just enough administration" (least privilege) principle.
  • Use diagnostic settings to send logs to another location, such as Log Analytics or a Storage Account, to retain logs for more than 90 days.
  • Enable Microsoft Defender for Cloud advanced threat protections, such as threat protection for Azure Network: Learn more about threat protections.

ℹ️ Additional Context

This threat model review is based on the publicly available version 0.6 of FinOps Hubs, with the inclusion of Azure Data Explorer as part of the deployment.

🙋‍♀️ Ask for the community

We could use your help:

  1. Please vote this issue up (👍) to prioritize it.
  2. Leave comments to help us solidify the vision.

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.