Governance guide

How to govern Operation in Glean

A step-by-step guide to governing Operation in Glean with Rencore: detect, review by owner and severity, and remediate with an audit trail.

Definition

Governing Operation in Glean means finding where it goes wrong, reviewing the findings by owner and severity, and remediating with an audit trail. Rencore covers this concern for Glean with the pre-built controls below, so it becomes a repeatable check rather than a one-off cleanup. The steps that follow apply the same detect, review, remediate loop to Operation.

Steps

  1. Inventory Glean

    Connect Glean and let Rencore build a continuous inventory of its resources, owners, and configuration, so governance starts from what exists rather than a stale export.

  2. Detect with policies

    Turn on the pre-built policies that cover Operation in Glean to surface oversharing, sprawl, and misconfiguration on the first scan, before writing a single custom rule.

  3. Review by owner and severity

    Use the Glean reports to review findings by owner, category, and severity, and to share them with stakeholders who do not have a seat in the platform.

  4. 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.

Glean controls for Operation

Grounded in the Rencore catalog. See the full Glean catalog on the Glean connector page.

  • Glean agent is live and callable

    Enabled agents are callable by users, raising the likelihood that any weakness is exploited

    Severity: Medium
  • Glean agent is disabled

    Detects Glean agents that are currently disabled

    Severity: Low
  • Glean datasource is disconnected

    Detects Glean datasources that are currently disabled or disconnected

    Severity: High
  • Glean datasource not crawled in 7 days

    Detects enabled Glean datasources that have not been crawled in over 7 days

    Severity: Medium
  • Glean datasource has crawl error

    Detects enabled Glean datasources that are in error state

    Severity: High
  • Glean datasource has excessive documents

    Detects Glean datasources with more than 500,000 indexed documents

    Severity: Low
  • Glean agent not updated in 30 days

    Detects enabled Glean agents that have not been updated in over 30 days

    Severity: Low
  • Glean agent has stale configuration

    Detects enabled Glean agents created over 6 months ago and not updated in 3 months

    Severity: Low
  • Glean agent has low satisfaction

    Detects Glean agents where negative feedback (downvotes) exceeds positive feedback (upvotes)

    Severity: Medium
  • Glean agent has zero usage

    Detects Glean agents with no runs during the monitoring period

    Severity: Low
  • Glean agent has high usage but no feedback

    Detects Glean agents with significant usage but zero user feedback

    Severity: Low
  • Deleted Glean agent had recent usage

    Detects deleted Glean agents that were being used before deletion

    Severity: Medium
  • Glean user created too many agents

    Detects Glean users who have created an unusually high number of agents

    Severity: Low
  • Agent feedback summary

    Shows upvotes vs downvotes for Glean agents

  • Disable Glean Agent

    Automatically disables a Glean agent after approval

  • Delete Glean User

    Automatically deletes a Glean user after approval

Explore the full Glean governance catalog | All guides

Trusted by

MAPALBAMVille de LuxembourgWACKERGRUNDFOSAMGENOsramLufthansaThyssenKruppSunrisePattern