> For the complete documentation index, see [llms.txt](https://docs.themspkb.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.themspkb.com/ai-for-msps/ai-security.md).

# AI Security

Framework for securing AI in MSP environments, covering risks, compliance, governance, and operational safeguards.

### **Introduction**

MSPs adopting AI must treat it as a new class of SaaS with unique risks. This section outlines the major risk areas, the safeguards MSPs should apply, and the policies needed to govern AI responsibly. Each subpage provides detail, examples, and guardrails.

### Subpages Overview

1. [**Risks & Guardrails for AI in MSP Environments**](/ai-for-msps/ai-security/risks-and-guardrails-for-ai-in-msp-environments.md)\
   Explains the main risks (data, operational, business) and practical guardrails (policy, monitoring, oversight).
2. [**Data Handling & Privacy**](/ai-for-msps/ai-security/data-handling-and-privacy.md)\
   Covers how AI tools process, store, and transmit data; residency and training risks; anonymization, tenant isolation, and contractual safeguards.
3. [**Operational Safeguards & Oversight**](/ai-for-msps/ai-security/operational-safeguards-and-oversight.md)\
   Details practical controls: human-in-the-loop enforcement, sandbox testing, incident response, logging, and AI-native security layers.
4. [**AI Governance & Acceptable Use Policies**](/ai-for-msps/ai-security/ai-governance-and-acceptable-use-policies.md)\
   Guidance on writing internal and client-facing policies, managing shadow AI, defining augmentation vs automation, and training users.

### **Bottom Line**

MSPs can safely adopt AI by following structured governance: identify risks, secure data handling, enforce clear policies, and maintain oversight.


---

# 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://docs.themspkb.com/ai-for-msps/ai-security.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.