SLT-Services · Digital

Log analysis and IT monitoring

Know what is happening in your servers, networks and applications: we collect and analyse your logs, monitor your infrastructure and alert you before an incident costs you time or money.

Our services

See in real time, understand, anticipate

LOGS

Log collection and analysis

Centralising the logs of your servers, firewalls and applications to trace the origin of an incident.

MONITORING

Infrastructure monitoring

Monitoring the availability and performance of your networks, servers and sites, with automatic alerts.

DETECTION

Anomaly detection

Spotting unusual behaviour: suspicious logins, traffic spikes, repeated errors.

DASHBOARDS

Indicators and reports

Readable dashboards and regular reports for management and technical teams.

SETUP

Tool installation

Deployment and configuration of monitoring tools suited to your environment.

INCIDENTS

Post-incident analysis

Reconstructing what happened, likely causes and measures to prevent a recurrence.

Your needs

What you are looking to solve

01

“My site or my network went down, why?”

Finding the cause of an incident in the logs.

02

“I want to be warned before the outage”

Alerts on availability and critical thresholds.

03

“I need to prove what happened”

Traceability of access and actions, useful for audits.

Method

How an engagement works

01

Scoping

Discussion of your infrastructure and your challenges.

02

Collection

Setting up the flow of logs and measurements.

03

Analysis

Reading the data, spotting anomalies.

04

Follow-up

Dashboards, alerts and regular reports.

Every engagement is carried out by our team, supplemented where needed by experts brought in for your project.

Who it is for

Our clients

01

SMEs & companies

To keep systems available.

02

Institutions & local authorities

For traceability and monitoring of digital services.

03

Hotels & multi-site organisations

To monitor several sites remotely.

Predicting an incident: reading weak signals

An attack is almost always preceded by discreet signs. The problem is not a lack of signals, it is that nobody looks at them.

What we see before an incident

  • Unusual log-ins (time, country, device)
  • An abnormal rise in failed log-ins
  • Accounts whose behaviour suddenly changes
  • Access to resources never used before
  • Discreet spikes in outgoing traffic

A real case

A company suffers a ransomware attack on a Monday morning. After analysis: VPN log-ins at 3 a.m. in the previous days, an administrator account created on Friday, logs switched off for a while, permission tests on several servers. Everything was visible in the logs, but nobody was watching the correlations.

How to anticipate, in practice

Logs are most useful before an incident, not only after it.

  • Centralise critical logs: authentication, VPN, directory, firewall, workstations
  • Set up alerts on behaviour, not only on known signatures
  • Follow trends rather than isolated events: +300% access attempts is a signal, even if none succeeds
  • Define a normal baseline and question anything that departs from it
  • Hunt for threats regularly: 30 minutes a week is enough to spot the abnormal

A monitoring need?

Describe your infrastructure and we will propose a suitable engagement, with no commitment.

Request a quote