Governance guide

How to govern Box

A step-by-step guide to governing Box with Rencore: detect with 26 policies, review with 12 reports, and remediate with 4 automations.

Definition

Governing Box means keeping its access, configuration, and lifecycle under continuous control rather than reacting after something breaks. Rencore governs Box with 26 pre-built policies, 12 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

  1. Inventory Box

    Connect Box 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 Box to surface oversharing, sprawl, and misconfiguration on the first scan, before writing a single custom rule.

  3. Review by owner and severity

    Use the Box 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.

Recommended Box policies

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

  • Shared link is open to anyone

    Open shared links are reachable by any internet user, raising the likelihood that a weakness in the shared content is exploited.

    Severity: High
  • File reachable via open shared link

    Files exposed by an open (public) shared link are reachable by anyone with the URL, raising the likelihood of exploitation.

    Severity: High
  • Folder reachable via open shared link

    Folders exposed by an open (public) shared link are reachable by anyone with the URL, raising the likelihood of exploitation.

    Severity: High
  • User exempt from login verification

    Users exempt from login verification bypass 2FA enforcement and are a more readily exploited entry point, raising the likelihood axis.

    Severity: Medium
  • Shared link open to anyone

    Detects Box shared links with access set to 'open' (any internet user).

    Severity: High
  • Folder allows external collaboration

    Detects folders that have collaborations and are not restricted to the enterprise.

    Severity: High
  • Open shared link without password

    Detects open shared links that have no password protection.

    Severity: Medium
  • Inactive user still owns content

    Detects inactive users with non-zero storage used (still owning files).

    Severity: High
  • Admin exempt from login verification

    Detects admin or co-admin role holders that bypass 2FA enforcement.

    Severity: High
  • Folder inactive for over a year

    Detects folders whose content has not been modified in 365+ days.

    Severity: Low
  • File owned by inactive user

    Detects active files whose owner is an inactive Box user.

    Severity: Medium
  • Folder not covered by a retention policy

    Detects folders that are not assigned to any retention policy.

    Severity: Medium
Explore the full Box governance catalog | All guides

Trusted by

MAPALBAMVille de LuxembourgWACKERGRUNDFOSAMGENOsramLufthansaThyssenKruppSunrisePattern