Box: Configuring the Remediation Actions Integration

Prev Next

Overview

XOps integrations let you take response actions in connected third-party applications as part of an investigation. You can revoke a user’s sessions or disable their account in your single sign-on (SSO) provider or a specific application. These actions help you contain threats by restricting access to affected accounts. To enable these actions, configure a connector for the relevant third-party application.

For more information, see Mitigating Threats in XOps Stories.

To configure the Remediation Actions integration, you need to:

  1. Configure the required settings in the SaaS application

  2. Create the API connector in the CMA

A XOps license is required for Remediation Actions integrations.

Benefits of Connecting Box

The Box Remediation Actions connector lets Cato take response actions on Box users during an investigation. It uses a dedicated Box Platform App with write access, without affecting other Box connectors, such as App Activities and Data Discovery.

  • Disable User: Finds the managed Box user whose login matches the requested email, ignoring letter case, and sets the account status to Inactive. The user can no longer sign in and is signed out of all Box apps. The user's folders and files are hidden from collaborators until the account is reactivated. Collaborators retain their permission levels. The user's content, groups, and seat are retained. If the user is already inactive, the action reports that condition and succeeds.

  • Revoke Sign-In Sessions: Finds the managed user in the same way and requests that Box end all active sessions. The account stays active and the password is unchanged, so the user can sign in again. Box runs session termination as a background job. The action succeeds when Box accepts the job, and the job outcome appears in the Box admin events. The action also runs for an inactive user.

Each action runs on one user, identified by email, and reports Completed or Failed with a reason. Failure reasons include a missing email, no matching user, or a Box error during user lookup or the action request. When Box returns an error code and message, they appear in the result.

Configuring the Box Integration

To configure the integration, create and authorize a dedicated Box Platform App, then create the connector in the Cato Management Application (CMA).

Prerequisites

  • A Box Enterprise license
  • A Box Admin who can create a Platform App and approve it for the enterprise
  • Two-factor authentication enabled on the Box account that creates the app. Without it, the Client Secret is unavailable.

The Manage users scope grants broad permissions over managed users, including changing logins, resetting passwords, changing roles, and managing their enterprise content. Use a dedicated Platform App for this connector. Do not add this scope to the app used by other Box connectors.

Step 1: Configure the Integration in Box

Create a dedicated Platform App with enterprise access and permission to manage users.

To configure the integration in Box:

  1. Log in to the Box Developer Console at https://<your_tenant>.app.box.com/developers/console.
  2. Create a Platform App.
  3. Choose Custom App and enter a name. Select Integration as the purpose and Security & Compliance as the category.
  4. Choose Server Authentication (Client Credentials Grant) and click Create App.
  5. On the General Settings page, copy and save the Enterprise ID so it can be entered into the CMA. Enter this value as the Box Subject ID.
  6. On the Configuration page, click Fetch Client Secret. Copy and save the Client ID and Client Secret so they can be entered into the CMA.
  7. On the Configuration page, set App Access Level to App + Enterprise Access. This setting provides access to users across the enterprise, rather than only the app's own users.
  8. Under Application Scopes, select Manage users, then click Save Changes. This scope is required to look up users by email, disable users, and end sign-in sessions.
  9. Go to the Authorization page and click Review and Submit.
  10. Have the Box Admin approve the app for the enterprise using the email notification.

Store the Client Secret securely. Do not place it in source control, tickets, or chat. If you change the app's scopes, the Box Admin must reauthorize the app from Admin Console > Platform > Platform Apps.

Step 2: Create the API Connector in the CMA

After you have set up an integration with the required application, add the details in the CMA.

For Box, select OAuth2 authentication for Box and enter the credentials from Step 1.

To create the API connector in the CMA:

  1. From the navigation menu, click Resources > Integrations.
  2. Click the Configured Integrations tab.
  3. Click New. The New Integration panel opens.
  4. Select the SaaS Application you want to add.
  5. In the Capability drop-down, select Remediation Actions.
  6. Add the details created during step one.
    • SaaS Application: Box
    • Select OAuth2 authentication for Box
    • Client ID: Enter the Client ID from Step 1
    • Client Secret: Enter the Client Secret from Step 1
    • Box Subject ID (Enterprise ID): Enter the Enterprise ID from Step 1
    • Enter a name for the integration
    • (Optional) Enter a description
  7. Click Save.

The app is visible on the Integrated Apps table with a Connected status.

Known Limitations

  • Managed users only: Both actions look up only managed users in your Box enterprise. External collaborators are not found, even if their login matches the requested email. The action reports that no user matches.

  • Connector service account: The connector's own service account cannot be targeted. Service accounts are not returned by Box user searches. An action targeting that account's login reports that no user matches.

  • Subsequent sign-ins: Subsequent sign-ins are not blocked by Revoke Sign-In Sessions. The account stays active and the password is unchanged. The user, or anyone holding their credentials, can sign in again. Use Disable User to block access.

  • Session termination results: The number of sessions ended is not reported by Revoke Sign-In Sessions. Box accepts the request before the background job runs, without checking it against the user's sessions. Check the Box admin events for the job result.

  • Collaborator access to content: The user's files and folders are hidden from collaborators by Disable User until the account is reactivated. The content remains in Box. To restore sign-in and collaborator access, set the user's status to Active in the Box Admin Console.

  • Connection status: Only sign-in and user lookup are checked by the connection test. Connected confirms that Cato can authenticate with the app's credentials and list enterprise managed users. A missing permission to disable users or end sessions is reported when an action runs, as a Failed result with the Box error.

  • Authentication: Only the OAuth 2.0 client credentials flow is supported.