CSAEC — A complete operational introduction to CSAEC, based on the official User Guide version 1.0.
Use a standard Windows desktop environment with enough local storage for the application, its security components and the local AI model. Detailed hardware needs can vary with the authorised build and selected AI configuration.
Some system and network checks require suitable user permissions. If a result is unavailable, treat it as a limitation. Never assume that an unobserved control is healthy and never bypass organisational policy simply to obtain a result.
Obtain CyberScanner.exe only from the authorised distribution, confirm that it is intended for 64-bit Windows and compare the SHA-256 checksum before execution. Approve only prompts you understand.
The downloadable installer does not work as a licensed product by itself. A valid commercial licence, published at €6.250, and the associated activation information are required.
Close unnecessary applications, follow the authorised package instructions and retain any installation information supplied by CONNEXT EOOD. If Windows, endpoint protection or organisational controls display an unexpected publisher, source or permission request, stop and ask the responsible IT administrator.
Do not disable antivirus, firewall protection, application controls or policy settings to force installation. A successful installation that required unauthorised security weakening is not an acceptable outcome. The objective is to deploy the application in a controlled, supportable manner.
After installation, open CSAEC from the installed application entry or authorised package location. Allow local components, including the AI model, time to initialise. Some functions may take longer on first use because local resources must be prepared on the workstation.
The score provides a high-level orientation across the twelve controls. It should be read only after the assessment completes and never used without the individual findings.
Each card represents one security check, with status, severity, plain-language explanation, general action and any relevant technical details.
Checks can complete at different speeds. Network discovery and vulnerability-oriented checks often take longer because visibility depends on services and network conditions.
Open warnings and high-attention findings to read the explanation, observed hosts or services, limitation and recommended next step.
Recheck a single control after an approved change, or run the complete assessment again to create a new point-in-time overview.
The Security Wiki and integrated AI assistant help explain findings locally, without sending the prompt to a cloud AI service or requiring an Internet connection.
Open CSAEC and select the complete assessment option if the scan does not begin automatically. Keep the application open while all twelve controls run. Avoid changing network connections or system configuration during the scan unless instructed by authorised technical personnel, because the result should represent a coherent point in time.
As checks finish, the interface displays their current status. A fast local configuration check may complete before device discovery, port inspection or vulnerability-oriented analysis. Progress differences do not automatically indicate a fault. If a check remains incomplete, wait briefly, review permissions and use the troubleshooting guidance before repeating it.
When the assessment has finished, examine the score classification and then open every warning or high-attention card. Green does not mean permanent safety; amber can represent a weakness or limited visibility; red indicates that a material concern may be present and should be validated promptly.
A completed scan proves only that the defined checks reached an outcome under the conditions visible at that time. It does not prove that every device was visible, every vulnerability was detected or every configuration is appropriate for the organisation.
Open a finding and read the status, explanation, available host or port information, limitation and suggested action. Treat the suggested action as a starting point for investigation, not as an automatic command. Significant changes to firewalls, encryption, endpoint protection, updates, backups, services or radio interfaces can affect operations and require approval.
After an approved change, use the individual recheck when you want to test the relevant control. Use a complete recheck after several changes or when a fresh overall snapshot is needed. New results replace the displayed scan state, so retain reports according to your organisation's evidence and retention process.
Explore every control, the completely local AI architecture, frequently asked questions and practical troubleshooting.