Skip to content
Technology transformation expertise firm · ARDIANE Group Innovate, secure, succeed

Glossary

Security accreditation (homologation de sécurité): definition, applicable texts and process

Domain

Cloud and platforms

In brief

Security accreditation (homologation de sécurité) is, under Article 4-3 of French Decree No. 2019-1088 of 25 October 2019, a formal decision attesting that security risks have been identified, that the necessary measures are implemented and that residual risks are accepted. This article requires security accreditation before the components of the State information system are put into service, unless exempted.

Page contents

Definition of security accreditation

Security accreditation (homologation de sécurité in French) is, under Article 4-3 of Decree No. 2019-1088 of 25 October 2019, “a formal decision taken by the authority qualified in information systems security or by any person to whom it delegates this function” (our translation, as for the quotations below). It attests “that the risks to security have been identified and that the measures necessary to control these risks are implemented”, and that any residual risks have been identified and accepted.

The same article requires it for the infrastructure and software services of the State information system “prior to their implementation”, unless exempted by order. ANSSI more broadly describes a decision by which risks are accepted “at the highest level of an organisation” and which allows the system to be put and kept into service (document “L’homologation simplifiée”, on its MonServiceSécurisé service).

The texts that provide for it

The State information system. Article 4-3, created by Decree No. 2022-513 of 8 April 2022 and in force since 1 October 2022, is cited here in its version of 24 April 2023.

Administrative authorities. Decree No. 2010-112 of 2 February 2010 requires them to identify risks and set security objectives (Article 3), then to attest “formally” to users that the system is protected in accordance with these objectives (Article 5). The word homologation does not appear in it. ANSSI presents the référentiel général de sécurité (RGS, general security framework), whose version 2.0 was approved by an order of 13 June 2014, as the text that requires online public services to be accredited. Ordinance No. 2005-1516 of 8 December 2005 counts State administrations and local authorities among these authorities, and covers systems for electronic exchanges with users or between administrative authorities (Article 1).

Classified information. Article 4-3 reserves the accreditation provided for by Article R. 2311-6-1 of the French Defence Code. On this subject, ANSSI cites General Interministerial Instruction No. 1300, approved by order of 9 August 2021.

The process described by ANSSI

The document “L’homologation simplifiée” distinguishes, after a scoping phase, three stages: assessing security needs, securing, then preparing the decision (scope, file and accreditation committee). The effort is proportionate across three levels: simplified, intermediate or reinforced process.

According to this document, the written decision states in particular the system and its scope, its date and its period of validity, which the authority sets without exceeding three years. For projects run in an agile way, the document calls for security to be built in from the first line of code, which is what our entry on DevSecOps describes.

Accreditation, qualification, certification, audit: not to be confused

Notion Concerns Who decides
Accreditation An information system in its context of use The accreditation authority of the organisation answerable for it
Qualification A security product or a provider’s service, such as a cloud service for SecNumCloud ANSSI or an approved body
Certification Conformity with a standard, for example ISO/IEC 27001 A third-party body
Security audit The vulnerabilities found in a system The auditor, through findings and recommendations

The NIS2 directive, which requires risk management measures from entities, falls under a different framework.

Example: a portal hosted in the cloud

Take a ministry preparing a portal for submitting applications, hosted by a cloud provider: Article 4-3 requires a decision before it is put into service.

In our reading, qualified hosting does not replace this decision: qualification concerns the provider’s service, accreditation the system that uses it. ANSSI links the accreditation scope of a hosted system to the contractor’s level of responsibility.

The expected level of hosting depends on the “cloud au centre” doctrine and is the subject of our page on sovereign cloud. In the reinforced process, ANSSI lists a resilience plan among the documents in the file: our page on cyber resilience covers business continuity and recovery.

The procurement and management framework for these projects is presented on our public sector page.

FAQ

Frequently asked questions

Another question? Ask us

Who issues a security accreditation?

A security accreditation is issued by an accreditation authority. For the State information system, Article 4-3 of Decree No. 2019-1088 of 25 October 2019 designates the authority qualified in information systems security, or any person to whom it delegates this function. For other organisations, ANSSI (the French national cybersecurity agency) describes the accreditation authority as the person at the highest hierarchical level of the entity responsible for the system, for example the mayor of a municipality, who may delegate this role in writing.

Is security accreditation mandatory?

Security accreditation is mandatory, before they are put into service, for the infrastructure and software services of the State information and communication system: this is the purpose of Article 4-3 of Decree No. 2019-1088 of 25 October 2019, created by Decree No. 2022-513 of 8 April 2022. The same article refers the cases of exemption to an order of the Prime Minister. ANSSI states that it is also mandatory for administrative authorities, local authorities included, under the référentiel général de sécurité (general security framework). The situation of a given body is checked with its information systems security officer and its legal department.

How long does a security accreditation remain valid?

The period of validity of a security accreditation is set by the accreditation authority and stated in the decision. According to the document "L'homologation simplifiée" (simplified accreditation) published by ANSSI, it must not exceed three years, and a period of less than six months is not recommended. The same document provides for renewal on expiry, or earlier in the event of a significant change to the system, its environment or the risks.

What is the difference between accreditation and qualification?

Security accreditation concerns an information system in its context of use: it is decided by the organisation answerable for it. Qualification concerns a security product or the services of a provider: Decree No. 2010-112 of 2 February 2010 has it issued by the Director General of ANSSI for a product, and by an approved body for a trust service provider. The first accepts risks, the second attests conformity with a framework.

Does security accreditation concern private companies?

According to ANSSI, the security accreditation obligation mainly concerns public entities, but also certain regulated private companies. Outside any obligation, the agency presents the process as a security management practice that any organisation is encouraged to adapt. Its application to a given company is checked in the texts specific to its sector.

A project to bring to completion?

A first conversation is enough to understand your challenge, identify the right people and tell you frankly what we can bring.