Deployment & Update

Deployment Options

CICB supports multiple deployment methods:

  • Official MSI installers for enterprise rollout
  • Silent installation for automated deployment
  • Group Policy deployment
  • Managed deployment through enterprise endpoint tools
  • WinGet distribution where applicable
  • Portable or script-based deployment for specialized environments

Client Deployment

Administrators can preconfigure client connection settings such as server address, port, and API key before rollout. The client.connection file can be deployed with the client package when needed.

Core client-side components may include:

  • client.exe
  • banner.exe
  • ccm.exe when client-side configuration workflows are required
  • client.connection for preconfigured connection settings

MSI and Managed Rollout

For most enterprise deployments, use the official MSI packages with silent install options, Group Policy, or equivalent managed deployment tooling.

Scripted and Portable Rollout

Portable and script-based deployment remains available for air-gapped, lab, VDI, or specialized environments where administrators prefer file-based rollout and custom orchestration.

Updates

Update workflows can be managed using packaged releases, administrative deployment scripts, or your organization's software-distribution platform. The exact update mechanism should align with your operational environment and compliance requirements.

Cyber Intel Classification Banner - Software Upgrade
The example PowerShell script is located in client/tools/updater.ps1 and server/deployment/updater.ps1. (Start from the bottom right fig. to the bottom left fig.)
NOTICE: from the fig. above, both Updater.ps1 scripts already exist under both the Client package and Server package.