Skip to main content

System- und Netzwerkanforderungen

Stellen Sie sicher, dass Ihr System und Ihr Netzwerk die Mindestanforderungen erfüllen, bevor Sie einen DigiCert-Sensor installieren.

System requirements

The sensor software runs on systems with the following requirements:

Docker Engine 18.06.3 or later and Docker Compose 1.26.2 or later

  • Minimum supported sensor version is 3.8.31

    • 64-bit

    • x86 processor (x86-64)

    • 4 GB RAM

    • 2 GB free disk space (minimum)

  • Other Docker container and network interface requirements include:

    • Docker sensor containers use a bridge network by default. This associates the Docker network with a bridge interface on the host, along with firewall rules to filter traffic between these interfaces.

    • Docker containers that share the same Docker network and host bridge interface but are isolated from each other by a firewall can communicate with each other on the bridge network.

    • To view a list of Docker interfaces, run the docker network ls command.

    • To get information about Docker interfaces, run the docker inspect <docker_container_ID> | grep sensor command.

Microsoft Windows 10, Server (2016, 2019, and 2022)

  • Minimum supported sensor version is 3.8.31

    • 64-bit

    • x86 processor (x86-64)

    • 4 GB RAM

    • 2 GB free disk space (minimum)

Red Hat Enterprise Linux (7.x, 8.x, 9.x), Ubuntu (20.04 and later)

  • Minimum supported sensor version is 3.8.31

    • Root privileges

    • 64-bit and US locale required

    • x86 processor (x86-64)

    • 4 GB RAM

    • 2 GB free disk space (minimum)

Network requirements

The sensor must be able to:

  • Connect outbound to HTTPS (port 443).

  • Access the external DigiCert URLs one.digicert.com and clientauth.one.digicert.com. To use the sensor for certificate lifecycle automation and/or certificate cipher discovery, it must also be able to reach discovery-service.digicert.com.

  • Access any external systems that it will integrate with via connectors, or any systems on your network that it will target for certificate lifecycle automation or in network scans.

  • Resolve the fully qualified domain names (FQDNs) for its host system, either via DNS or a local "hosts" file.