governance/wg-security

Security WG

Proactively ensures the Security of Electron as a project, responds to incoming incidents, and oversees rollout of fixes.

Membership

Avatar	Name	Role	Time Zone
	Samuel Attard @MarshallOfSound	Chair	PST (Vancouver)
	Charles Kerr @ckerr	Member	CST (New Orleans)
	Deepak Mohan @deepak1556	Member	?
	Cheng Zhao @zcbenz	Member	JST (?)
	Felix Rieseberg @felixrieseberg	Member	PST (San Francisco)
	Jeremy Apthorp @nornagon	Member	PST (San Francisco)
	Milan Burda @miniak	Member	CET (Prague)
	Pedro Pontes @ppontes	Member	CET (Prague)
	Steve Barbaro @StevenEBarbaro	Member	?

Current Objective and Key Results

Objective:

Electron is used/trusted by organizations with enterprise and corporate-high-security environments.

Key Results:

1. Increase adoption of Electron security best-practices & tooling in AFP and partner applications
2. Increase engagement of website security documentation (i.e. MOAR pageviews)
3. Increase measurable security for self-identified enterprise apps.

• Partner Applications: an app reporting feedback to Electron but outside the AFP
• AFP: App Feedback Program
• measurable security: an audit tool like https://github.com/doyensec/electronegativity, or self-report

Areas of Responsibility

• The reporting address: security@electronjs.org
• Coordinating fixes and disclosures of vulnerabilities
• Security of Electron as a project
  • Build infrastructure
  • Release tooling
  • Credential management
• Proactive measures
  • Fuzz testing
  • Pen testing
  • Security review of parts of the codebase
  • Security sign-off on IPC and certain API related changes

Associated Repositories

All repositories in the electron organization along with exclusive access to electron/security.

Rules for Membership

See Membership and Notifications

Meeting Schedule

• Sync Meeting 1hr Weekly @ Wednesday 9:30AM PT

Meeting notes may be viewed in meeting-notes as they become available.