April 2002
Intermediate to advanced
816 pages
20h 56m
English
You are now in a daunting position: You need to design for security in a new software component you're about to develop, but the concept of security is a slippery one. How exactly do you “design for security?” Where do you even begin?
Remember our discussions of trust and responsibility in the previous chapter? When we look at the problem in those terms, we see that our principal concern is interacting with code of a lower (or undetermined) level of trust. The system administrator will handle assigning trust through the use of a security policy. The .NET Framework security system will take care of sandboxing each unit of code (that is, each assembly) into ...
Read now
Unlock full access