> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/ox-code/ox-scan-engines.md). # OX Scan Engines OX Scan Engines analyze different areas of your software development environment to identify security risks, vulnerabilities, and configuration issues across the software supply chain. Each scan engine focuses on a specific security domain, such as application code, secrets and sensitive data, open source dependencies, infrastructure as code, source control configuration, or CI/CD security. Rather than treating these areas as isolated security checks, OX combines findings from its scan engines with context collected across your development environment. This context helps OX understand relationships between applications, code, dependencies, infrastructure, and development processes, and determine the potential impact of identified issues. Scan engine findings are evaluated according to OX policies and enriched with contextual information to help prioritize the issues that require attention. Use the pages in this section to learn more about the different OX scan engines, what each engine analyzes, and the security issues it can identify. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.ox.security/ox-code/ox-scan-engines.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.