> 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/get-started/planning-next-steps.md). # Planning Next Steps After reviewing your first scan results, plan the next steps to tailor OX to your environment and workflow: * **Connect Container Registries and Cloud Accounts:** Add container registries and cloud accounts if they are relevant to your environment. This is optional and depends on the type of applications you manage. * [**Connect Your Ticketing and Messaging Systems:**](/ticketing-and-messaging/about-messaging-and-ticketing-in-ox.md) Connect systems such as Jira to streamline issue creation and assignment from OX. * [**Connect CI/CD Pipelines:**](/scan-and-analyze-with-ox/scanning/scanning-ci-cd-pipelines.md) Integrate your pipelines to scan, build artifacts, and enforce security checks during development. This step is more advanced and not required for your first scan. * [**Configure Workflows:**](/automate-with-ox-workflows/ox-automations.md) Adjust or create workflows to define how issues should be handled, routed, or automated across your teams. * [**Enable Runtime Visibility:**](/ox-cloud/ox-runtime-sensor.md) Connect your runtime environment to help OX understand which components are actually used in production. * [**Fine-tune Policies:**](/ox-policies/policies.md) Review the built-in policies, such as License Policy and other security policies, and confirm they reflect the rules you want to enforce in your organization. --- # 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.ox.security/get-started/planning-next-steps.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.