> For the complete documentation index, see [llms.txt](https://docs.ozone.one/ozone-end-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ozone.one/ozone-end-user-guide/documentation/devsecops/shift-left-policy-management.md).
# Shift Left Policy Management
In the context of policy management, shifting left means bringing policy definition, enforcement, and monitoring closer to the beginning of the SDLC, allowing organizations to identify and mitigate risks and ensure compliance requirements are met from the outset. This proactive approach helps to prevent security vulnerabilities and compliance violations from propagating throughout the development process, reducing the potential impact and cost of addressing them later.
Key aspects of shift left policy management include:
1. **Policy Definition**: Policies governing security, compliance, and governance requirements are established early in the development process, often in collaboration with security and compliance teams.
2. **Automation**: Automated tools and processes are integrated into the development pipeline to enforce policies, such as static code analysis, automated testing, and continuous integration/continuous deployment (CI/CD) pipelines.
3. **Developer Empowerment**: Developers are empowered with the knowledge and tools to understand and comply with policies effectively. This may involve providing training, documentation, and easy-to-use tools for policy enforcement.
4. **Continuous Monitoring**: Policies are continuously monitored throughout the development lifecycle to ensure compliance and identify any deviations or violations promptly.
5. **Feedback Loop**: Shift left policy management emphasizes a feedback loop where insights gained from monitoring and enforcement are used to refine policies and improve processes iteratively.\
\
By implementing shift left policy management, organizations can enhance their overall security posture, reduce compliance risks, and improve the efficiency of their software development processes by addressing security and compliance concerns early and consistently throughout the development lifecycle.
---
# 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.ozone.one/ozone-end-user-guide/documentation/devsecops/shift-left-policy-management.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.