Docaposte Cyberdéfense - Contributions de l’utilisateur [fr]

Information de sécurité

2021-10-20T09:27:22Z

Scarpentier :

{| style="color: black; background-color: #ffffcc; width: 100%;"
| style="width: 30%; background-color: #EBECEC; text-align: center;"|
[[fichier:CSIRT.red.png|190px]]
| style="width: 70%; background-color: #EBECEC; text-align: left;"|
<span style="color:#000000"><br><br>'''Votre connexion vient d'être bloquée à destination des services de Docaposte. Veuillez vous rapprocher de l'équipe en charge du service'''</span>
<span style="color: #000000">'''Si vous pensez que cette restriction n'est pas justifiée, veuillez utiliser le formulaire de contact en y indiquant le numéro de support.'''</span>
<br>
<br>
====Informations techniques :====
*<span style="color: #000000">Support ID :</span> <span style="color: #FF5657">'''{{#urlget:_event_transid}}'''</span>
<br>
|}

2021-07-05T10:14:58Z

Scarpentier :

<btn class="btn-primary">
TLP:WHITE
C0
</btn>
=== <center><div style="color:#FFFFFF; background-color: #009EE0">'''Security contact'''</div></center> ===

We provide a security.txt file for structured security contact information. You may also use email, via csirt@docaposte.fr addresse, but please remember that email is unencrypted by default and should not contain confidential or security-related information.

=== <center><div style="color:#FFFFFF; background-color: #009EE0">'''Security statement'''</div></center> ===

The security of this site is of great importance and every effort is made to maintain industry-leading standards and processes. Security updates to all levels of software are implemented within a very short time-frame and the site is monitored constantly for modified files and unauthorised login attempts. Unless it is absolutely necessary to deliver the content or service you have requested, we do not record or process personal data. All links to third party sites are clearly marked and embedded content is identifiable and disclosed. For more information please refer to our privacy policy.

=== <center><div style="color:#FFFFFF; background-color: #009EE0">'''Disclosure policy'''</div></center> ===

If you believe this site has a security vulnerability, we would be very happy to hear from you, provided that you follow the terms of our disclosure process:

* The disclosure must be made following the contact procedure set out above.
* The disclosure may be made anonymously.
* The disclosure you make to us should relate directly to this site or to the email service associated with it.
* The disclosure must relate to a service in our control, rather than to a matter which is the responsibility of a third party providing a service to us.
*The disclosure must not be released to the public without our prior consent.
* Abusive or threatening language, harassment, impersonation, or any other kind of criminal activity, will be reported to the relevant authorities and pursued to the full extent of the law.
Automated penetration testing or unauthorised attempts to gain access to our site will be treated by us as a deliberate attack and be subject to legal action.
* The disclosure must relate to a matter set out below and specifically not to matters such as the exact configuration of our current security headers or to recently announced zero-day vulnerabilities:

** Information leakage, or leakage of personal data
** Unauthorised access at either user or root level
** Code injection
** Remote code execution

When a potential security issue is reported privately in accordance with these terms, we will check the issue and respond within one working week if you have provided valid contact details.

We will not take legal action against anyone who reports a security concern to us privately, in accordance with this policy, and without having undertaken intrusive testing. We are not currently able to offer ‘bug bounties’ or similar cash rewards, but, with your consent, we would be happy to publish an acknowledgement on this site to express our gratitude.

=== <center><div style="color:#FFFFFF; background-color: #009EE0">'''Thanks and acknowledgements'''</div></center> ===

CSIRT DOCAPOSTE would like to thank the following testers, researchers, and developers:

* '''SLCC LA POSTE'''

Security.txt

2021-07-05T10:14:46Z

Scarpentier :

2021-07-05T10:05:53Z

Scarpentier :

2019-11-13T20:11:15Z

Scarpentier :

{| style="color: black; background-color: #ffffcc; width: 100%;"
| style="width: 30%; background-color: #EBECEC; text-align: center;"|
[[fichier:CSIRT.red.png|190px]]
| style="width: 70%; background-color: #EBECEC; text-align: left;"|
<span style="color:#000000"><br><br>'''Votre connexion vient d'être bloquée à destination des services de l'Agence Nationale des Titres Sécurisés.'''</span>
<span style="color: #000000">'''Si vous pensez que cette restriction n'est pas justifiée, veuillez nous écrire par mail à : <br><span style="color: #cc0000
">[mailto:celluleweb-ants@interieur.gouv.fr?Subject=RWD_COSC_DCP:Accès%20refusé%20sur%20une%20ressource%20:%20{{#urlget:_event_transid}}&body=Veuillez%20indiquer%20la%20raison%20de%20l'%20accès <br> celluleweb-ants@interieur.gouv.fr]<span style="color:#000000">'''</span>
<br>
<br>
====Informations techniques :====
*<span style="color: #000000">Support ID :</span> <span style="color: #FF5657">'''{{#urlget:_event_transid}}'''</span>
<br>
|}