IMPORTANT ANNOUNCEMENT: On May 6, 2024, Carbon Black User eXchange (UeX) and Case Management will move to a new platform!
The Community will be in read-only mode starting April 19th, 7:00 AM PDT. Check out the blog post!
You will still be able to use the case portal to create and interact with your support cases until the transition, view more information here!

App Control: How To Format Command Line Exclusions

App Control: How To Format Command Line Exclusions

Environment

  • App Control Console: All Supported Versions
  • App Control Agent: All Supported Versions

Objective

To properly format a Command Line Exclusion in a Rapid Config.

Resolution

Command Line Exclusions (or exceptions) should be added in the format:
<cmdline:*portion of commandline*>process

Example with the Rapid Config Suspicious Command Line Protection N-Z:

This Rapid Config monitors for command lines related to sc.exe by default using:
<cmdline:*create*>sc.exe
This means that anytime the process sc.exe includes create in the command line, the Agent may take action. For instance, this command line would trigger the Rapid Config:
sc create AcmeSoftware binPath=C:\Windows\System32\Drivers\AcmeSoftware.sys type=kernel start=boot error=normal
So a potentially very dynamic Exclusion would become:
<cmdline:*AcmeSoftware*>sc.exe
While a very specific Exclusion would become:
<cmdline:AcmeSoftware binPath=C:\Windows\System32\Drivers\AcmeSoftware.sys type=kernel start=boot error=normal>sc.exe

Additional Notes

  • Further testing should be done to determine how specific to make the Exclusion while still allowing desired functionality.
  • Exclusions may need to be adjusted over time depending on changes by 3rd party vendors.
  • It is recommended to start with Rapid Configs in Report mode before changing to Block to allow an opportunity to test changes.

Related Content


Labels (1)
Tags (2)
Was this article helpful? Yes No
No ratings
Article Information
Author:
Creation Date:
‎01-24-2024
Views:
150
Contributors