Disable Cockpit Management Server

An XCCDF Rule

Description

The Cockpit Management Server (cockpit) provides a web based login and management framework. The cockpit service can be disabled with the following command:

$ sudo systemctl mask --now cockpit.service

Rationale

Cockpit provides a form of remote login.

ID: xccdf_org.ssgproject.content_rule_service_cockpit_disabled
Severity: Medium
Updated: about 1 year ago

apiVersion: machineconfiguration.openshift.io/v1
kind: MachineConfig
spec:
  config:
    ignition:
      version: 3.1.0    systemd:
      units:
      - name: cockpit.service
        enabled: false
        mask: true
      - name: cockpit.socket
        enabled: false
        mask: true


[customizations.services]
disabled = ["cockpit"]

- name: Block Disable service cockpit
  block:

  - name: Disable service cockpit
    block:
    - name: Disable service cockpit
      systemd:
        name: cockpit.service
        enabled: 'no'
        state: stopped
        masked: 'yes'
    rescue:

    - name: Intentionally ignored previous 'Disable service cockpit' failure, service
        was already disabled
      meta: noop
  when: ansible_virtualization_type not in ["docker", "lxc", "openvz", "podman", "container"]
  tags:
  - disable_strategy
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed
  - service_cockpit_disabled

- name: Unit Socket Exists - cockpit.socket
  command: systemctl -q list-unit-files cockpit.socket
  register: socket_file_exists
  changed_when: false
  failed_when: socket_file_exists.rc not in [0, 1]
  check_mode: false
  when: ansible_virtualization_type not in ["docker", "lxc", "openvz", "podman", "container"]
  tags:
  - disable_strategy
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed
  - service_cockpit_disabled

- name: Disable socket cockpit
  systemd:
    name: cockpit.socket
    enabled: 'no'
    state: stopped
    masked: 'yes'
  when:
  - ansible_virtualization_type not in ["docker", "lxc", "openvz", "podman", "container"]
  - socket_file_exists.stdout_lines is search("cockpit.socket",multiline=True)
  tags:
  - disable_strategy
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed
  - service_cockpit_disabled

include disable_cockpit

class disable_cockpit {
  service {'cockpit':
    enable => false,
    ensure => 'stopped',  }
}

# Remediation is applicable only in certain platforms
if [ ! -f /.dockerenv ] && [ ! -f /run/.containerenv ]; then

SYSTEMCTL_EXEC='/usr/bin/systemctl'
"$SYSTEMCTL_EXEC" stop 'cockpit.service'
"$SYSTEMCTL_EXEC" disable 'cockpit.service'"$SYSTEMCTL_EXEC" mask 'cockpit.service'
# Disable socket activation if we have a unit file for it
if "$SYSTEMCTL_EXEC" -q list-unit-files cockpit.socket; then
    "$SYSTEMCTL_EXEC" stop 'cockpit.socket'
    "$SYSTEMCTL_EXEC" mask 'cockpit.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 'cockpit.service' || true

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

Disable Cockpit Management Server

Description

Rationale

Remediation - Kubernetes Patch

Remediation - OS Build Blueprint

Remediation - Ansible

Remediation - Puppet

Remediation - Shell Script