Security/QA/TestPlans/Web Authentication: Difference between revisions

Jump to navigation Jump to search
m
Integrating feedback
m (UPdated revision history)
m (Integrating feedback)
Line 11: Line 11:
| JC Jones || Software Engineer || Engineering || Date || Email
| JC Jones || Software Engineer || Engineering || Date || Email
|-
|-
| (not assigned) || EPM || Product Management || Date || Email
| JC Jones || EPM || Product Management (acting) || Date || Email
|}
|}


Line 26: Line 26:
|-
|-
| 2017-10-04 || 1.1 || Matt Wobensmith || Sending for review
| 2017-10-04 || 1.1 || Matt Wobensmith || Sending for review
|-
| 2017-10-04 || 1.2 || Matt Wobensmith || Incorporating review feedback from RyanVM
|}
|}


Line 119: Line 121:
{| class="wikitable"
{| class="wikitable"
|-
|-
! ID !! Description / Threat Description !! Covered by Test Objective !!  Magnitude !! Probability !! Priority !! Impact Score  
! ID !! Description / Threat Description !! Covered by Test Objective !!  Magnitude !! Probability !! Discoverability !! Impact Score  
|-
|-
| RAC-1 || Incorrect authentication allows security bypass || TO-1, TO-2, TO-3 || 3-High || 1-Unlikely || 2-Moderate || 6
| RAC-1 || Incorrect authentication allows security bypass || TO-1, TO-2, TO-3 || 3-High || 1-Unlikely || 2-Moderate || 6
Line 144: Line 146:
* '''Probability:''' 1-Unlikely, ''2-Possible'', '''3-Almost Certain'''
* '''Probability:''' 1-Unlikely, ''2-Possible'', '''3-Almost Certain'''


* '''Priority:''' 1 - Low, ''2-Medium'', '''3-High'''
* '''Discoverability:''' 1 - Low, ''2-Medium'', '''3-High'''


'''Impact Score Breakdown:'''  
'''Impact Score Breakdown:'''  
Line 152: Line 154:


== Test Objectives ==
== Test Objectives ==
This section details the progression test objectives that will be covered. Please note that this is at a high level. For large projects, a suite of test cases would be created which would reference directly back to this master.
Verify that the feature works as designed, interacts well with normal use of Firefox, is stable and has secure code.
This could be documented in bullet form or in a table similar to the one below.


{| class="wikitable"
{| class="wikitable"
Line 198: Line 199:


== Testing Tools ==
== Testing Tools ==
Detail the tools to be used for testing, for example see the following table:
Testing requires access to Test Rail, as well as physical possession of USB keys.
 
{| class="wikitable" style="width:50%"
{| class="wikitable" style="width:50%"
|-
|-
Line 227: Line 229:
= Testcases =  
= Testcases =  
== Test Areas ==
== Test Areas ==
Note: This feature has no UI. Therefore, all test areas that involve UI are marked n/a or not applicable.
{| class="wikitable" style="width:80%"
{| class="wikitable" style="width:80%"
|-
|-
Line 316: Line 321:
|-
|-
| Temporary or permanent telemetry monitoring   
| Temporary or permanent telemetry monitoring   
|style="text-align:center;" | no ||
|style="text-align:center;" | yes ||  
|-
|-
| Telemetry correctness testing   
| Telemetry correctness testing   
|style="text-align:center;" | no ||  
|style="text-align:center;" | yes ||  
|-
|-
| Server integration testing   
| Server integration testing   
Confirmed users
651

edits

Navigation menu