Carbon Black App Control and ASD ACSC Essential 8 – Implementation Guide

Carbon Black App Control and ASD ACSC Essential 8 – Implementation Guide

Australian Signals Directorate | Australian Cyber Security Centre | Application Control | Compliance Overview

Purpose of this document is to provide a comprehensive Carbon Black App Control implementation and  configuration guide to comply with ASD ACSC Essential 8.

Carbon Black App Control is used to lock down endpoints, servers, and critical systems, prevent unwanted changes, and ensure continuous compliance with regulatory mandates, including the application control mitigation strategy of the ASD ACSC Essential 8. 

This How-To Guide offers a comprehensive outline of the procedures an organisation can adopt to reach Maturity Level 1 (ML1), ML2, and/or ML3 of ASD ACSC’s Essential 8 Mitigation strategy for application control. By adhering to this guide, users of Carbon Black App Control can formulate and implement a systematic plan for the gradual implementation of Carbon Black App Control at High Enforcement throughout their production environment.

Get the document from this GitRepo – Carbon Black App Control and ASD ACSC Essential 8 – https://github.com/RockAfeller2013/CarbonBlackAppControlE8Guide

Additional resources;

You can use dascli on an endpoint that is not connected to the App Control server, but only in a limited way.

Key distinction

  • Full App Control policies are created, assigned, and managed by the server.
    These policies cannot be exported from the server and imported into a disconnected agent.
  • dascli policy can manage local rule types only on the endpoint, such as:
    • Path rules
    • Script rules
    • Object rules
    • Registry rules
    These rules are stored in an XML file and are applied locally, even when the agent is offline.

What this means

  • You can use dascli to add or change local rules on an offline endpoint.
  • You cannot use dascli to fully copy or recreate a server-side policy or its assignments on a disconnected agent.
  • When the agent reconnects, the server-managed policy may override any local changes.

Typical offline use cases

  • Pre-stage specific local rules on the endpoint while it is offline.
  • Use local approvals or temporary overrides so the system can operate safely until it reconnects to the server.

Screenshots:

  • Test machine is offline and the scripts runs normally
  • Below command is run to import the rule:
  • After this the script is blocked from running
  • The below command is then used to remove the rule, after which the script is able to execute again.

– How to Collect Logs for Server Upgrade Failures – https://knowledge.broadcom.com/external/article?articleNumber=288340

– Server Install Log Location – https://knowledge.broadcom.com/external/article?articleNumber=291206

– Upgrade from Server Version 8.10.0 or Lower to the Latest One Takes Very Long Time to Complete – https://knowledge.broadcom.com/external/article/286569/upgrade-to-server-version-8104-and-highe.html

– Collect Database Logs for Performance Issues (SQL Server) – https://knowledge.broadcom.com/external/article?articleNumber=286421

https://knowledge.broadcom.com/external/article/388701/console-inaccessible-with-demo-expired-m.html

– https://knowledge.broadcom.com/external/article/286713/app-control-after-license-change-there-i.html