This document defines and describes the main characteristics of the security management system that the Centreon teams implement around the Centreon Cloud product. Centreon's ISMS aims to follow security best practices and tends towards compliance with reference standards, such as ISO 27001.
We realize the importance for customers of the data entrusted to Centreon, and we apply strict security practices, always striving to improve, so as to guarantee the best protection level for the assets in our care.
Centreon relies on a committee dedicated to cybersecurity issues, which is led by the Chief Information Security Officer. His team is organized around 4 main areas:
- Product security
- Security of infrastructures and user environments
- Network and Cloud Security
- SOC/Incident response
This committee puts cybersecurity at the heart of its action, and plans each of its actions according to the principles of continuous improvement.
Centreon's executive team constantly keeps up with the latest developments in cybersecurity, as it makes security issues and data protection their number one priority. Risk analysis and a detailed review of these are carried out regularly in line with ISO 27001.
Centreon offers to all employees an onboarding process that includes security awareness training. Each department receives tailored support based on core knowledge and practices that apply to the whole company, including security and data protection best practices. We conduct regular training that reminds each department of the good practices, and issues and expectations concerning security.
Software development process
Development processes integrate security requirements and include security by design and continuous improvement practices.
Each development sprint and each architecture decision integrate security in a strict and tracked way, including elements such as access control, integrity or encryption. Development relies on the most tried and tested principles, practices and third-party elements.
Integration and release process
An automated and controlled continuous integration and delivery process allows us to implement measures and security checkpoints at each key stage of the development. These checkpoints use SAST and DAST tools, but also systematic peer reviewing by 2 experienced developers. The tools used by the Centreon teams include development security standards such as OWASP Top 10.
Each stable version that is delivered has gone through quality checks carried out by dedicated QA engineers. External users (community or enterprise users) are also able to test and use any beta versions by pulling the packages from public “unstable” repositories.
The Centreon Cloud services are all hosted by Amazon Web Services (AWS). Centreon Cloud relies on the physical security as well as the quality of AWS infrastructures and networks to offer customers a level of security ranked among the strictest in the world.
AWS's hosting services meet the compliance requirements of the standards and programs most recognized in the world. (See the AWS Compliance program.)
In addition, Centreon Cloud has passed the Foundational Technical Review (FTR) and AWS Well-Architected Framework (WAR) reviews. These reviews have allowed Centreon to integrate the AWS Partner Network, and guarantee our customers will enjoy a service that is in compliance with the best practices as to architecture, account management, logging, disaster recovery and business continuity, and continuous improvement.
The Centreon Cloud services are all hosted and run from the European Union:
|Centreon Cloud||AWS EU Ireland Region (eu-west-1)||France|
More information on AWS's security and compliance practices here.
The Centreon infrastructure includes dedicated network security equipment at each change of zone. Additional equipment such as software firewalls, intrusion detection or protection software, or flow analysis are implemented and monitored closely. Strict controls are applied to the flows to allow the safe transit of customer data.
Admin access to the product is strictly limited to duly authorized administrators. Centreon takes steps to control all actions and to guarantee that malicious actions are detected.
Authentication and authorization
Authentication is strictly personal. Authorization to access the infrastructure is multi-factor (authentication, access from an authorized network, access from an authorized device). Authentication and authorization are subject to continual security and compliance checks.
Centreon has access to and analyzes infrastructure logs provided by AWS. These logs are subject to continual security and compliance checks.
Data entrusted to Centreon is protected by symmetric and asymmetric encryption systems, depending on usage. This meets the current best practices, whether the data is in transit or static. Data in transit is encrypted using an up-to-date and maintained open source technological solution. Static data is encrypted using AWS mechanisms, reinforced by a key generated by Centreon. The Centreon Cloud services use a Public Key Infrastructure to manage, store, distribute and destroy encryption keys and certificates. Centreon uses protocols, certificates, algorithms and software that are up-to-date to guarantee the security of data, whatever its state.
|Communication protocols||TLS 1.2/TLS 1.3|
|Certificates||RSA 2048 bits|
|Algorithms||PKCS #1 SHA-256 with RSA encryption|
|Software||OpenSSL v1.1.x, OpenVPN 2.4.x|
Centreon guarantees to their clients that the application is configured in a secure manner. Actions on product configuration are only performed by certified employees. It relies on orchestration and automation that guarantee the resilience, robustness and standardization of the service that is offered.
Authentication and access to the platform's administration
Admin access to the product is strictly limited to duly authorized administrators. This authorization is multi-factor (authentication, access from an authorized network, access from an authorized device).
User access to the product is strictly limited to duly authorized users. This authorization can be multi-factor, depending on the customer's requirements and their ability to make their environment secure (radius authentication, MFA, network security and filtering, etc). Customers can configure their user accesses and authorizations using Centreon's CIAM (Customer Identity and Access Management) portal. This portal uses OpenID Connect, and can be configured to use the customer's own identity provider.
Centreon holds the application logs and checks them regularly. Logs are kept for 12 full months.
Centreon actively monitors infrastructure and services to detect any event or anomaly that could impact the security of the product it delivers. Reporting, escalation and internal crisis management processes are implemented and tested several times a year.
Centreon Cloud's architecture and design make the service resilient to breakdowns and technical incidents by default.
Automation and orchestration mechanisms guarantee a quick restoration of the service provided to customers.
Centreon has a process that allows for effective receipt and processing of vulnerability reports. If you believe you have found a security vulnerability, please report it to us as described in the reporting process.
Centreon has processes and multilayer security tools that make it possible to proactively detect anomalies with code or infrastructure that could introduce vulnerabilities. This multilayer security includes internal human control, automatic analysis and external security audits.
Centreon categorizes any reported or detected vulnerabilities and assesses their severity using the CVSS (version 3.1) methodology. An adequate action plan is then set up, resulting in the correction of the vulnerability.
Centreon implements all necessary means to handle any discovered vulnerabilities. Centreon's commitment is to mitigate and fix any reported vulnerabilities in the following manner:
|CVSS score||Mitigation deadline||Fix deadline|
|9.0 - 10||24h||As soon as possible|
|7.0 - 8.9||48 working hours||30 days|
|4.0 - 6.9||96 working hours||180 days|
|0.1 – 3.9||120 working hours||365 days|
|CVSS score||Mitigation deadline||Fix deadline|
|9.0 - 10||24h||As soon as possible|
|7.0 - 8.9||48 working hours||8 days|
|4.0 - 6.9||96 working hours||15 days|
|0.1 – 3.9||120 working hours||30 days|
Note: Fixing infrastructure vulnerabilities can be subject to extended time limits and can depend on providers publishing fixes (hosting provider, OS publisher). Centreon commits to react as soon as possible should such a scenario arise.
Centreon does not offer a structured rewards plan for reporting vulnerabilities. Specific talks can be started according to the severity of the reported vulnerability.
Outsourcing and uninterrupted service
Centreon strengthens its ability to deliver service partly by using outsourcing. Qualified outsourcers hold the best AWS qualifications and skills, and take action within a security framework that has been strictly approved by Centreon. This outsourcing allows Centreon to guarantee an uninterrupted service and watch over the AWS infrastructure.
Centreon commits to security and quality processes based on continuous improvement. In the same way as for its products, Centreon audits, reviews and improves its security governance (including this document) regularly. This governance will be reviewed, possibly revised, and adequately validated at least once a year.
Communications about security
Centreon communicates on an ad hoc basis via the usual channels (direct communication by email, via The Watch, or through the support team).
Centreon communicates actively with the relevant authorities in case of a significant vulnerability or personal data breach.
Centreon strives for transparency and communicates about vulnerabilities to the public reference frameworks (MITRE).
Centreon carries out a complete audit of Cloud services on an annual basis, complemented by control audits on an ad hoc basis. The key points of this process will be shared by Centreon; more details can be provided to customers under certain conditions.