Prisma Cloud can secure Windows containers running on Windows Server 2016 and Windows Server 2019 hosts. A single instance of Prisma Cloud Console can simultaneously protect both Windows and Linux containers on both Windows and Linux hosts. Prisma Cloud’s Intelligence Stream includes vulnerability data from Microsoft, so as new CVEs are reported, Prisma Cloud can detect them in your Windows images.
The architecture for Defender on Windows is different than Defender on Linux. Rather than running as a Docker container (as it does on Linux), Defender runs as a Windows service. And rather than implementing runtime protection in userspace (as it does on Linux), Windows drivers are used. This is because there is no concept of capabilities in Windows Docker containers like there is on Linux. Defender on Windows runs as service so it can acquire the permissions it needs to secure the containers on your host. When you deploy the Defender, it appears as a service. The Defender type "Container Defender - Windows" means that Defender is capable of securing your containers, not that it’s deployed as a container.
To deploy Defender on Windows, you’ll copy a PowerShell script from the Prisma Cloud Console and run it on the host where you want to install Defender.
Full feature parity on both Windows and Linux is a key objective. With every release, Prisma Cloud expands Defender’s capabilities on Windows.
The following table shows the current state of Prisma Cloud’s Windows support:
As a quick review, Prisma Cloud runtime defense builds a whitelist model for each container image during a so-called learning period. After the learning period has completed, any violation of the model triggers an action as defined by your policy (alert, prevent, block).
As Prisma Cloud builds the model, any interactive tasks that are run are logged. These interactive tasks can be viewed in the History tab of each model. On Windows, Prisma Cloud cannot currently detect when interactive tasks are run with the
docker execcommand, although Prisma Cloud does correctly record interactive tasks run from a shell inside a container with the
docker run -it <IMAGE> shcommand. No matter how the interactive task is run, however, the model will correctly whitelist a process if it’s in learning mode, and it will take action if the model is violated when in enforcement mode.
Deploying Defender on Windows
Prisma Cloud Console must be first installed on a Linux host. Prisma Cloud Defenders are then installed on each Windows host you want to protect. For more information about installing Console, see Getting Started. The Onebox install is the fastest way to get Console running on a stand-alone Linux machine.
Defenders are deployed with with a PowerShell 64-bit script,
defender.ps1, which downloads the necessary files from Console. Defender is registered as a Windows service.
Run the Prisma Cloud Defender deployment PowerShell script from a Windows PowerShell 64-bit shell.
After the install is completed, Prisma Cloud files can be found in the following locations:
- C:\Program Files\Prisma Cloud\
- C:\ProgramData\Prisma Cloud\
- Windows Server 2016 or Windows Server 2019. Prisma Cloud is not supported on Windows 10 or Hyper-V.
- Log into Console.
- Go toManage > Defenders > Deploy.
- InChoose the Defender type, selectDocker on Windows.
- Copy the curl script and run it on your host to install Windows Defender.If you install Windows locally on your laptop, the 'netsh' commands are not needed. They are only applicable to the GCE environment.
To scan Windows images in your registry, you must install at least one Windows Defender. Prisma Cloud automatically distributes the scan job across available Defenders. To scan registries that hold both Windows and Linux images, install at least one Linux Defender and one Windows Defender in your environment.
You can uninstall Defender directly from the Console UI.
You can also manually uninstall Defender from the command line by running:
C:\Program files\twistlock\scripts\defender.ps1 -uninstall
Since Defender runs as a Windows service, decommissioning it will stop the service. Some remnant files might need to be deleted manually.
- Go toManage > Defenders > Manage.This page shows a list of Defenders deployed in your environment and connected to Console.
- Click theDecommissionbutton.
Recommended For You
Recommended videos not found.