Projects

Industrial group — security supervision centre

A single control room for six sites whose security systems did not talk to each other.

Reference
KP-2025-002
Sector
Enterprise and sensitive-site security
Country
Mali
Year
2025
Duration
6 months
Workshop and offices of an industrial site at the end of the day — editorial context image, unrelated to the sites of this project.

What stays on site and what goes up, schematic

01Equipped sites
Each site keeps its equipment and its ability to operate alone. Losing the link does not deprive it of its security.
02Local recording
Recordings never leave the site. A compromised link therefore exposes no history, only the present moment.
03Primary link
A dedicated link between the site and the central position. It carries only metadata and the streams actually being viewed.
04Second carrier
A backup path through a separate carrier. Two links from the same supplier fail together the day that supplier fails.
05Central position
Viewing, per-user rights, a log of every consultation. An extraction request goes back down to the site holding the sequence.
Schematic of the split described above. No site, no equipment count and no real route appears on it.Typical sizing figures, not measured on an installation. The retention period is a common one, to be settled with the data controller; the bandwidth share is what a metadata-only uplink calls for.
  1. 01

    The context

    Each site had its own monitoring position, its own instructions and its own incident log. An event at one site reached head office only in the weekly report. Intervention procedures differed from site to site with no justification for the difference.

  2. 02

    The mission

    Feed the six systems into a single position, harmonise operating procedures, and make the incident log common and usable.

  3. 03

    The architecture

    Dedicated links between the sites and the central position, with a backup path through a second carrier. Recordings stay on each site; only metadata and the streams being viewed are sent up, which cuts the bandwidth required and limits exposure if the link is compromised.

  4. 04

    Delivery

    Procedures were written with the site managers before any technical connection. Three threat scenarios the client considered realistic served as the reference, and each procedure was rehearsed before the position went into service.

  5. 05

    Results

    An event is qualified within minutes by a trained operator, under the same instruction whichever site is concerned. The common incident log makes it possible, for the first time, to compare sites with one another.

  6. 06

    What we take from it

    A supervision centre is not designed from the server room. Intervention procedures determine what needs to be fed up, not the other way round; starting with the connection leads to collecting a great deal and deciding very little.

Results

6
Sites connected
3
Threat scenarios rehearsed before commissioning
6
Months of programme

Technologies

  • Milestone
  • Wazuh
  • Graylog
  • MikroTik
  • Zabbix

Why some clients are not named here

We design security systems and information systems for organisations whose public exposure is an operational risk. The discretion we apply to their projects is the discretion we will apply to yours. Identities, architectures and contractual documents are shared with an identified organisation as part of a pre-qualification.

Request pre-qualification

Consultations · Pre-qualifications · Partnerships

A comparable requirement?

Site constraints differ from one project to the next, but the questions to settle recur. An initial technical discussion establishes whether the comparison holds.