Application check

The Application Check device posture attribute checks that a specific application process is running on a device. You can create multiple application checks for each operating system you need to run it on, or if you need to check for multiple applications.

Prerequisites

• Cloudflare WARP client is deployed on the device. For a list of supported modes and operating systems, refer to WARP Client Checks.

Configure an application check

1. In Zero Trust ↗, go to Settings > WARP Client.

2. Scroll down to WARP client checks and select Add new.

3. Select Application Check.

4. You will be prompted for the following information:

   1. Name: Enter a unique name for this device posture check.
   2. Operating system: Select your operating system.
   3. Application path: Enter the file path for the executable that will be running (for example, C:\Program Files\myfolder\myfile.exe).

   Note

   • Be sure to enter the binary file path, not the application launch path. When checking for an application on macOS, a common mistake is to enter /Applications/ApplicationName.app. This will not work as ApplicationName.app is a folder. The executable file that will be running is located within the folder, for example ApplicationName.app/Contents/MacOS/ApplicationName.
   • Some applications change their file path after an update. Ensure that the application is always in a stable location, or use an environment variable to identify a specific folder. For example, Windows provides recognized environment variables ↗ that you can reference in your file path (%PROGRAMFILES%\myfolder\myfile.exe).

5. Signing certificate thumbprint (recommended): Enter the thumbprint of the publishing certificate used to sign the binary. Adding this information will enable the check to ensure that the application was signed by the expected software developer.

6. SHA-256 (optional): Enter the SHA-256 value of the binary. This is used to ensure the integrity of the binary file on the device.

7. Select Save.

Next, go to Logs > Posture and verify that the application check is returning the expected results.

Determine the signing thumbprint

The process to determine the signing thumbprint of an application varies depending on the operating system. This is how you would look up the signing thumbprint of the Cloudflare WARP application on macOS and Windows.

Note

When setting up new device posture checks, we recommend first testing them without setting certificate thumbprint or SHA256 checksum values.

macOS

1. Create a directory.

   ~/Desktop $ mkdir tmp
   
   ~/Desktop $ cd tmp

2. Run the following command to extract certificates for the WARP application:

   ~/Desktop/tmp $ codesign -d --extract-certificates "/Applications/Cloudflare WARP.app/Contents/Resources/CloudflareWARP"
   Executable=/Applications/Cloudflare WARP.app/Contents/Resources/CloudflareWARP

3. Next, run the following command to extract the SHA1 thumbprint:

   ~/Desktop/tmp $ openssl x509 -inform DER -in codesign0 -fingerprint -sha1 -noout | tr -d :
   SHA1 Fingerprint=FE2C359D79D4CEAE6BDF7EFB507326C6B4E2436E

Windows

1. Open a PowerShell window.

2. Use the Get-AuthenticodeSignature command to find the thumbprint. For example:

   PowerShell

   Get-AuthenticodeSignature -FilePath c:\myfile.exe

Determine the SHA-256 value

The SHA-256 value almost always changes between versions of a file/application.

macOS

1. Open a Terminal window.

2. Use the shasum command to find the SHA256 value of the file. For example:

   shasum -a 256 myfile

Windows

1. Open a PowerShell window.

2. Use the get-filehash command to find the SHA256 value of the file. For example:

   PowerShell

   get-filehash -path "C:\myfile.exe" -Algorithm SHA256 | format-list

How WARP checks for an application

Learn how the WARP client determines if an application is running on various systems.

macOS

To get the list of active processes, run the following command:

ps -eo comm | xargs which | sort | uniq

The application path must appear in the output for the check to pass.

Linux

The WARP client gets the list of running binaries by following the soft links in /proc/<pid>/exe. To view all active processes and their soft links:

ps -eo pid | awk '{print "/proc/"$1"/exe"}' | xargs readlink -f | awk '{print $1}' | sort | uniq

The application path must appear in the /proc/<pid>/exe output for the check to pass.