# Automate AI Governance

To configure your Cortex workspace for AI Governance, we recommend the following actions:

* **Connect Data**: [Ingest data and ensure ownership](#step-1-ingest-data-and-solve-ownership) is assigned to your entities
* **Standardize**: [Configure a Scorecard](#step-2-configure-scorecards-to-track-ai-governance) to enforce standards for AI security controls, visibility, and governance
* **Streamline**: [Automate project scaffolding via Workflows](#step-3-automate-processes-via-workflows) to ensure governance standards are followed, and streamline your abilities to obtain information from Cortex using [Cortex MCP](#step-4-configure-cortex-mcp)
* **Improve**: [Measure the impact of AI on engineering efficiency](#step-5-review-eng-intelligence-metrics-attributable-to-ai), and demonstrate whether AI improves delivery without sacrificing reliability

## Use Cortex features to drive AI Governance

Expand the tiles below to learn about configuring Cortex features to drive AI Governance.

<details>

<summary><strong>Step 1: Ingest data and solve ownership</strong> <span data-gb-custom-inline data-tag="emoji" data-code="1f50c">🔌</span></summary>

{% hint style="success" %}
**Action Items:**

* [**Import your data**](https://docs.cortex.io/ingesting-data-into-cortex/ingesting-data-into-cortex)
* [**Ensure ownership is set**](https://docs.cortex.io/ingesting-data-into-cortex/entities/ownership)
* [**Configure integrations**](https://docs.cortex.io/ingesting-data-into-cortex/integrations)
  {% endhint %}

For AI initiatives to succeed, it is crucial to import your services, resources, infrastructure, and other entities, and to have clear visibility into the ownership of your entities.&#x20;

Connecting your entities to Cortex establishes a single source of truth across your engineering organization. It enables the ability to get timely information from Cortex MCP, track progress via Scorecards, automate Workflows, and gain insights from Eng Intelligence.&#x20;

In addition to the built-in entity types that Cortex supports, you can [create custom entity types](/ingesting-data-into-cortex/entities-overview/entities/adding-entities/entity-types.md) to represent your AI-related entities. For example, you might want to create a type called "AI Models" to categorize models.

<figure><img src="/files/wvK3FxFDwsBH1WbesLgy" alt=""><figcaption></figcaption></figure>

Setting ownership of entities ensures that every service and system is clearly linked to accountable teams or individuals, enabling faster incident response, reducing handoff friction, and making it possible to enforce standards consistently. &#x20;

{% hint style="info" %}
We recommend [adding a group](/ingesting-data-into-cortex/entities-overview/entities/groups.md) called `ai-enabled` to your AI-enabled services. This will allow you to filter your AI-enabled services in the [relationship graph](/ingesting-data-into-cortex/entities-overview/entities/relationship-graph.md), [Scorecards](/standardize/scorecards.md), and other places in Cortex where filters are supported.
{% endhint %}

#### Relevant integrations

To focus on driving AI Governance, Cortex recommends integrating with tools that provide visibility and control over code, project management, CI/CD, observability, and documentation. This enables visibility into which AI tools are being used and how they're managed.

Make sure you have configured integrations for the following categories:

* **Version control**: [Azure DevOps](https://docs.cortex.io/ingesting-data-into-cortex/integrations/azuredevops), [Bitbucket](https://docs.cortex.io/ingesting-data-into-cortex/integrations/bitbucket), [GitHub](https://docs.cortex.io/ingesting-data-into-cortex/integrations/github), [GitLab](https://docs.cortex.io/ingesting-data-into-cortex/integrations/gitlab)
  * Ensure policies are being enforced in version control systems
* **Project management**:  [GitHub](https://docs.cortex.io/ingesting-data-into-cortex/integrations/github), [Jira](https://docs.cortex.io/ingesting-data-into-cortex/integrations/jira), [Azure DevOps](https://docs.cortex.io/ingesting-data-into-cortex/integrations/azuredevops), [ClickUp](https://docs.cortex.io/ingesting-data-into-cortex/integrations/clickup)
  * Monitor and control the ethical use of AI within projects, ensuring data integrity and compliance
* **CI/CD**: [ArgoCD](https://docs.cortex.io/ingesting-data-into-cortex/integrations/argocd), [Azure DevOps](https://docs.cortex.io/ingesting-data-into-cortex/integrations/azuredevops), [Bitbucket](https://docs.cortex.io/ingesting-data-into-cortex/integrations/bitbucket), [Buildkite](https://docs.cortex.io/ingesting-data-into-cortex/integrations/buildkite), [CircleCI](https://docs.cortex.io/ingesting-data-into-cortex/integrations/circleci), [GitHub](https://docs.cortex.io/ingesting-data-into-cortex/integrations/github), [GitLab](https://docs.cortex.io/ingesting-data-into-cortex/integrations/gitlab), [Jenkins](https://docs.cortex.io/ingesting-data-into-cortex/integrations/jenkins)
  * Identify pipelines deploying AI models and ensure the models go through testing and validation
* **Observability**: [Coralogix](https://docs.cortex.io/ingesting-data-into-cortex/integrations/coralogix), [Datadog](https://docs.cortex.io/ingesting-data-into-cortex/integrations/datadog), [Dynatrace](https://docs.cortex.io/ingesting-data-into-cortex/integrations/dynatrace), [Google Observability Cloud](https://docs.cortex.io/ingesting-data-into-cortex/integrations/google), [Instana](https://docs.cortex.io/ingesting-data-into-cortex/integrations/instana), [New Relic](https://docs.cortex.io/ingesting-data-into-cortex/integrations/newrelic), [Prometheus](https://docs.cortex.io/ingesting-data-into-cortex/integrations/prometheus), [ServiceNow Cloud Observability (formerly Lightstep)](https://docs.cortex.io/ingesting-data-into-cortex/integrations/lightstep), [Splunk Observability Cloud (formerly SignalFX)](https://docs.cortex.io/ingesting-data-into-cortex/integrations/splunk-observability), [Sumo Logic](https://docs.cortex.io/ingesting-data-into-cortex/integrations/sumologic)
  * Link incidents back to AI-driven components to track risk and enforce reliability standards
* **External docs**: Cortex also recommends l[linking to runbooks and documentation](https://docs.cortex.io/ingesting-data-into-cortex/entities/external-docs) for your entities, ensuring your users have access to critical information.
  * Use Scorecards to ensure that your entities contain links to compliance docs for AI usage.

With your data in Cortex, you have a jumping-off point to start driving AI Governance.

</details>

<details>

<summary><strong>Step 2: Configure Scorecards to track AI governance</strong> <span data-gb-custom-inline data-tag="emoji" data-code="1f4cb">📋</span></summary>

{% hint style="success" %}
**Action Item:** [**Create a Scorecard**](https://docs.cortex.io/standardize/scorecards/create) **for AI Governance**
{% endhint %}

Scorecards automate the process of checking whether services meet criteria for your AI Governance goals.\
\
Cortex's AI Governance template includes a set of predefined rules which can be customized based on your organization's requirements, infrastructure, and goals. It is structured into three levels — Bronze, Silver, and Gold — with each representing increasing levels of governance.&#x20;

The Scorecard template contains rules that check for industry best practices, such as:

* PR reviews required from codeowners, ensuring humans review AI-written code
* Automated security testing in CI/CD
* Incident response plan for AI security

#### Prerequisites

One of the rules in this template requires a custom data field on entities to track whether entity owners have read and reviewed the [ATLAS Matrix](https://atlas.mitre.org/matrices/ATLAS). Before using this rule, [create a custom data field](/ingesting-data-into-cortex/entities-overview/entities/custom-data.md) named `owners-reviewed-mitre-atlas-matrix`.&#x20;

#### Step 2.1: Create the Scorecard and configure the basics

1. On the [**Scorecards** page](https://app.getcortexapp.com/admin/scorecards) in your workspace, click **Create Scorecard**.
2. On the `AI Governance` template, click **Use**. <br>

   <div align="left"><figure><img src="/files/kE90XkuZn6iIUyqIoGtJ" alt="Click Create Scorecard, then click the AI Governance template."><figcaption></figcaption></figure></div>
3. Configure basic settings, including the Scorecard's name, unique identifier, description, and more.
   * Learn about configuring the basic settings in the [Creating a Scorecard documentation](https://docs.cortex.io/standardize/scorecards/create#step-1-configure-the-basic-scorecard-fields).

#### Step 2.2: Review and modify the rules

While Cortex's template is based on common industry standards, you may need to adjust the rules based on which tools you use and how your organization prioritizes standards and requirements. You can reorder, delete, and edit rules, you can add more rules to a level, and you can assign more points to a rule to signify its importance.

When adding or changing the template rules, you can select from a list of available pre-built rules. Behind each rule is a [Cortex Query Language (CQL) ](https://docs.cortex.io/standardize/cql)query; you can also write your own queries to further refine your rules.&#x20;

</details>

<details>

<summary><strong>Step 3: Automate processes via Workflows</strong> <span data-gb-custom-inline data-tag="emoji" data-code="2699">⚙️</span></summary>

{% hint style="success" %}
**Action item:** [**Configure Workflows**](https://docs.cortex.io/streamline/workflows/create)
{% endhint %}

You can use Workflows to streamline and standardize processes relating to your AI governance initiatives.

#### Workflows to establish adherence to best practices

* When Scaffolding new services, you can use templates to ensure that every new service starts with baseline standards (e.g., runbooks include AI-driven diagnostics, services integrate AI-based anomaly detection, risk assessment files are included, etc.).&#x20;
  * See the documentation on [registering a Scaffolder template](https://docs.cortex.io/streamline/workflows/scaffolder) and [configuring a Scaffolder block](https://docs.cortex.io/streamline/workflows/blocks#scaffolder).
  * As a best practice, your Scaffolder template should include files for:
    * AI service configuration security
    * AI security documentation and guidelines
    * Data privacy and PII protection measures
    * External AI vendor risk assessments
    * AI model access controls and authentication

Note that the [AI Governance Scorecard](#step-2-configure-scorecards-to-track-ai-governance) template checks for the files listed above.

</details>

<details>

<summary><strong>Step 4: Configure Cortex MCP</strong> <span data-gb-custom-inline data-tag="emoji" data-code="1f916">🤖</span></summary>

{% hint style="success" %}
**Action Item:** [**Configure Cortex MCP**](https://docs.cortex.io/get-started/mcp)
{% endhint %}

[Cortex MCP](https://docs.cortex.io/get-started/mcp) can significantly help boost efficiency by providing instant, conversational access to critical service and team information directly from your MCP client. Use Cortex MCP to ask questions about visibility, compliance, accountability, and risks.&#x20;

* **It provides real-time, structured answers**: Ask questions like "What AI models are currently deployed in our environment?" or "Give me next steps for my AI Governance Scorecard." MCP fetches the data in real time from Cortex's API, ensuring accurate and up-to-date information about service health, ownership, and operational readiness.
* **It gives you quick access to your centralized data**: Efficiency goals can be slowed down by uncertainty over who owns models, pipelines, and other AI services. Use the MCP to quickly find out which teams are accountable for each tool in your environment.
* **It enables quick access to Scorecard details**: If you implement Scorecards to measure AI-related initiatives, you can use the MCP to understand quickly how healthy your services are and how you can improve scores.

</details>

<details>

<summary><strong>Step 5: Review Eng Intelligence metrics attributable to AI</strong> <span data-gb-custom-inline data-tag="emoji" data-code="1f4c8">📈</span></summary>

{% hint style="success" %}
**Action Items:**&#x20;

* [**Review Eng Intelligence metrics**](https://docs.cortex.io/improve/eng-intelligence) **and establish baselines.**
  {% endhint %}

When focusing on an AI governance use case, you might want to know whether AI tools are improving efficiency without sacrificing reliability.&#x20;

Use Eng Intelligence features — the [DORA dashboard](https://docs.cortex.io/improve/eng-intelligence/dora-dashboard), [Velocity Dashboard](https://docs.cortex.io/improve/eng-intelligence/velocity-dashboard), and [Metrics Explorer](https://docs.cortex.io/improve/eng-intelligence/metrics-explorer) —  to understand how well teams are performing before and after AI initiatives have been implemented.

<figure><img src="/files/hKWjA2IrZMv4MweKoNpz" alt="Review trends in Eng Intelligence graphs and metrics." width="563"><figcaption></figcaption></figure>

Review baselines in areas such as cycle time, incident frequency, and time to resolution, and review the trends over time as AI initiatives are adopted.&#x20;

This visibility gives insight into where teams can improve efficiency across the software development lifecycle and whether the addition of AI tooling is impacting delivery and reliability.

</details>

## AI Governance in action

Learn about what ongoing AI Governance looks like in [AI Governance in action](/solutions/ai-governance/in-action.md).


---

# 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.cortex.io/solutions/ai-governance/configure.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.
