Confirm permission
Install and run CSAEC only on systems you own or are explicitly authorised to assess. Network-oriented checks should comply with organisational policy and the agreed assessment scope.
AUTHORISED DOWNLOAD
Get CSAEC for Windows.
CSAEC — Download the application for 64-bit Windows and review the licence notice before installation.
WIN 64
CyberScanner.exe
Microsoft Windows 10 or later · 64-bit
SHA-2564c3b97233f0f1cdabe39939ca7273fa05df2995acb97feb9141e5ff99c13a578
LICENCE REQUIRED
The download alone does not activate CSAEC.
A valid commercial licence is required for the software to function. Contact CONNEXT EOOD to purchase the licence and receive activation instructions.
Installation safety
- Verify the SHA-256 checksum after downloading.
- Approve only prompts you understand and that identify the expected source.
- Do not weaken security controls or bypass company policy.
- Suitable permissions may be required for some checks.
BEFORE YOU DOWNLOAD
Prepare for a controlled installation.
Review the platform
The supported baseline is Microsoft Windows 10 or later, 64-bit. Storage and hardware requirements can vary with the authorised package and local AI configuration.
Verify the checksum
Calculate the SHA-256 digest of the downloaded executable and compare it with the value published on this page. A mismatch means the file should not be executed.
Respect security controls
Do not disable endpoint protection, firewall settings or organisational safeguards simply to complete installation. Unexpected prompts should be reviewed with IT support.
Obtain activation
The installer alone is not an operational product. A valid €6.250 commercial licence and the associated activation instructions are required.
Read before scanning
Use the User Guide for operation and the Technical Guide for architecture, result limitations, network components, local AI and maintenance details.
Why checksum verification matters
A cryptographic checksum is a reproducible fingerprint of a file. If the downloaded bytes change because of corruption, incomplete transfer or unauthorised modification, the calculated SHA-256 value should differ from the published value. Verification does not prove that software is suitable for every environment, but it is an important distribution-integrity check.
Windows administrators can use an approved local checksum utility or PowerShell’s file-hash functionality according to internal procedure. Compare the complete sequence, not only the first or last characters. If the values differ, delete the suspect copy, do not bypass warnings and obtain the installer again from the authorised source.
After installation
Start the application from the authorised package location or installed entry. Some checks need suitable permissions. Keep the application open during the complete assessment and allow longer network or vulnerability-oriented modules to finish. If a result is limited or unavailable, investigate the message rather than assuming the control is healthy.
Review every finding before preparing a report. Reports may contain security-sensitive details about system configuration, network devices, ports or potential vulnerabilities. Store them according to organisational policy and share them only with authorised recipients through an approved secure channel.
Download responsibility
The executable is distributed as supplied and is not run or modified by this website. The website cannot determine whether your hosting provider, browser, endpoint security product or corporate policy permits executable downloads. Organisations remain responsible for approval, malware scanning, licence compliance and controlled deployment.
CONTROLLED SOFTWARE LIFECYCLE
Plan installation, operation and review.
Before deployment, identify the authorised package owner and record the version and checksum. During operation, protect local results and model files with the same care applied to other business software. When an updated authorised build becomes available, review release information and organisational compatibility before replacement.
If the application is removed, follow internal software-management and data-retention procedures. Reports that remain necessary for audit trails or improvement records should be stored securely; obsolete sensitive copies should be removed through an approved process.