Disable Squid

An XCCDF Rule

Description

The squid service can be disabled with the following command:

$ sudo systemctl mask --now squid.service

Rationale

Running proxy server software provides a network-based avenue of attack, and should be removed if not needed.

ID: xccdf_org.ssgproject.content_rule_service_squid_disabled
Severity: Unknown
Updated: about 1 month ago

Remediation Templates

[customizations.services]
masked = ["squid"]

include disable_squid
class disable_squid {
  service {'squid':
    enable => false,
    ensure => 'stopped',
  }
}

- name: Gather the package facts
  package_facts:
    manager: auto
  tags:
  - disable_strategy
  - low_complexity  - low_disruption
  - no_reboot_needed
  - service_squid_disabled
  - unknown_severity
- name: Disable Squid - Collect systemd Services Present in the System
  ansible.builtin.command: systemctl -q list-unit-files --type service
  register: service_exists
  changed_when: false
  failed_when: service_exists.rc not in [0, 1]
  check_mode: false
  when: ( "squid" in ansible_facts.packages and "kernel" in ansible_facts.packages
    )
  tags:
  - disable_strategy
  - low_complexity
  - low_disruption
  - no_reboot_needed
  - service_squid_disabled
  - unknown_severity

- name: Disable Squid - Ensure squid.service is Masked
  ansible.builtin.systemd:
    name: squid.service
    state: stopped
    enabled: false
    masked: true
  when:
  - ( "squid" in ansible_facts.packages and "kernel" in ansible_facts.packages )
  - service_exists.stdout_lines is search("squid.service", multiline=True)
  tags:
  - disable_strategy
  - low_complexity
  - low_disruption
  - no_reboot_needed
  - service_squid_disabled
  - unknown_severity

- name: Unit Socket Exists - squid.socket
  ansible.builtin.command: systemctl -q list-unit-files squid.socket
  register: socket_file_exists
  changed_when: false
  failed_when: socket_file_exists.rc not in [0, 1]
  check_mode: false
  when: ( "squid" in ansible_facts.packages and "kernel" in ansible_facts.packages
    )
  tags:
  - disable_strategy
  - low_complexity
  - low_disruption
  - no_reboot_needed
  - service_squid_disabled
  - unknown_severity

- name: Disable Squid - Disable Socket squid
  ansible.builtin.systemd:
    name: squid.socket
    enabled: false
    state: stopped
    masked: true
  when:
  - ( "squid" in ansible_facts.packages and "kernel" in ansible_facts.packages )
  - socket_file_exists.stdout_lines is search("squid.socket", multiline=True)
  tags:
  - disable_strategy
  - low_complexity
  - low_disruption
  - no_reboot_needed
  - service_squid_disabled
  - unknown_severity

# Remediation is applicable only in certain platforms
if ( rpm --quiet -q squid && rpm --quiet -q kernel ); then
SYSTEMCTL_EXEC='/usr/bin/systemctl'
"$SYSTEMCTL_EXEC" stop 'squid.service'
"$SYSTEMCTL_EXEC" disable 'squid.service'
"$SYSTEMCTL_EXEC" mask 'squid.service'# Disable socket activation if we have a unit file for it
if "$SYSTEMCTL_EXEC" -q list-unit-files squid.socket; then
    "$SYSTEMCTL_EXEC" stop 'squid.socket'
    "$SYSTEMCTL_EXEC" mask 'squid.socket'
fi
# The service may not be running because it has been started and failed,
# so let's reset the state so OVAL checks pass.
# Service should be 'inactive', not 'failed' after reboot though.
"$SYSTEMCTL_EXEC" reset-failed 'squid.service' || true

else
    >&2 echo 'Remediation is not applicable, nothing was done'
fi

Disable Squid

Description

Rationale

Remediation Templates

OS Build Blueprint

A Puppet Snippet

An Ansible Snippet

A Shell Script