BlackSec Agent is a closed-source product distributed only from this site, which makes integrity verification worth doing every time. Every build is published with a SHA-256 digest, and comparing it takes about two minutes.
1. Get the published digest
Open the agent page and find the download section. The verification block shows the expected SHA-256 for the current release, together with the exact expected file size in bytes. Note both.
2. Hash the file you received
Open PowerShell in the folder containing the installer and run:
Get-FileHash .\BlackSecAgent-Setup-<version>-x64.exe -Algorithm SHA256
PowerShell prints a hash in uppercase hexadecimal. Comparison is case-insensitive, but every character must match.
3. Compare, and know what a mismatch means
If the digest matches, the file is byte-for-byte the build we published. If it does not match, the file was corrupted in transit or altered after publication. In that case do not run it: delete it and download it again from the download section. A second mismatch is worth reporting rather than working around.
Checking the size is a useful second signal. The digest is authoritative, but a wildly different size tells you immediately that you have the wrong file — an older release, a partial download, or something else entirely.
Why not just trust the browser?
HTTPS protects the transfer, not the file at rest on your disk, and it says nothing about whether the artefact was what the publisher intended to ship. A published digest is the part that lets you check the bytes yourself. That is also why the Installer License prohibits stripping or bypassing integrity verification: the check is part of how the product is meant to work.