FR White paper section? Security WP example.

Ouverte
  • Quelque chose ne va pas ?
#644 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
2/5
Temps estimé
1-3 heures
Accessibilité débutants
35/100
Type d'issue
Documentation
Clarté
Plutôt claire
Activité
À l'abandon
Stack technique
php
Domaine
documentation, security

Piste de recherche

Start by reviewing the linked security reporting guidelines, security and privacy pages, spam tools, and Cypress XSS example to check which claims and links are current. The issue proposes a security white paper section but does not specify its location or structure; agree on an outline and placement before drafting. Done means a reviewed section presents accurate recommendations and examples with working links.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

I get intermittent requests for white papers - typically on security and server recommendations. Not sure if docs would be the right spot, but... maybe?

Community Involvement in Risk Vulnerability Identification
Participant in HakerOne's vulnerability disclosure program https://hackerone.com/expressionengine?type=team
Security reporting guidelines and encouragement of users to report suspected vulnerabilities (https://github.com/ExpressionEngine/ExpressionEngine-User-Guide/blob/6.dev/docs/bugs-and-security-reports.md#security-reporting-guidelines)
 
Spam prevention
Native integration of Google reCaptcha (https://docs.expressionengine.com/latest/control-panel/settings/captcha.html#recaptcha-v3-settings)
Native spam module that uses machine learning to identify suspect content submissions (https://docs.expressionengine.com/latest/add-ons/spam.html#usage)
Ban access by IP, IP block, or referrer (https://docs.expressionengine.com/latest/add-ons/blocklist.html)
  
Tools for Website Administrators
Customizable Password Policies (https://docs.expressionengine.com/latest/control-panel/settings/security-privacy.html#password-security-policy)
User agent and IP Requirements for Login (https://docs.expressionengine.com/latest/control-panel/settings/security-privacy.html#require-user-agent-and-ip-for-login)
Recommendations for site hardening (https://docs.expressionengine.com/latest/security/general-tips.html#security-tips)
 
 Security and Privacy for End Users
Native tools to help achieve GDRP (General Data Protection Regulation) compliance (https://docs.expressionengine.com/latest/general/gdpr.html#gdpr-and-expressionengine)
Consent module for fine grained control over user consent to cookies (https://docs.expressionengine.com/latest/add-ons/blocklist.html)
Ability to anonymize user data (https://docs.expressionengine.com/latest/control-panel/member-profile.html#anonymize-user)
 
Automated Testing
Security checks built into automated testing. Here's an example of a Cross Site Scripting (XSS) check in our Cypress tests.

CVE (Common Vulnerabilities and Exposures) Reports
There have been no known critical level CVE exploits reported in our 20 year history
https://www.cvedetails.com/vulnerability-list/vendor_id-7662/Expressionengine.html

Langage dominant
CSS
Étoiles
22
Forks
79
Merge moyen
2 j 1 h
PR mergées (30 j)
6

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de ExpressionEngine/ExpressionEngine-User-Guide

Toutes les issues de ExpressionEngine/ExpressionEngine-User-Guide

Issues similaires

Plus d'issues Documentation

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.