Skip to content

[Security Overview FR version] Add the FR version for each documents in the Security Overview section#3681

Open
SC-Jerome-S wants to merge 3 commits into
masterfrom
feat/security-overview-FR-version-creation
Open

[Security Overview FR version] Add the FR version for each documents in the Security Overview section#3681
SC-Jerome-S wants to merge 3 commits into
masterfrom
feat/security-overview-FR-version-creation

Conversation

@SC-Jerome-S
Copy link
Copy Markdown
Contributor

@SC-Jerome-S SC-Jerome-S commented Apr 16, 2026

Add French translations to Security Overview documentation
This PR adds complete French translations to all Security Overview documentation files, making them bilingual (English/French).

Changes
Files modified: 15 security overview documents in overview

2000-01-01-application-security.md
2000-01-01-auditing.md
2000-01-01-backups.md
2000-01-01-business-disaster.md
2000-01-01-code-security.md
2000-01-01-compliance.md
2000-01-01-connectivity.md
2000-01-01-data-protection.md
2000-01-01-employee-security.md
2000-01-01-incident-support.md
2000-01-01-monitoring.md
2000-01-01-network-security.md
2000-01-01-operational-security.md
2000-01-01-physical-security.md
2000-01-01-third-parties.md

Implementation
Each file now includes:

Bilingual navigation links at the top (English version / Version française)
Anchor tags and for direct linking to each language version
Complete French translations of all content, maintaining technical accuracy
Updated modification dates to 2026-04-16
This ensures French-speaking users can access security documentation in their native language while preserving the original English content.

@benjaminach benjaminach requested a review from Frzk April 17, 2026 08:59
@SC-Jerome-S
Copy link
Copy Markdown
Contributor Author

@yanjost can you take a look?

@semgrep-code-scalingo
Copy link
Copy Markdown

Legal Risk

The following dependencies were released under a license that
has been flagged by your organization for consideration.

Recommendation

While merging is not directly blocked, it's best to pause and consider what it means to use this license before continuing. If you are unsure, reach out to your security team or Semgrep admin to address this issue.

MPL-2.0

@SC-Jerome-S
Copy link
Copy Markdown
Contributor Author

SC-Jerome-S commented May 29, 2026

Side note: I was going to propose a very small change to the jekyll-extlinks.rb but I think this is not the place. (my build was failling). So I removed the change to focus only on the security documents

@SC-Jerome-S SC-Jerome-S force-pushed the feat/security-overview-FR-version-creation branch from 45e0a79 to 68c2874 Compare May 29, 2026 17:03
@SC-Jerome-S
Copy link
Copy Markdown
Contributor Author

@Frzk I think I'll need your help to understand why my build fail :) I must be missing something
Thanks !

Copy link
Copy Markdown
Contributor

@Frzk Frzk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion: I think you could adopt a simpler way to put anchors for your titles.

suggestion: I've added a few other suggestions (abbreviations + remove deprecated addon mentions).

I've haven't found the issue with the build. The log mentions a faulty link to #scalabilité (the é is not OK, and should be replaced by e). But I haven't been able to find such a link in your PR :-/

Comment on lines +12 to +14
<span id="en"></span>

## English
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd rather benefit from Kramdown syntax and put it like this, which is cleaner:

Suggested change
<span id="en"></span>
## English
## English {#en}

Comment on lines +61 to +64
<span id="fr"></span>

