# Continuous Compliance - Policy

Typical enterprises need to validate various policies during software releases.  Some of the policies are team, corporate, security policies, while others are industry regulations like SOX, HIPPA, FedRamp, etc.  OpsMx ISD integrates with 40+ eco-system tools (e.g., source code repository, CI, SAST/DAST, CD, and Monitoring tools)  and ingests relevant data about the new release available for use by the policy engine.  The policy engine allows the creation of extensible policies that can act on data ingested from various data sources. This capability allows OpsMx ISD to fully automate the policy check and allow for automated approval of releases.

This feature lets you ensure compliance to industry standards and organizational policies while shipping your releases faster to production. Quickly identify the who, what, when, where, and how for your pipelines and applications through audit reports and traces.

![](/files/K23exr6xif8a5f3AnTmu)

It cater to the rigid world of regulatory compliance with static compliance as code – while having the freedom and flexibility to tie policy and control into the rapidly changing IT services. It lets you create accurate coverage with controls by specifying them at an abstract level – while enforcing them at a pipeline level by integrating with Spinnaker.

![](/files/ToTxws1VVqL2oVUfpmkM)


---

# Agent Instructions: 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:

```
GET https://docs.opsmx.com/opsmx-1/opsmx-context-engine/additional-resources/previous-releases/isd-3.12/data-and-intelligence-module-autopilot/continuous-compliance-policy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.