Please further limit read access to some properties of the deviceHealthScript resource
維護者通常 2 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 25/100
- Issue 類型
- 功能
- 描述清晰度
- 基本清楚
- 活躍度
- 停滯
- 技術堆疊
- azure, powershell
- 領域
- api, authorization, security
研究方向
從連結的 deviceHealthScript 資源文件和 Microsoft Graph 權限參考開始。評估所提議的最小權限 app role,以及對 detectionScriptContent 和 remediationScriptContent 的屬性層級存取行為。指定並記錄所要求的存取限制或替代方案後,即視為完成。
由索引模型根據 Issue 內容生成。
描述
Hello,
We are creating an audit tool to identify risks in some Microsoft systems, including Intune. As part of that work, we are looking at auditing risks surrounding various resource types, including deviceHealthScript resources.
The deviceHealthScript resource type includes these two properties:
- detectionScriptContent
- remediationScriptContent
Those properties' values are base64-encoded PowerShell scripts.
This is problematic because our experience has been that PowerShell scripts often contain sensitive material such as credentials. When we deploy our software to our customers, we ask them to create an Entra application and grant the application the least privilege required to read information relevant to how we identify risks. Our product is a SaaS product, so the customer's data winds up in our infrastructure.
We can of course control our data collection software to filter out the detectionScriptContent and remediationScriptContent field values before the data is sent to our SaaS instance. But we would prefer, if possible, to be able to select a least-privilege MS Graph app role that can list deviceHealthScript objects, but cannot read the detectionScriptContent and remediationScriptContent field values. We believe this would be the most effective change to limit the risks we ourselves are creating for our customers.
The two MS Graph app roles that enable reading deviceHealthScript resources are:
- DeviceManagementConfiguration.Read.All
- DeviceManagementConfiguration.ReadWrite.All
Perhaps a possible solution could be to add a new MS Graph app role called:
- DeviceManagementConfiguration.ReadBasic.All
And then constrain access to reading property values on deviceHealthScript objects such that the detectionScriptContent and remediationScriptContent fields cannot be read when presenting a JWT with only that permission. This would function similarly to the existing User.ReadBasic.All MS Graph app role: https://learn.microsoft.com/en-us/graph/permissions-reference#userreadbasicall
Thank you for your consideration.
- 主要語言
- XSLT
- 星號
- 171
- 分支
- 56
- 平均合併
- 1 天 11 小時
- 30 天內合併 PR
- 9
環境準備
這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
microsoftgraph/msgraph-metadata 的其他 Issue
-
ToTriage
難度 2/5 1-3 小時 新手友好度 86/100
microsoftgraph/msgraph-metadata#1217 ·
維護者通常 2 天內回覆
-
ToTriage
難度 2/5 1-3 小時 新手友好度 68/100
microsoftgraph/msgraph-metadata#1192 ·
維護者通常 2 天內回覆
-
ToTriage
難度 3/5 1-2 天 新手友好度 57/100
microsoftgraph/msgraph-metadata#1233 ·
維護者通常 2 天內回覆
-
`microsoft.graph.managedDevice` is missing a filter restrictions annotation.可能已有人在做 @esidorenko-sl 於 86 天前認領。 未關閉ToTriage
難度 3/5 1-2 天 新手友好度 72/100
microsoftgraph/msgraph-metadata#1193 · 2 則留言 ·
維護者通常 2 天內回覆
-
ToTriage
難度 4/5 3-5 天 新手友好度 45/100
microsoftgraph/msgraph-metadata#1169 · 1 個 reaction ·
維護者通常 2 天內回覆
查看 microsoftgraph/msgraph-metadata 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 65/100
matomo-org/plugin-CustomAlerts#310 ·
維護者通常 1 天內回覆
-
bug level:trivial
難度 2/5 1-3 小時 新手友好度 72/100
exoego/keycloak-fuhito#666 ·
維護者通常 1 天內回覆
-
bug size:small
難度 2/5 1-3 小時 新手友好度 88/100
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 66/100
-
難度 2/5 1-3 小時 新手友好度 78/100
fb55/htmlparser2#2579 ·
維護者通常 1 天內回覆