Docker on Windows on-premises
You can configure automatic log upload for continuous reports in Cloud App Security using a Docker on Windows.
- Windows 10 (fall creators update)
- Windows Server version 1709+ (SAC)
- Windows Server 2019 (LTSC)
Disk space: 250 GB
RAM: 4 GB
Set your firewall as described in Network requirements
Virtualization on the operating system must be enabled with Hyper-V
- A user must be signed in for Docker to collect logs. We recommend advising your Docker users to disconnect without signing out.
- Docker for Windows is not officially supported in VMWare virtualization scenarios.
- Docker for Windows is not officially supported in nested virtualization scenarios. If you still plan to use nested virtualization, refer to Docker's official guide.
If you have an existing log collector and want to remove it before deploying it again, or if you simply want to remove it, run the following commands:
docker stop <collector_name> docker rm <collector_name>
Log collector performance
The Log collector can successfully handle log capacity of up to 50 GB per hour. The main bottlenecks in the log collection process are:
Network bandwidth - Your network bandwidth determines the log upload speed.
I/O performance of the virtual machine - Determines the speed at which logs are written to the log collector's disk. The log collector has a built-in safety mechanism that monitors the rate at which logs arrive and compares it to the upload rate. In cases of congestion, the log collector starts to drop log files. If your setup typically exceeds 50 GB per hour, it's recommended that you split the traffic between multiple log collectors.
Set up and configuration
Step 1 – Web portal configuration: Define data sources and link them to a log collector
Go to the Automatic log upload settings page.
- In the Cloud App Security portal, click the settings icon followed by Log collectors.
For each firewall or proxy from which you want to upload logs, create a matching data source.
- Click Add data source.
- Name your proxy or firewall.
- Select the appliance from the Source list. If you select Custom log format to work with a network appliance that isn't listed, see Working with the custom log parser for configuration instructions.
- Compare your log with the sample of the expected log format. If your log file format doesn't match this sample, you should add your data source as Other.
- Set the Receiver type to either FTP, FTPS, Syslog – UDP, or Syslog – TCP, or Syslog – TLS.
Integrating with secure transfer protocols (FTPS and Syslog – TLS) often requires additional settings or your firewall/proxy.
f. Repeat this process for each firewall and proxy whose logs can be used to detect traffic on your network. It's recommended to set up a dedicated data source per network device to enable you to:
- Monitor the status of each device separately, for investigation purposes.
- Explore Shadow IT Discovery per device, if each device is used by a different user segment.
- Click Add data source.
Go to the Log collectors tab at the top.
- Click Add log collector.
- Give the log collector a name.
- Enter the Host IP address of the machine you'll use to deploy the Docker. The host IP address can be replaced with the machine name, if there is a DNS server (or equivalent) that will resolve the host name.
- Select all Data sources that you want to connect to the collector, and click Update to save the configuration.
Further deployment information will appear. Copy the run command from the dialog. You can use the copy to clipboard icon, . You will need this later.
Export the expected data source configuration. This configuration describes how you should set the log export in your appliances.
- A single Log collector can handle multiple data sources.
- Copy the contents of the screen because you will need the information when you configure the Log Collector to communicate with Cloud App Security. If you selected Syslog, this information will include information about which port the Syslog listener is listening on.
- For users sending log data via FTP for the first time, we recommend changing the password for the FTP user. For more information, see Changing the FTP password.
Step 2 – On-premises deployment of your machine
The following steps describe the deployment in Windows. The deployment steps for other platforms are slightly different.
Open a PowerShell terminal as an administrator on your Windows machine.
Run the following command to download the Windows Docker installer PowerShell script file:
Invoke-WebRequest https://adaprodconsole.blob.core.windows.net/public-files/LogCollectorInstaller.ps1 -OutFile (Join-Path $Env:Temp LogCollectorInstaller.ps1)
To validate that the installer is signed by Microsoft, see Validate installer signature
To enable PowerShell script execution, run
& (Join-Path $Env:Temp LogCollectorInstaller.ps1)This installs the Docker client on your machine. While the log collector container is installed, the machine will be restarted twice and you will have to log in again. Make sure the Docker client is set to use Linux containers.
After each restart, open a PowerShell terminal as an administrator on your machine, re-run:
& (Join-Path $Env:Temp LogCollectorInstaller.ps1)
Before the installation completes, you will have to paste in the run command you copied earlier.
Deploy the collector image on the hosting machine by importing the collector configuration. Import the configuration by copying the run command generated in the portal. If you need to configure a proxy, add the proxy IP address and port number. For example, if your proxy details are 192.168.10.1:8080, your updated run command is:
(echo db3a7c73eb7e91a0db53566c50bab7ed3a755607d90bb348c875825a7d1b2fce) | docker run --name MyLogCollector -p 21:21 -p 20000-20099:20000-20099 -e "PUBLICIP='192.168.1.1'" -e "PROXY=192.168.10.1:8080" -e "CONSOLE=mod244533.us.portal.cloudappsecurity.com" -e "COLLECTOR=MyLogCollector" --security-opt apparmor:unconfined --cap-add=SYS_ADMIN --restart unless-stopped -a stdin -i mcr.microsoft.com/mcas/logcollector starter
Verify that the collector is running properly with the following command:
docker logs <collector_name>
You should see the message: Finished successfully!
Step 3 - On-premises configuration of your network appliances
Configure your network firewalls and proxies to periodically export logs to the dedicated Syslog port of the FTP directory according to the directions in the dialog. For example:
BlueCoat_HQ - Destination path: \<<machine_name>>\BlueCoat_HQ\
Step 4 - Verify the successful deployment in the Cloud App Security portal
Check the collector status in the Log collector table and make sure the status is Connected. If it's Created, it's possible the log collector connection and parsing haven't completed.
You can also go to the Governance log and verify that logs are being periodically uploaded to the portal.
Alternatively, you can check the log collector status from within the docker container using the following commands:
- Log in to the container by using this command:
docker exec -it <Container Name> bash
- Verify the log collector status using this command:
If you have problems during deployment, see Troubleshooting Cloud Discovery.
Verify that the logs are being uploaded to Cloud App Security and that reports are generated. After verification, create custom reports. You can create custom discovery reports based on Azure Active Directory user groups. For example, if you want to see the cloud use of your marketing department, import the marketing group using the import user group feature. Then create a custom report for this group. You can also customize a report based on IP address tag or IP address ranges.
In the Cloud App Security portal, under the Settings cog, select Cloud Discovery settings, and then select Continuous reports.
Click the Create report button and fill in the fields.
To make sure that the docker installer is signed by Microsoft:
Right click on the file and select Properties.
Click on Digital Signatures and make sure that it says This digital signature is OK.
Make sure that Microsoft Corporation is listed as the sole entry under Name of signer.
If the digital signature is not valid, it will say This digital signature is not valid:
If you run into any problems, we're here to help. To get assistance or support for your product issue, please open a support ticket.