Frequently Asked Questions
Quickly find answers to your cybersecurity questions.
If a security incident occurs due to risky behavior by a poorly informed employee, the company remains largely responsible. The law, including the nLPD in Switzerland and the GDPR in Europe, requires organizations to take the necessary measures to protect data and reduce risks. This includes training and awareness for staff.
In the event of a dispute or investigation, a company unable to demonstrate that it has implemented preventive actions (such as regular training, awareness campaigns, or reminders of best practices) could be deemed negligent. This can lead to fines, damage to reputation, and a loss of trust from customers and partners.
The cve.org website, managed by MITRE, is the official source of CVE identifiers. It is essential for ensuring the uniqueness and structure of entries. However, cve.org focuses on the administrative aspect and does not provide EPSS scores, exploitation indicators, or advanced sorting functionalities.
Our CVE Find service takes this official data, enriches it with complementary metrics (KEV, EPSS, CVSS), and presents it in a more modern, faster, and filterable interface. It is therefore a practical monitoring tool, designed for operational and decision-making use on a daily basis.
They are two complementary tools:
- PhishTrainer works through practice: it sends fake phishing emails to your employees and measures who clicks and who reports the attack. This is the behavioural approach — learning by experience. The dashboard shows the click rate, the reporting rate and the trend over time.
- Bexxo Academy works through knowledge: video modules, interactive quizzes, educational games on cyber threats. Available 24/7 online, complemented by in-person sessions in Ins (BE). Ideal for onboarding new employees and updating knowledge.
Both tools together cover the complete loop: raise awareness → test → measure → improve.
The main difference between black box, gray box, and white box testing lies in the level of information provided to the tester before starting the simulated attack.
- In black box, the attacker has no prior knowledge of the system. They act as an external hacker and attempt to access resources without any assistance. This type of test is realistic for simulating an external attack, but it is often limited to what can be guessed or discovered from the outside.
- In gray box, the tester has some technical information or partial access (such as a user account). This reflects a scenario where the attacker has already infiltrated part of the system or possesses internal knowledge, such as a former employee.
- In white box, all information is provided: source code, technical documentation, administrator access. This type of test provides a complete view and allows for the identification of deep vulnerabilities, often invisible from the outside.
Each approach has its advantages, and the choice depends on the objectives of the test and the level of risk to be covered.
A vulnerability scan is an automated analysis performed by a tool that examines a system or application for known vulnerabilities, typically by comparing software versions or testing configurations. It is fast and inexpensive, but often produces raw or incomplete results, with false positives.
A pentest, on the other hand, goes beyond detection: it seeks to actually exploit vulnerabilities to demonstrate their concrete impact. It is a manual and methodical process that validates detected vulnerabilities, identifies new ones, and provides realistic attack scenarios. The pentest is therefore much more thorough and contextual, but requires time, expertise, and planning.
Security awareness aims to spread a general security culture, accessible to all employees, regardless of their profession or technical level. It covers concrete topics: phishing, passwords, mobility, social networks, vigilance in teleworking, etc. The goal is to make everyone an actor in security in their daily uses.
Technical training, on the other hand, is aimed at more specialized profiles (IT teams, devs, admins) and focuses on specific skills such as system hardening, secure development, or incident management. It often requires prerequisites and aims to strengthen security through technical mastery.