---
title: Disable kea-dhcp4-server Service
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: Docs > Datadog Security > OOTB Rules > Disable kea-dhcp4-server Service
---

> For the complete documentation index, see [llms.txt](https://docs.datadoghq.com/llms.txt).

# Disable kea-dhcp4-server Service
 
## Description{% #description %}

The `kea-dhcp4-server` service should be disabled on any system that does not need to act as a DHCPv4 server. The `kea-dhcp4-server` service can be disabled with the following command:

```
$ sudo systemctl mask --now kea-dhcp4-server.service
```

## Rationale{% #rationale %}

Unmanaged or unintentionally activated DHCP servers may provide faulty information to clients, interfering with the operation of a legitimate site DHCP server if there is one.

## Remediation{% #remediation %}

### Shell script{% #shell-script %}

The following script can be run on the host to remediate the issue.

```bash
#!/bin/bash

# Remediation is applicable only in certain platforms
if dpkg-query --show --showformat='${db:Status-Status}' 'linux-base' 2>/dev/null | grep -q '^installed$'; then

SYSTEMCTL_EXEC='/usr/bin/systemctl'
if [[ $("$SYSTEMCTL_EXEC" is-system-running) != "offline" ]]; then
  "$SYSTEMCTL_EXEC" stop 'kea-dhcp4-server.service'
fi
"$SYSTEMCTL_EXEC" disable 'kea-dhcp4-server.service'
"$SYSTEMCTL_EXEC" mask 'kea-dhcp4-server.service'
# Disable socket activation if we have a unit file for it
if "$SYSTEMCTL_EXEC" -q list-unit-files kea-dhcp4-server.socket; then
    if [[ $("$SYSTEMCTL_EXEC" is-system-running) != "offline" ]]; then
      "$SYSTEMCTL_EXEC" stop 'kea-dhcp4-server.socket'
    fi
    "$SYSTEMCTL_EXEC" mask 'kea-dhcp4-server.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 'kea-dhcp4-server.service' || true

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

### Ansible playbook{% #ansible-playbook %}

The following playbook can be run with Ansible to remediate the issue.

```go
- name: Gather the package facts
  package_facts:
    manager: auto
  tags:
  - disable_strategy
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed
  - service_kea_dhcp4_server_disabled

- name: Disable kea-dhcp4-server Service - Disable service kea-dhcp4-server
  block:

  - name: Disable kea-dhcp4-server Service - Collect systemd Services Present in the
      System
    ansible.builtin.service_facts: null
    check_mode: false

  - name: Disable kea-dhcp4-server Service - Ensure kea-dhcp4-server.service is Masked
    ansible.builtin.systemd:
      name: kea-dhcp4-server.service
      state: stopped
      enabled: false
      masked: true
    when: '"kea-dhcp4-server.service" in ansible_facts.services'

  - name: Unit Socket Exists - kea-dhcp4-server.socket
    ansible.builtin.find:
      paths:
      - /etc/systemd/system
      - /run/systemd/system
      - /usr/lib/systemd/system
      - /lib/systemd/system
      - /usr/local/lib/systemd/system
      patterns: kea-dhcp4-server.socket
      file_type: any
    register: socket_file_exists
    check_mode: false

  - name: Disable kea-dhcp4-server Service - Disable Socket kea-dhcp4-server
    ansible.builtin.systemd:
      name: kea-dhcp4-server.socket
      enabled: false
      state: stopped
      masked: true
    when: socket_file_exists.matched > 0
  tags:
  - disable_strategy
  - low_complexity
  - low_disruption
  - medium_severity
  - no_reboot_needed
  - service_kea_dhcp4_server_disabled
  - special_service_block
  when: '"linux-base" in ansible_facts.packages'
```
