Engie: EBIOS RM Risk Analysis on Azure

CASE STUDY · ENERGY & UTILITIES

A risk analysis of the group's Cloud platform, then a security approach built into application projects.

Two successive engagements for the ENGIE group IT department: the EBIOS RM risk analysis of the Azure Cloud platform in 2022, then the industrialisation of an EBIOS-type approach across application projects in 2023.

Engie : Adservio case study
Client
ENGIE Group
Expertise
EBIOS RM risk analysis · ISO 27005 · Cloud security
Tech Stack
Azure · EBIOS RM · ISO 27005 · DICT criteria
Engagement
4 experts · 2022 and 2023
CONTEXT

Project Context

The ENGIE group IT department wanted to analyse the risks weighing on Microsoft's Azure Cloud platform: to make sure it met the needs and stakes of the business, and complied with the group security policy.

Beyond this first analysis, the challenge was to industrialise the approach: to build an EBIOS-type approach into application projects from their inception, alongside the architects and the business CISOs.

Strategic Objectives

(01)

Business needs

Make sure the Azure Cloud platform meets the needs and stakes of the group's businesses.

(02)

Group security policy

Check that the platform complies with the ENGIE group security policy.

(03)

Industrialised risk analysis

Turn Cloud risk analysis into a repeatable approach, built into application projects.

Solutions Delivered by Adservio

Adservio worked in two stages: in 2022 with a delivery manager, a senior ISO 27005 / EBIOS RM consultant and a Cloud security consultant; in 2023 with a delivery manager, a senior consultant and two ISO 27005 / EBIOS RM consultants.

(01)

Questionnaires and interviews

Risk questionnaires and interviews with the business, the CISOs and the suppliers, to capture security needs and stakes.

(02)

Cloud EBIOS RM analysis

EBIOS RM risk analysis of the Azure platform following ISO 27005, a risk level matrix and a proposed action plan.

(03)

Designing the approach

Design of an EBIOS-type approach for application projects, with contributions to the working group bringing security into the group's project processes and to the design of the tooling.

(04)

Pilot run

The approach run as a pilot, with security needs defined from the inception phase of projects.

(05)

DICT criteria

Project security needs characterised against DICT criteria (availability, integrity, confidentiality, traceability), taking business impacts into account.

(06)

Measures and residual risks

Technical risk analysis, security measures built into application architectures and residual risks formalised.

A one-off risk analysis,
turned into a group approach.

Starting from the EBIOS RM analysis of the Azure Cloud platform, the engagement led to a security approach built into application projects from their inception, carried by the architects and the business CISOs.

Results

In two years, a one-off risk analysis became a security approach shared across the group. The risks of the Azure Cloud platform are identified, ranked in a matrix and paired with an action plan to reduce them. Areas of non-compliance are mapped at group level and for each department. And security now enters application projects from their inception, with needs expressed against DICT criteria and measures built into the architectures.

TALK TO AN EXPERT

Secure your Cloud projects from the design stage

EBIOS RM risk analysis, ISO 27005, security built into projects: let's discuss your Cloud cybersecurity challenges. An Adservio expert gets back to you within 24h.

By submitting this form, you agree to our privacy policy.