What it is
This page is a short orientation guide for reading a first CyberLens report without having to study the whole documentation before you know where to start.
Why it matters
The first useful step is rarely reading everything. In most cases, it is better to separate the findings that are already clear, the ones that are more urgent, and the ones that can wait.
How CyberLens checks it
CyberLens collects several technical checks and shows them with severity, context, and technical details. This page does not add new checks: it helps readers understand how to use the ones that already exist.
Possible findings
In a first report, it is often useful to split findings into:
- issues that are already fixable with a published guide;
- issues that require hosting, DNS, or server access;
- improvements that are worth planning later but are not urgent.
Recommended action
- Open the clearest or most urgent finding in the report.
- Check whether a dedicated guide is already available.
- Avoid fixing everything at once. One verified correction at a time is usually the better path.
How to fix it
For the checks already documented, the simplest path is to start from one of these guides: