# Overview and Implementation Guide

## About this document set

This is the entry point to the Relyance Policy Center documentation. Start here, then branch out to the guide that matches your role:

| Document | Audience | What's in it |
|---|---|---|
| **Overview and Implementation Guide** (this doc) | Everyone | What the Policy Center is, how obligations, controls, policies, and issues connect, and a rollout plan |
| [Admin Configuration Guide](/docs/policy-center/admin-configuration-guide/) | Privacy, security, AI governance, and GRC teams who run the Policy Center | Enabling obligations, turning policies on, building your own policies, controls, remediation steps, and coverage on individual entities |
| [Issues and AI Review](/docs/policy-center/issues-and-ai-review/) | Everyone who triages issues | The AI review's verdict and trace on an issue, and which issues the Issues list shows by default |
| [Dashboard and Reporting](/docs/policy-center/dashboard-and-reporting/) | Program owners, compliance leads, auditors | Every card on the Policy Center dashboard and how to drill into it |
| [Legal and Compliance Guide](/docs/policy-center/legal-and-compliance-guide/) | Legal, compliance, and audit teams | What continuous control monitoring shows and what it doesn't - no UI steps |
| [FAQ: Policy Center](/docs/policy-center/faq-policy-center/) | Prospects, new customers, sales and CS | Common questions in plain language |

## What is the Policy Center?

The Policy Center is where you tell Relyance which rules your organization is held to, and where Relyance checks your environment against them. It's under **Enforce → Policy Center** in the main navigation.

It's built on four connected pieces:

| Piece | What it is | Who sets it |
|---|---|---|
| **Obligation** | A regulation, standard, or framework you're held to - GDPR, ISO/IEC 27001, the EU AI Act, PCI DSS, HIPAA, and more than 200 others | You enable the ones that apply |
| **Control** | A specific clause of an obligation, such as GDPR Article 32 or an ISO/IEC 27001 Annex A control | Ships with the obligation; you can switch individual controls off |
| **Policy** | A check Relyance runs against your data assets, identities, vendors, services, repositories, AI models, AI agents, MCP servers, and other records. Each policy maps to the controls it tests | Relyance ships reference policies; you turn them on, tune them, or build your own |
| **Issue** | A specific thing a policy found - for example, one unencrypted bucket holding sensitive data - with remediation steps | Raised by policies automatically |

**In practice:** you enable GDPR and ISO/IEC 27001 as obligations, turn on the policies that check their controls, and Relyance starts raising issues wherever your environment falls short. The dashboard then tells you which obligations and controls are failing, where your coverage has gaps, and which issues to fix first.

## How the pieces fit together

**Obligations decide what matters.** Enabling an obligation brings its controls into scope. Disabling one stops enforcement for its controls. You manage them from **Manage Obligations**.

**Policies do the checking.** Relyance ships a catalogue of **Relyance reference** policies grouped into six categories - **Data Posture**, **Identity Posture**, **AI Security Posture**, **Third Party Risk**, **Data Residency and Sovereignty**, and **Privacy** - each mapped to the controls it tests. Most reference policies start switched off so you choose what to enforce. When a policy is on, Relyance evaluates it continuously against what it has discovered in your environment.

**You can build your own.** **Create Policy** opens a three-step builder: choose what to watch and the conditions that make something an issue (or describe the policy in one sentence and let Relyance write the conditions), configure its name, severity, controls, and remediation, then review it before it starts running. A preview shows what the policy would raise if it ran today.

**Issues carry the fix.** Every issue comes with remediation steps - what to do, why it matters, and how - and a step can open a Jira ticket, a GitHub issue, or a Slack message. Relyance AI can review an issue in context and record a verdict, with a summary and a trace of how it was reached; by default the Issues list shows only the issues it's highly confident are a considerable risk, plus any it hasn't reviewed. See [Issues and AI Review](/docs/policy-center/issues-and-ai-review/). Issues appear in **Risks & Issues → Issues**, on the entity they're about, and on any [Risk Register](/docs/risk-register/overview-and-implementation-guide/) risk the policy monitors.

**Coverage closes the loop.** For any single asset, identity, vendor, repository, or AI system, the **Policies & Coverage** tab on its drawer shows which policies watch it and whether each control they monitor is passing, failing, or not yet decided.

## Recommended rollout

### Phase 1 - Enable your obligations
**Owner: Compliance or GRC lead.** Open **Policy Center → Manage Obligations** and enable the regulations and frameworks your organization is actually held to. Review the controls under each and switch off any that don't apply. See [Obligations](/docs/policy-center/admin-configuration-guide/#obligations).

### Phase 2 - Turn on policies
**Owner: Privacy, security, and AI governance teams.** On the **Policies** tab, filter to the obligations you enabled and turn on the reference policies that check them. Adjust each policy's default severity to match your own priorities. Use the dashboard's **Coverage gaps** card to find enabled obligations that still have mapped policies switched off. See [Turning policies on and off](/docs/policy-center/admin-configuration-guide/#turning-policies-on-and-off).

### Phase 3 - Fill the gaps with your own policies
**Owner: Policy owners.** Where a rule specific to your organization isn't covered, build it with **Create Policy**, map it to the controls it tests, and write remediation steps your teams can act on. See [Creating a policy](/docs/policy-center/admin-configuration-guide/#creating-a-policy).

### Phase 4 - Work the issues
**Owner: Asset, system, and vendor owners.** Triage open issues by severity from **Risks & Issues → Issues**, using each issue's AI review **Summary** to prioritize, and check the **Unconfirmed or low confidence** filter for issues that need a person's judgment. Follow the remediation steps, and open tickets in your tracker from the steps that offer them. See [Issues and AI Review](/docs/policy-center/issues-and-ai-review/).

### Phase 5 - Monitor and report
**Owner: Program owner, ongoing.** Use the Policy Center dashboard to track obligation posture, control health, and coverage by jurisdiction, and link policies to the risks they monitor in the Risk Register. See [Dashboard and Reporting](/docs/policy-center/dashboard-and-reporting/).

## Who should read what

- **New to the product or evaluating it?** Start with this doc, then the [FAQ](/docs/policy-center/faq-policy-center/).
- **Setting up and running the Policy Center?** The [Admin Configuration Guide](/docs/policy-center/admin-configuration-guide/) is your reference.
- **Triaging issues?** [Issues and AI Review](/docs/policy-center/issues-and-ai-review/).
- **Reporting on compliance posture?** [Dashboard and Reporting](/docs/policy-center/dashboard-and-reporting/).
- **Legal, compliance, or audit?** Read the [Legal and Compliance Guide](/docs/policy-center/legal-and-compliance-guide/).