## Français
{: #francais}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<span id="fr"></span>
## Français
{: #francais}
## Français {#fr}

Comment on lines +12 to +14
<span id="en"></span>

## English
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<span id="en"></span>
## English
## English {#en}

Comment on lines +36 to +39
<span id="fr"></span>

## Français
{: #francais}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<span id="fr"></span>
## Français
{: #francais}
## Français {#fr}

Comment on lines +12 to +14
<span id="en"></span>

## English
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<span id="en"></span>
## English
## English {#en}

Comment on lines +12 to +14
<span id="en"></span>

## English
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<span id="en"></span>
## English
## English {#en}

Comment on lines +41 to +44
<span id="fr"></span>

## Français
{: #francais}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<span id="fr"></span>
## Français
{: #francais}
## Français {#fr}

### Customer VPN

We offer the possibility to set up a VPN connection (OpenVPN) between your infrastructure and the Scalingo
We offer the possibility to set up a VPN connection (OpenVPN, IPSec) between your infrastructure and the Scalingo
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IPSec VPN addon has been deprecated:

Suggested change
We offer the possibility to set up a VPN connection (OpenVPN, IPSec) between your infrastructure and the Scalingo
We offer the possibility to set up a VPN connection (OpenVPN) between your infrastructure and the Scalingo


### VPN Client

Nous offrons la possibilité de mettre en place une connexion VPN (OpenVPN, IPSec) entre votre infrastructure et la plateforme Scalingo. Cela vous permet de connecter en toute sécurité votre infrastructure à la plateforme et de protéger vos données contre les accès non autorisés.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IPsec VPN addon has been deprecated.

Suggested change
Nous offrons la possibilité de mettre en place une connexion VPN (OpenVPN, IPSec) entre votre infrastructure et la plateforme Scalingo. Cela vous permet de connecter en toute sécurité votre infrastructure à la plateforme et de protéger vos données contre les accès non autorisés.
Nous offrons la possibilité de mettre en place une connexion VPN (OpenVPN) entre votre infrastructure et la plateforme Scalingo. Cela vous permet de connecter en toute sécurité votre infrastructure à la plateforme et de protéger vos données contre les accès non autorisés.

@@ -27,3 +34,32 @@ Our operations team is available 24/7 to respond to security incidents and to en
Our technical support team is available to assist you with any technical or security issues, Monday to Friday, from 9:00 AM to 12:00 PM and 2:00 PM to 6:00 PM CET/CEST. You can contact us via chat or email at [support@scalingo.com](mailto:support@scalingo.com).
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

non-blocking: we usually don't provide the mailto link. I'll let you decide whether you want to keep it or not :)

Suggested change
Our technical support team is available to assist you with any technical or security issues, Monday to Friday, from 9:00 AM to 12:00 PM and 2:00 PM to 6:00 PM CET/CEST. You can contact us via chat or email at [support@scalingo.com](mailto:support@scalingo.com).
Our technical support team is available to assist you with any technical or security issues, Monday to Friday, from 9:00 AM to 12:00 PM and 2:00 PM to 6:00 PM CET/CEST. You can contact us via chat or email.

Copy link
Copy Markdown
Contributor

@Frzk Frzk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion: I think you could adopt a simpler way to put anchors for your titles.

suggestion: I've added a few other suggestions (abbreviations + remove deprecated addon mentions).

I've haven't found the issue with the build. The log mentions a faulty link to #scalabilité (the é is not OK, and should be replaced by e). But I haven't been able to find such a link in your PR :-/

Copy link
Copy Markdown
Contributor

@Frzk Frzk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you'll have to provide an id for all titles containing a special chars. (Or update Jekyll config to handle them properly - I haven't check how to do that, but there might be a way :))


Chaque application est déployée dans son propre conteneur, qui est isolé des autres conteneurs s'exécutant sur le même hôte. Cela garantit que l'application est protégée des autres applications s'exécutant sur le même hôte. Les conteneurs sont également isolés du système d'exploitation hôte, ce qui fournit une couche supplémentaire de sécurité.

### Scalabilité
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should fix your build:

Suggested change
### Scalabilité
### Scalabilité {#scalabilite}


De plus, si activée, la fonctionnalité d'auto-scaling ajustera automatiquement le nombre de conteneurs en fonction, par exemple, de l'utilisation du CPU de l'application ou du nombre de requêtes qu'elle reçoit.

### Gestion des Dépendances
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### Gestion des Dépendances
### Gestion des Dépendances {#gestion-des-dependances}


Nous mettons à jour régulièrement les dépendances utilisées par la plateforme pour assurer qu'elles sont à jour et qu'elles ne contiennent aucune vulnérabilité de sécurité connue. Cela inclut les images de base utilisées pour construire les conteneurs, les bibliothèques et outils utilisés par la plateforme, et les dépendances utilisées par les applications déployées sur la plateforme.

### En-têtes de Sécurité
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### En-têtes de Sécurité
### En-têtes de Sécurité {#en-tetes-de-securite}

## Français
{: #francais}

### Contrôles Internes
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### Contrôles Internes
### Contrôles Internes {#controles-internes}


Nous effectuons des sauvegardes régulières des données hébergées sur la plateforme pour les protéger contre la perte de données. Les sauvegardes sont stockées dans un système de stockage redondant sécurisé différent des serveurs d'hébergement principaux et géographiquement distribué, pour garantir que les données sont protégées contre les pannes matérielles et autres catastrophes.

### Politique de Récupération
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### Politique de Récupération
### Politique de Récupération {#politique-de-recuperation}

## Français
{: #francais}

### Reprise d'Activités (PRA)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### Reprise d'Activités (PRA)
### Reprise d'Activités (PRA) {#pra}


Nous disposons de plans de reprise d'activités pour garantir la disponibilité de la plateforme en cas de catastrophe. Les plans de reprise d'activités comprennent des procédures pour restaurer le fonctionnement normal de la plateforme et pour garantir la disponibilité de la plateforme à nos clients. Ces plans sont testés régulièrement pour s'assurer qu'ils sont efficaces et que nous pouvons restaurer le fonctionnement normal de la plateforme en cas de catastrophe.

### Continuité des Activités (PCA)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### Continuité des Activités (PCA)
### Continuité des Activités (PCA) {#pca}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants