How to govern SharePoint
A step-by-step guide to governing SharePoint with Rencore: detect with 32 policies, review with 11 reports, and remediate with 4 automations.
Governing SharePoint means keeping its access, configuration, and lifecycle under continuous control rather than reacting after something breaks. Rencore governs SharePoint with 32 pre-built policies, 11 reports, and 4 automations, so teams can detect risk, review posture, and remediate with an audit trail. The steps below turn that coverage into a repeatable routine.
Steps
-
Inventory SharePoint
Connect SharePoint and let Rencore build a continuous inventory of its resources, owners, and configuration, so governance starts from what exists rather than a stale export.
-
Detect with policies
Turn on the pre-built policies that cover SharePoint to surface oversharing, sprawl, and misconfiguration on the first scan, before writing a single custom rule.
-
Review by owner and severity
Use the SharePoint reports to review findings by owner, category, and severity, and to share them with stakeholders who do not have a seat in the platform.
-
Remediate and automate
Apply automations to fix findings at scale, route sensitive changes through approvals, and keep every action reversible and logged for the audit trail.
Recommended SharePoint policies
Grounded in the Rencore catalog. See the full SharePoint catalog on the SharePoint connector page.
-
SharePoint file is shared with external users
Detects SharePoint files that have been shared externally, potentially exposing sensitive data.
Severity: High -
SharePoint site is inactive for more than 90 days
Detects SharePoint sites without activity for a defined period, which could impact content accuracy.
Severity: Medium -
Classic sites
Shows classic SharePoint sites
Severity: Information -
Unused Classic sites
Shows classic SharePoint sites
Severity: Low -
Site collection is unused with more than 1 GB
Shows sites which have not been used in last 90 days and are larger than 1 GB
Severity: Medium -
SharePoint agent is not approved
Identifies SharePoint agents that have not been reviewed or approved before use, posing security risks.
Severity: Low -
SharePoint agent references confidential site without approval
Identifies SharePoint agents connected to confidential sites without approval, increasing the risk of unauthorized AI-generated responses.
Severity: High -
SharePoint site has broken permission inheritance
Detects SharePoint sites where permission inheritance is broken, increasing security risks.
Severity: Medium -
SharePoint site collection lacks sensitivity label
Detects SharePoint site collections missing sensitivity labels, increasing data security risks.
Severity: Medium
