This fourth step for testing a secured assembly is the culmination of work for the first three steps:
Define what is being protected as specifically as possible.
Understand how resources are being protected.
Test any custom permissions that are used to protect resources.
This step asks how well the assembly design was implemented in the secured assembly. To address this point, it is especially important that you have the list of methods and properties being protected from the first step.
To test the methods and properties that should be protected, there are two primary actions that must occur. First, the methods and properties should be checked to see if they implement ...