> For the complete documentation index, see [llms.txt](https://documentations.seclea.com/nist-ai-risk-management-framework/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentations.seclea.com/nist-ai-risk-management-framework/grn-6-managing-3rd-party-risk/grn-6.2-3rd-party-contingency.md).

# GRN 6.2 - 3rd Party Contingency

NIST AI RMF (in the playbook companion) states:

> ### GOVERN 6.2 
>
> Contingency processes are in place to handle failures or incidents in third-party data or AI systems deemed to be high-risk. <br>
>
> <details>
>
> <summary><strong>About</strong></summary>
>
> To mitigate the potential harms of third-party system failure, organizations should implement policies and procedures that include redundancies for covering third-party functions.
>
> </details>
>
> <details>
>
> <summary><strong>Actions</strong></summary>
>
> * Establish policies for handling third-party system failures to include consideration of redundancy mechanisms for vital third-party AI systems.
> * Verify that incident response plans address third-party AI systems.
>
> </details>
>
> <details>
>
> <summary><strong>Transparency and Documentation</strong></summary>
>
> **Organizations can document the following:**
>
> * To what extent does the plan specifically address risks associated with acquisition, procurement of packaged software from vendors, cybersecurity controls, computational infrastructure, data, data science, deployment mechanics, and system failure?
> * Did you establish a process for third parties (e.g. suppliers, end-users, subjects, distributors/vendors or workers) to report potential vulnerabilities, risks or biases in the AI system?
> * If your organization obtained datasets from a third party, did your organization assess and manage the risks of using such datasets?
>
> </details>


---

# 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://documentations.seclea.com/nist-ai-risk-management-framework/grn-6-managing-3rd-party-risk/grn-6.2-3rd-party-contingency.md?ask=<question>&goal=<user_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.