> For the complete documentation index, see [llms.txt](https://docs.oort.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oort.io/understanding-check-failures/oort-insights/identity-posture-management-insights/attack-path-alert.md). # Attack Path Alert The Attack Path Alert check identifies identities that appear in attack path findings ingested from [BloodHound Enterprise](/integrations/bloodhound-enterprise.md). Attack paths represent sequences of relationships and permissions that could allow lateral movement or privilege escalation to reach high-value targets. When triggered, this check highlights users who may be positioned to reach sensitive assets through one or more discovered paths. **Recommended actions**\ Validate the attack path details and remove excessive privileges or risky relationships involved in the path. Prioritize users with high impact or exposure, especially those connected to privileged roles or critical assets. **Check settings**\ You can adjust the check settings to filter out some attack paths based on severity to reduce noise and focus on higher-risk findings. **Compatibility**\ BloodHound Enterprise --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.oort.io/understanding-check-failures/oort-insights/identity-posture-management-insights/attack-path-alert.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.