e wireless network for guests. For optimal security, this network should not be accessible to all guests without any limits. Wi-Fi networks have known vulnerabilities that needs to be protected against independently. Environments based on containers (such as Docker), often use tooling for central management (container orchestration). These tools must be set up carefully to prevent attackers from taking over the entire infrastructure by breaking into one application. Ensure that there are no unnecessary applications running on the systems, and that when any applications/services are started, they are properly secured. Remote management aspects SNMP is based on UDP, a simple, stateless protocol, and is therefore susceptible to IP spoofing, and replay attacks. In addition, the commonly used SNMP protocols 1, 2, and 2c offer no traffic encryption, meaning SNMP information and credentials can be easily intercepted over a local network. Traditional SNMP protocols also have weak authentication schemes and are commonly left configured with default public and private community strings. The remote management of devices in a network are managed with different protocols such as, RDP (Remote Desktop Protocol), VNC (Virtual Network Computing), X11, SSH (Secure Shell), FTP (File Transfer Protocol), etc. There may be known vulnerabilities due to not updating this software. Also, misconfiguration for these protocols can cause serious problems. Security updates A secure computer requires a secure base. It is therefore crucial that the used operation sys- tems are fully patched, and no security updates are missing. In server software, as in all other software, security vulnerabilities are discovered continuously. Therefore it is essential to patch software as soon as possible. Patching is needed even more in case of programs or guides which make it easy for less skilled attackers to carry out an attack that are available on the Internet. To resolve security vulnerabilities, vendors, and communities actively maintain software. This 