About the Device
Squid is a caching proxy for the Web supporting HTTP, HTTPS, FTP, and more. It reduces bandwidth and improves response times by caching and reusing frequently-requested web pages. Squid has extensive access controls and makes a great server accelerator.
Squid provides the best possible web access by optimizing the data flow between client and server to improve performance and by caching frequently-used content to save bandwidth. Squid can also route content requests to servers in a wide variety of ways to build cache server hierarchies which optimizes network throughput. Squid helps in building content clusters to route and load balance requests via a variety of web servers.
Device Information
Entity | Particulars |
|---|---|
Vendor Name | Squid |
Product Name | Web Proxy |
Type of Device | Hosted |
Collection Method
Log Type | Ingestion label | Preferred Logging Protocol - Format | Log collection method |
|---|---|---|---|
Squid Web Proxy | SQUID_WEBPROXY | Syslog | CyberHub |
Port Requirements
Source | Destination | Port |
|---|---|---|
Squid Web Proxy | CyberHub | 601 (TCP) |
To facilitate secure communication and align with our best practice, we strongly encourage the use of Transport Layer Security (TLS) between your security devices and our Adaptive MxDR platform for event forwarding.
While we understand that TLS support may not be available on all devices, if your devices do support TLS communication, we recommend utilizing port 6514 for seamless integration.
In some cases, the upgraded version of the device might incorporate TLS support without prior notice. If you come across such a scenario or for further assistance in configuring TLS, we kindly ask you to reach out to your dedicated Adaptive MxDR Service Delivery Lead.
Device Configuration
The procedures in this document have been tested on - Squid Proxy v5.7 installed on Ubuntu 22.04.4 LTS. As a prerequisite, we assume that Squid Server has been deployed and running properly on the host machine.
Follow the below steps to configure Squid Proxy Server and RSyslog service to forward Squid Access Logs to CyberHub.
Access Host machine with root or Similar Privileges.
Ensure taking backup of your existing squid configuration file (
squid.conf).Modify Squid configuration file
/etc/squid/squid.confby carefully adding following lines under Log File options to specify Log Format along with Syslog settings for Access Log and save the edits.
Adaptive MxDR support two formats: The Default Format (squid) and a Custom Format (AMxDRSquid). For more detailed logging data, we recommend using the Custom Format.
a. To use Custom format, add following lines in the squid configuration file.
logformat AMxDRSquid %ts.%03tu %6tr %>a %Ss/%03>Hs %<st %rm %ru %[un %Sh/%<a %mt %>p %<p "%{Referer}>h" "%{User-Agent}>h" %>st %<st
access_log syslog:<Syslog_Facility>.<Syslog_Severity> AMxDRSquid
Specify any chosen Linux Syslog_Facility and Syslog_Severity.
Here we have used Syslog_Facility as local6 and Syslog_Severity as info. Kindly follow the below snapshot.
b. To use Default Squid format, add the following line in the squid configuration file.
access_log syslog:<Syslog_Facility>.<Syslog_Severity> squid
Specify any chosen Linux Syslog_Facility and Syslog_Severity
Here we have used Syslog_Facility as local6 and Syslog_Severity as info. Kindly follow the below snapshot.
Modify or create the
/etc/rsyslog.d/50-default.conffile and add the following line at the end of the file and save the edits.
$template AMxDRSquidPattern,"<%pri%>%timegenerated% %HOSTNAME% squid-access%msg%\n" local6.info @@<CyberHub-IP>:601;AMxDRSquidPattern
Specify <CyberHub-IP>in the IP placeholder.
Restart Squid and rsyslog services.
systemctl restart rsyslog systemctl restart squid
Integration Parameters
Parameters required from customer for Integration.
Property | Default Value | Description |
|---|---|---|
IP Address | Squid Web Proxy interface IP address | Hostname or IP address of the device which forwards logs to the CyberHub |