|
1 | 1 | # HTB Certified — ACEVision Case Study |
| 2 | +> **Version Note** |
| 3 | +> |
| 4 | +> This case study was created using an earlier version of ACEVision before the introduction of: |
| 5 | +> |
| 6 | +> * Object Type Detection |
| 7 | +> * Trigger Right Detection |
| 8 | +> * ACEVision Advisor |
| 9 | +> * Recommended Abuse Paths |
| 10 | +> * Potential Outcomes |
| 11 | +> * Suggested Attack Flows |
| 12 | +> |
| 13 | +> The ACL analysis, SID relationships, and privilege escalation findings documented in this case study remain valid. |
| 14 | +> |
| 15 | +> The screenshots shown throughout this document reflect the ACEVision output available at the time the research was performed. |
| 16 | +> |
| 17 | +> For examples of the current ACEVision Advisor output, see: |
| 18 | +> |
| 19 | +> * `docs/validation/` |
| 20 | +> * `docs/comparisons/` |
| 21 | +> |
| 22 | +> These directories contain validation screenshots and BloodHound comparisons generated using the latest version of ACEVision. |
2 | 23 |
|
3 | 24 | ## Overview |
4 | 25 |
|
@@ -238,3 +259,21 @@ By exposing the exact trustee, object, and permission responsible for the relati |
238 | 259 |
|
239 | 260 | This visibility helps operators, defenders, and students understand not only that a privilege escalation path exists, but why it exists. |
240 | 261 |
|
| 262 | +## ACEVision Advisor (Current Version) |
| 263 | + |
| 264 | +Since this case study was published, ACEVision has evolved beyond ACL enumeration and now includes an interpretation layer known as **ACEVision Advisor**. |
| 265 | + |
| 266 | +ACEVision Advisor automatically identifies: |
| 267 | + |
| 268 | +* Object Type |
| 269 | +* Trigger Right |
| 270 | +* Recommended DACL Modifications |
| 271 | +* Recommended Abuse Paths |
| 272 | +* Potential Outcomes |
| 273 | +* Suggested Attack Flows |
| 274 | + |
| 275 | +The goal is to help operators understand not only **who controls an object**, but also **what that control means** and **how it may be abused in real-world Active Directory attack paths**. |
| 276 | + |
| 277 | +See the validation and comparison directories for examples generated using the current version. |
| 278 | + |
| 279 | + |
0 commit comments