Security/Testing: Difference between revisions
Ptheriault (talk | contribs) |
Ptheriault (talk | contribs) |
||
| Line 41: | Line 41: | ||
"include_fields": ["id", "summary", "whiteboard", "status", "resolution"], | "include_fields": ["id", "summary", "whiteboard", "status", "resolution"], | ||
"status": ["NEW", "UNCONFIRMED", "ASSIGNED", "REOPENED"], | "status": ["NEW", "UNCONFIRMED", "ASSIGNED", "REOPENED"], | ||
} | } | ||
</bugzilla> | </bugzilla> | ||
Revision as of 05:44, 2 January 2019
Firefox Security Testing Team
Security Testing, Auditing and Monitoring to keep Firefox secure
Contact
Email us at security-testing@mozilla.com.
To report a security issue on a given site, use the client bug bounty form here.
Activities
Release Security Testing
Security testing of features to mitigate implementation risk and catch common security flaws. Testing will be targeted on features identified by:
- Residual risk highlighted by Engineering Security Review process
- Triage upcoming desktop & mobile features to identify “risky” features/changes that warrant security testing (catch-all for features which missed security review)
Queue: https://mzl.la/2CVfuCn
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
Vulnerability management and measurement
Security Activities in in the post-release phase - monitoring of incoming security bugs, measuring features on the web, and security maintenance activities like monitoring for security issues in dependencies.
Security Auditing Projects
Target security testing projects not tied to a specific Firefox release:
- Testing of large browser features that span multiple releases (e.g. Web Payments)
- Testing of Firefox security components (e.g. Sandbox testing)
- Testing of areas of known weakness (e.g. components receiving frequent security issues)
Bugzilla query error
Query options must be valid JSON.1