Configure automatic log upload for continuous reports on a virtual appliance - Deprecated
Applies to: Microsoft Cloud App Security
It is highly recommended to configure log upload using Docker for more flexible deployment.
- Hypervisor: Hyper-V or VMware
- Disk space: 250 GB
- CPU: 2
- RAM: 4 GB
- Set your firewall as described in Network requirements
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 generally exceeds 50 GB per hour, it's recommended to 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 automated upload setting 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:
a. Click Add data source.
b. Name your proxy or firewall.
c. 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.
d. 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.
e. Set the Receiver type to either FTP or Syslog. For Syslog, choose UDP, TCP, or TLS.
f. Click Add to save the data source. Repeat this process for each firewall and proxy whose logs can be used to detect traffic on your network.
Go to the Log collectors tab at the top.
a. Click Add log collector.
b. Give the log collector a Name.
c. Select all Data sources that you want to connect to the collector. Click Update to save the configuration and generate an access token.
- A single Log collector can handle multiple data sources.
- Copy the contents of the screen because you will use it when you configure the Log Collector to communicate with Cloud App Security. If you selected Syslog, this information includes information about which port the Syslog listener is listening on.
If you accept the end-user license terms, Download a new log collector virtual machine by clicking on Hyper-V or VMWare. Then, unzip the file using the password you received in the portal.
Step 2 – On-premises deployment of the virtual machine and network configuration
The following steps describe the deployment in Hyper-V. The deployment steps for VM hypervisor are slightly different.
Open the Hyper-V Manager.
Select New and then Virtual Machine and click Next.
Provide a Name for the new virtual machine, for example CloudAppSecurityLogCollector01.then click Next.
Select Generation 1 and click Next.
Change the Startup memory to 4096 MB.
Check Use Dynamic Memory for this virtual machine and click Next.
If available, choose the network Connection and click Next.
Choose Use an existing virtual hard disk. Select the .vhd file that was included in the Zip file you downloaded.
Click Next and then click Finish.
The machine is added to your Hyper-V environment.
Click on the machine in the Virtual Machines table and click Start.
Connect to the Log Collector virtual machine to see if it has been assigned a DHCP address: Click on the virtual machine and select Connect. You should see the sign in prompt. If you see an IP address, then you can connect to the virtual machine using a terminal/SSH tool. If you don't see an IP address, sign in using the Hyper-V/VMWare connection tools with the credentials you copied down when you created the Log Collector previously. You can change the password and configure the virtual machine using the network configuration utility by running the following command:
The virtual machine is pre-configured to obtain an IP address from a DHCP server. If you need to configure a static IP address, default gateway, hostname, DNS servers, and NTPS, you can use the network_config utility or perform changes manually.
At this point, your log collector should be connected to your network and should be able to reach the Cloud App Security portal.
Step 3 – On-premises configuration of the log collection
The first time you sign in to the log collector and import the log collector's configuration from the portal, as follows.
Sign in to the log collector over SSH using the Interactive admin credentials provided to you in the portal. (If this is your first time logging in to the console, you'll need to change the password and sign in again after changing the password. If you're using a terminal session, you might need to restart the terminal session. )
Run the collector config utility with the access token provided to you when you created the log collector.
sudo collector_config <access token>
Enter your console domain, for example:
contoso.portal.cloudappsecurity.comThis is available from the URL you see after logging in to the Cloud App Security portal.
Enter the name of the log collector you want to configure, for example: CloudAppSecurityLogCollector01 or NewYork from the preceding picture.
Import the log collector's configuration from the portal, as follows:
a. Sign in to the log collector over SSH using the Interactive admin credentials provided to you in the portal.
b. Run the collector config utility with the access token provided to you in the command
sudo collector_config \<access token>
c. Enter your console domain, for example:
d. Enter the name of the log collector you want to configure, for example:
Step 4 - 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:
`London Zscaler - Destination path: 614` BlueCoat_HQ - Destination path: \<<machine_name>>\BlueCoat_HQ\
Step 5 - 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 that the log collector connection and parsing haven't completed.
Go to the Governance log and verify that logs are being periodically uploaded to the portal.
If you have problems during deployment, see Troubleshooting Cloud Discovery.
Optional - Create custom continuous reports
After you've verified that the logs are being uploaded to Cloud App Security and the reports are being generated, you can create custom reports. You can now 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, you can import the marketing group using the import user group feature, and 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.
- Under the Filters you can filter the data by data source, by imported user group, or by IP address tags and ranges.
All custom reports are limited to a maximum of 1 GB of uncompressed data. If there is more than 1 GB of data, the first 1 GB of data will be exported into the report.