Code42 CLI end-of-life FAQ

Overview

To improve security, functionality, and to focus on managing insider risks, the Code42 CLI has been replaced by the Incydr command-line interface (CLI).

The Code42 CLI reaches end-of-support on January 1, 2026, and reaches end-of-life on January 1, 2027.

For more details, review the FAQs below.

General

Why is the Code42 CLI being discontinued?

• The Code42 CLI is being discontinued because it was focused primarily on backup features and offered a limited set of functions and authentication options.
• By transitioning to the Incydr CLI, you gain access to a modern CLI designed specifically for interacting with the Incydr API, offering enhanced security features and a comprehensive command structure for managing security-related tasks. The Incydr CLI also offers more robust functionality, improved authentication methods, and a design tailored to managing insider risks.

Timing

What is the end-of-support date for the Code42 CLI, and what happens on this date?

• The end-of-support date for the Code42 CLI is January 1, 2026.
• After this date, Incydr will no longer provide technical support, bug fixes, or updates to the Code42 CLI. While the Code42 CLI may continue to function after this date, we cannot assist you with any issues that may arise.

What is the end-of-life date for the Code42 CLI, and what happens on this date?

• The end-of-life date for the Code42 CLI is January 1, 2027.
• On this date, the Code42 CLI functionality will be removed from Incydr. All integrations, scripts, and other tools using the Code42 CLI will stop working. To prevent any interruptions to service, make sure to migrate to the Incydr CLI before this date.

Transitioning to the Incydr CLI

What is the Incydr CLI?

• The Incydr CLI tool offers a way to interact with your Incydr environment without using the Incydr console or making direct API calls. The Incydr CLI is designed specifically for interacting with the Incydr API, offering enhanced security features and a comprehensive command structure for managing security-related tasks.
• For example, you can use the Incydr CLI to ingest Incydr file events, alerts, and audit log data into an external security information and event management (SIEM) tool. The Incydr CLI can also help you manage watchlists, alerts, trusted activity, cases, and more.

What do I need to do to prepare for this transition?

• Identify any integrations, scripts, and other tools using the Code42 CLI in your environment.
• Plan and execute a migration to the Incydr CLI as soon as possible.
• Refer to the Incydr CLI documentation or contact our Technical Support Engineers if you need additional assistance.

What are the benefits of migrating to the Incydr CLI?

• The Incydr CLI offers enhanced security features and a comprehensive command structure for managing security-related tasks. Compared to the Code42 CLI, the Incydr CLI also offers more robust functionality, improved authentication methods, and a design tailored to managing insider risks.

Will Incydr provide migration support?

• Yes, migration support is available. First, review the Incydr CLI the documentation in our Developer Portal. If you need additional assistance, contact our Technical Support Engineers for support.

What happens if I don’t migrate to the Incydr CLI by the end-of-life date?

• If you do not migrate by January 1, 2027, all integrations, scripts, and other tools using the Code42 CLI will stop working. This will cause service interruptions for any functionality using the Code42 CLI.