This chapter describes Rapid Configs, which are sets of rules that can be used to accomplish tasks such as application optimization, operating system and application hardening, and approval of files delivered by software distribution systems.

Carbon Black App Control includes a variety of individual rules that you can use to monitor or protect your endpoints. In most cases, these rules perform a narrowly defined task, such as reporting or blocking the execution of files at a location you specify.

A Rapid Config (short for rapid configuration) is a set of rules that you can use to achieve more complex goals such as optimizing the interaction of Carbon Black App Control and a specific application, hardening of operating systems and applications, and approval of files created or delivered by certain tools or pathways. For example, a Rapid Config for a specific application might include rules that ignore writes to specified folders while approving certain files so that the application can be more easily used.

A single Rapid Config might combine actions that you could have taken by creating several individual rules. On the other hand, it might be entirely composed of internal rules not exposed in the user interface, or it might be a combination of internal and visible rules.

Rapid Configs are created by Carbon Black and are built into Carbon Black App Control. Although you cannot create a Rapid Config, some of them allow (and require) configuration so that they work properly in your environment. Other Rapid Configs are completely configured and require only that you enable them. You can enable any of these configurations to take advantage of their efficiency or protection features, or disable them if they interfere with activities you need to perform on the server or an endpoint.

To keep your Rapid Configs current, you can allow automatic updating by Carbon Black File Reputation. This feature is enabled by default when the connection between your App Control Server and Carbon Black File Reputation is enabled.