Threat Report: Exposing Malware in Linux-Based Multi-Cloud Environments | Download Now

Cb Protection v8.0.0 - User Guide

Cb Protection v8.0.0 - User Guide

Document Version: 8.0.0.h (April 2018)

This documentation provides information for administrators, incident responders, and others who will operate the Cb Protection Console. Staff who manage Cb Protection activities should be familiar with the Microsoft Windows operating system, web applications, desktop infrastructure (especially in-house procedures for software roll-outs, patch management, and anti-virus software maintenance), and the effects of unwanted software. In addition, if you intend to use features that integrate Cb Protection and Active Directory, you should be familiar with Active Directory concepts and use. Although not necessary for day-to-day users, knowledge of SQL Server management is required for the administrator of the Cb Protection database server at your site. Cb Protection administrators should also be familiar with the operating systems of clients managed by the Cb Protection server, as well as the software installed on them.


See the Comments below for changes in this version.

Labels (1)

Change to this document for version 8.0.0.h (April 2018)

  • Added a "List of Tasks" after the table of contents.
  • In the "Custom Rules chapter, corrected an example of the "OnlyIf:Company" macro.
  • In the "Managing Computers" chapter, modified the description of imagex.exe downloads  (for trusted approvals of WIMs) to include different download locations for different Windows versions.
  • In the "Management Computers" chapter, corrected one of the AV exclusion paths for Mac agents:  The correct path for current versions is /Library/Application Support/com.bit9.agent (replacing /Library/Caches/com.bit9.agent).
  • Other minor editing changes were made.


Would this be considered current for Patch 7?


Yes, cool_breeze. It is not marked for a particular patch release because it may remain the correct version for multiple releases, and we don't want to keep re-releasing it just to change the patch number on the cover when no actual content has changed.

We tag the latest version with the "current release" on this page (see above). It's always possible that we forget to update this, but in general the idea is that you can trust that tag to tell you that the document delivered through this page applies to the most recent software release. Hope that's clear -- if not, please let us know. Version control is always an adventure


That makes good enough sense.

Thanks for all the work you folks do on documentation.

You're welcome, and thanks for the feedback!


Can we download this user guide pdf?

Article Information
Creation Date: