.NET Framework Security

Determining What Is Being Protected

The first step in testing a secured assembly is to consider two points. First, you must understand what is conceptually being protected. Second, you must understand where your assembly is referencing those conceptual resources. This step is equivalent to understanding a software application's requirements before writing code for it. While it is tempting to try and jump to testing custom permissions or protected methods and properties, skipping this step can produce an end result that may not be what was really necessary.

Conceptual Resources

Unless you have detailed specifications for your secured assembly, this question can be the most difficult part of the whole process, because it involves defining abstract ...