Suggestions for new Queries
@martinsohn 已经在做这个了。
开始于 2026年8月4日。
评估
这个 Issue 还没有评估数据。
描述
I haven't found these in the database, but since we always check them in a customers environment, I though I suggest including them. They're both kinda related, to I only created a single issue.
name: Check for Objects not owned by Tier Zero
guid: b67b5d95-fe53-40f0-b0c5-a874abb086a5
prebuilt: false
platform: Active Directory
category: Dangerous Privileges
description: In most Active Directory environments, objects should usually be owned only by privileged
administrative groups (e.g., Domain Administrators or Enterprise Administrators). Assigned ownership to other
users or groups introduce potential privilege escalation risks, as object owners can always modify permissions and
regain full control. Therefore, object ownership should be regularly reviewed and corrected.
query:
MATCH p = (n)-[:Owns*1..]->(o)
WHERE NOT ((n:Tag_Tier_Zero) OR COALESCE(n.system_tags, '') CONTAINS 'admin_tier_0')
RETURN p
LIMIT 1000
revision: 1
resources: https://rdr-it.com/en/active-directory-change-object-owner-in-bulk/
acknowledgements: @kaasimir
The following query was created, since I often got false positives out of Bloodhound -> often a user was the owner of an object, but beside the Owns edge, other like WriteDacl, WriteOwner or GenericWrite where shown as well. With this query I check for implicit assigned permissions, which has been kinda handy in the past:
name: Check for Object Takeover Permissions
guid: 465e5364-3976-474e-b666-6e6d2ac573bf
prebuilt: false
platform: Active Directory
category: Dangerous Privileges
description: Object ownership implicitly grants the ability to modify an object's permissions, which can result in
additional effective rights. As a result, BloodHound may display multiple privilege edges even though ownership is
the underlying cause, making remediation more complex. This query identifies explicitly assigned critical
permissions, allowing them to be reviewed independently and removed where appropriate.
query:
MATCH p = (o)<-[:GenericWrite|GenericAll|WriteOwner|WriteDacl]-(n)
WHERE NOT (o)<-[:Owns]-(n)
AND NOT ((n:Tag_Tier_Zero) OR COALESCE(n.system_tags, '') CONTAINS 'admin_tier_0')
AND NOT n.name STARTS WITH 'MSOL'
RETURN p
LIMIT 1000
revision: 1
resources: -
acknowledgements: @kaasimir
Thx a ton guys, hope those are helpful and keep up the great work!
Cheers, kaasimir
- 主要语言
- Python
- 星标
- 205
- 派生
- 24
- PR 合并指标
- 30 天内没有已合并 PR
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
相似的 Issue
-
documentation help wanted
难度 2/5 1-3 小时 新手友好度 90/100
-
难度 2/5 1-3 小时 新手友好度 90/100
simonw/sqlite-utils#872 ·
-
难度 2/5 1-3 小时 新手友好度 88/100
-
难度 2/5 1-3 小时 新手友好度 82/100
-
难度 2/5 1-3 小时 新手友好度 78/100