LUAXERR accelerates your company's defenceSovereign cybersecurity, within everyone's reachSOC AI on your servers, free edition
Request a demoDemo

Free check-up

Your defence, in fifteen questions

Five steps, the ones an alert follows: see it, read it, decide, prove, hold. Your results build up as you answer, with no sign-up.

  • 15questions
  • 3 minor so
  • €0no commitment
  • 0data sent

Your answers never leave your browser. Nothing is sent: the results are worked out on your screen. You can check it in your browser's Network tab: no request goes out when you answer.

1

See

Does what happens on your systems leave a trace someone can read?

01Are the logs from your workstations, servers and remote access gathered in one place?

An intrusion rarely shows in a single source.

02Do you know what in your company can be reached from the internet?

It is the first door attackers try.

03Would you be warned if a log source stopped sending?

A silent source looks like a quiet week.

2

Read

An alert is only worth something if someone reads it in time.

04Is someone in charge of reading security alerts?

Without a name, an alert belongs to everyone, so to no one.

05Is an important alert looked at the same day?

This delay can be measured, and shortened.

06Are nights and weekends covered?

An attack does not keep to your office hours.

3

Decide

On the day of the incident, does everyone know what to do?

07Does a written procedure say what to do in an incident?

One page is enough, if it exists before the incident.

08Do at least two people know how to isolate a workstation and block an account?

The action that contains an incident must not wait for someone to come back from leave.

09Have you ever run a crisis exercise, even a tabletop one?

You find the gaps in a procedure by playing it out.

4

Prove

Afterwards, can you show what was seen and decided?

10Are the decisions taken on an alert recorded: who, when, why?

It is the first thing you will be asked after an incident.

11Are your logs kept long enough to trace an intrusion back?

An intrusion is often discovered late.

12Could you hand a clear file to your insurer or to an authority?

A file is easier to prepare before than after.

5

Hold

The basics that limit the damage when everything else has given way.

13Does two-factor authentication protect e-mail, remote access and administrator accounts?

A stolen password is no longer enough to get in.

14Do you have an offline backup, already restored to check it?

A backup that has never been restored is still a promise.

15Are security patches applied quickly, starting with what is exposed?

A published flaw quickly draws attention.

What next

Three possible next steps, none required

Go it alone

Most items need no tool, only a decision and a name. Start with the first three on your list.

Talk it through with us

A no-commitment conversation to go over your results together. You choose what you tell us.

Write to us

Try it on your alerts

The free edition runs on your machine, with no time limit and no outbound call.

Download

What this check-up is not

Not an audit, not a penetration test, not a regulatory assessment. It is a first benchmark, inspired by the IT hygiene guide of ANSSI, the French national cybersecurity agency. For a first-level assessment led by a trained person, the French public scheme MonAideCyber also exists.

An incident under way?

This check-up can wait. The French public service 17Cyber directs affected organisations to assistance.

This site uses cookies. Technical cookies are required for the site to work and stay on at all times. Functional and audience-measurement cookies wait for your consent.

Customise