# FAQ: Policy Center

*Audience: prospects evaluating Relyance, and new customers getting started.*

## What is the Policy Center, in one paragraph?

It's where you tell Relyance which regulations and frameworks you're held to and turn on the policies that check them. Each policy tests specific controls - such as a GDPR article or an ISO/IEC 27001 control - against your data assets, identities, vendors, services, repositories, and AI systems, and raises an issue with remediation steps wherever something falls short. A dashboard shows your posture per obligation, control, category, and jurisdiction. Find it under **Enforce → Policy Center**.

## What's the difference between an obligation, a control, and a policy?

An **obligation** is a regulation, standard, or framework, like GDPR or PCI DSS. A **control** is one clause of it. A **policy** is the check Relyance runs to test one or more controls against your environment. You enable obligations, and policies mapped to their controls do the checking.

## Which regulations and frameworks are included?

More than 200, spanning privacy laws (GDPR, UK GDPR, CCPA and other US state laws, LGPD, PIPEDA, and more), security standards (ISO/IEC 27001, SOC 2, PCI DSS, NIST SP 800-53, NIST CSF, CIS Controls, the HIPAA Security Rule), and AI frameworks (the EU AI Act, ISO/IEC 42001, the NIST AI RMF, OWASP AI lists). See them all under **Policy Center → Manage Obligations**.

## Are policies on by default?

Most Relyance reference policies start switched off, so you choose what to enforce. Turn them on from the **Policies** tab, typically starting with the policies mapped to the obligations you've enabled. The dashboard's **Coverage gaps** card shows where policies are still off.

## Can I write my own policies?

Yes. **Create Policy** opens a builder where you choose what to watch and set the conditions for an issue, or describe the policy in a sentence with **Define with AI**. You then set its name, severity, controls, issue title, and remediation steps, and review it before it starts running. See [Creating a policy](/docs/policy-center/admin-configuration-guide/#creating-a-policy).

## Can I change a Relyance reference policy?

You can turn it on or off, change its default severity, and disable individual controls for it. To change what it checks, use **Clone to edit** to make your own copy.

## What happens when I turn a policy off?

It stops being evaluated, stops enforcing its controls, and its existing open issues are closed. You can turn it back on at any time.

## How does a policy help me fix what it finds?

Every issue comes with remediation steps - what to do, why it matters, and how. Steps can open a Jira ticket, a GitHub issue, or a Slack message, so the fix lands where your teams already work.

## What is the AI review on an issue?

Relyance AI can review an issue in context and decide whether it's a considerable risk. Reviewed issues open with a **Summary** card: the verdict, the key signal, how the verdict was reached, and - under **Details** - a step-by-step trace of the review. See [Issues and AI Review](/docs/policy-center/issues-and-ai-review/).

## Why don't I see every issue in the Issues list?

By default the list shows only issues the AI review judged a considerable risk with high confidence, plus issues it hasn't reviewed. Issues it was less sure about are under **Unconfirmed or low confidence** in the **AI review** filter, and ones it judged not a considerable risk are under **Not a considerable risk**. Pick those values in the filter to see them.

## How do I see whether a specific system is covered?

Open the system's drawer - a data asset, identity, vendor, repository, AI model, AI agent, or MCP server - and select **Policies & Coverage**. It lists every policy watching it and whether each control is **Passing**, **Failing**, or **Not decided**.

## How does the Policy Center relate to the Risk Register?

Policies are how Relyance monitors the risks in your [Risk Register](/docs/risk-register/overview-and-implementation-guide/). Link a policy to a risk and its issues show on the risk. A policy's drawer also lists the register risks it monitors.

## How often are policies evaluated?

Enabled policies are evaluated automatically, and a new or edited policy starts evaluating as soon as it's saved. You can also force a full re-evaluation with **Run policy evaluation** from the **Policies** tab's menu.

## Does a clean dashboard mean we're compliant?

Not on its own. It means the policies you've enabled found nothing to raise in the systems Relyance is connected to. Many obligations also include procedural and contractual requirements that need other evidence. See the [Legal and Compliance Guide](/docs/policy-center/legal-and-compliance-guide/).
