Thunderbird/Security: Difference between revisions
Jump to navigation
Jump to search
(Create a Security page for Thunderbird) |
m (→Introduction: Add vulnerability management and incident response as security engineering activities) |
||
| Line 10: | Line 10: | ||
## Analyzing risk (and then mitigating it) by performing threat analysis and risk assessment. | ## Analyzing risk (and then mitigating it) by performing threat analysis and risk assessment. | ||
## Finding vulnerabilities in Thunderbird. | ## Finding vulnerabilities in Thunderbird. | ||
## Vulnerability management and incident response activities. | |||
# Security Software Engineering | # Security Software Engineering | ||
## Maintaining/building security-related code (the Security component) | ## Maintaining/building security-related code (the Security component) | ||
Revision as of 21:14, 21 June 2018
(Note: This page is an active work in progress)
Introduction
Thunderbird cares very strongly about the security and privacy of its users. To this end, there are various security-related activities maintained by the community that this page attempts to document.
There are two main aspects to security-related work:
- Security Engineering
- Designing Thunderbird to prevent vulnerabilities.
- Analyzing risk (and then mitigating it) by performing threat analysis and risk assessment.
- Finding vulnerabilities in Thunderbird.
- Vulnerability management and incident response activities.
- Security Software Engineering
- Maintaining/building security-related code (the Security component)
- Including strong security standards and technologies when appropriate.
- Building/researching new security-related features to improve the security of our users.
Security Engineering
Write me.
Security Software Engineering
Write me.
Mozilla Involvement
Write me.