Pre-built Policies
602 governance policies covering security, costs, sprawl, operations, and compliance, pre-built per connector, severity-graded, with recommended policies active by default.
Pre-built Policies are Rencore's curated catalog of 602 detection rules tuned to each connected service. Each policy has severity, category, target service, a recommended-action description, and an is_recommended flag. Recommended policies activate automatically on the first scan, so the platform produces meaningful findings before any custom configuration.
What gets shipped
The 602 policies break down roughly: ~200 covering Security and External Access, ~150 covering Sprawl and Operation, ~100 covering Costs and Adoption, ~80 covering AI-specific scenarios across Claude, OpenAI, GitHub Copilot and similar tools, and the remainder covering connector-specific operational concerns like mailbox quotas, redirect rules, or workflow execution failures.
How they run
Each policy evaluates every relevant object in the tenant against its rule on every scan cycle. A SharePoint policy looks at every site collection; an Exchange policy looks at every mailbox; a Claude policy looks at every workspace, user, and API key. Matching objects appear as violations with severity, description, recommended action, and a link to the affected object.
Violations feed dashboards, reports, segments, and automations, so the same finding can trigger a Teams notification, surface in this week’s scheduled report to compliance, and queue an approval-gated remediation in the same cycle.
Customizing without forking
A pre-built policy is a starting point, not a hard contract. Each policy is editable, you can change severity, refine the condition, tune the description, or disable it entirely. Custom policies use the same engine and live alongside pre-built ones in the same library. No fork, no separate “custom rules” experience.
Frequently asked questions
How do Rencore policies work?
What is Rencore governance?
How does Rencore detect oversharing?
Trusted by