pcx_content_type | title | weight |
---|---|---|
how-to |
Application check |
1 |
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.
- {{}}
-
In Zero Trust, go to Settings > WARP Client.
-
Scroll down to WARP client checks and select Add new.
-
Select Application Check.
-
You will be prompted for the following information:
- Name: Enter a unique name for this device posture check.
- Operating system: Select your operating system.
- Application path: Enter the file path for the executable that will be running (for example,
C:\Program Files\myfolder\myfile.exe
). {{}}
- 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 asApplicationName.app
is a folder. The executable file that will be running is located within the folder, for exampleApplicationName.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
).
{{}} 4. 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. 5. 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.
- Select Save.
Next, go to Logs > Posture and verify that the application check is returning the expected results.
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.
{{
}}When setting up new device posture checks, we recommend first testing them without setting certificate thumbprint or SHA256 checksum values.
{{
}}-
Create a directory.
~/Desktop $ mkdir tmp ~/Desktop $ cd tmp
-
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
-
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
-
Open a PowerShell window.
-
Use the
Get-AuthenticodeSignature
command to find the thumbprint. For example:PS C:\Users\JohnDoe> Get-AuthenticodeSignature -FilePath c:\myfile.exe
The SHA-256 value almost always changes between versions of a file/application.
-
Open a Terminal window.
-
Use the
shasum
command to find the SHA256 value of the file. For example:$ shasum -a 256 myfile
-
Open a PowerShell window.
-
Use the
get-filehash
command to find the SHA256 value of the file. For example:PS C:\Users\JohnDoe> get-filehash -path "C:\myfile.exe" -Algorithm SHA256 | format-list
Learn how the WARP client determines if an application is running on various systems.
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.
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.