> For the complete documentation index, see [llms.txt](https://www.mlcompendium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.mlcompendium.com/ai-engineering/tbd.md). # DevSecOps Definitions Security has to sit inside the delivery loop, not after it. This page gives three definitions of DevSecOps, moving from the vendor view, to the pipeline view, to the market view. The same notes are in [Definitions](/ai-engineering/definitions.md). The first definition starts from DevOps itself. [What is DevSecOps, by Red Hat](https://www.redhat.com/en/topics/devops/what-is-devsecops) argues that to take full advantage of the agility and responsiveness of DevOps, IT security must play a role in the full life cycle of your apps. [What is DevSecOps?](https://medium.com/@xenonstack/what-is-devsecops-and-benefits-of-adopting-devsecops-1c47e7616722) is Xenonstack's version of the same idea at the pipeline level: security for the application and infrastructure built on the DevOps methodology, with everything automated and security checks starting from the beginning of the pipeline. The last view explains why anyone is paying for this. [Explained, a venture-capital perspective](https://medium.com/inside-inovo/devsecops-explained-venture-capital-perspective-cb5593c85b4e) Kris Przybylak looks at DevSecOps as a market, forecast in that post to grow over 30% a year and reach almost USD 6 billion in 2023. --- # 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://www.mlcompendium.com/ai-engineering/tbd.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.