What action should a security team take to prevent hackers from invoking command-line interpreters using native administrative tools?

Disabling built-in operating system utilities when they are not needed for functionality is an effective measure to prevent unauthorized access via command-line interpreters. Native administrative tools, such as PowerShell or Command Prompt, can be exploited by attackers to execute commands or scripts that compromise the security of a system. By disabling these tools, the security team reduces the attack surface and limits the ability of malicious actors to utilize them in an exploitative manner.

This proactive approach ensures that only necessary services and tools are available, minimizing the opportunities for hackers to invoke these command-line interfaces, which are often used for executing advanced attacks. It is crucial for organizations to regularly assess the tools and utilities in use and disable those that do not serve a clear operational purpose.

While other options, like implementing HIPS and configuring AV solutions, can enhance security, they may not directly tackle the issue of preventing the use of command-line interpreters by hackers within the context of native tool utilization. Those measures might focus more on detecting or responding to threats rather than preventing the existence of potential attack vectors in the first place.