Secure Coding Guidelines for Microsoft dot net Framework:
Throughout the computing history, security and accessibility have constantly been playing twins. Security becomes the evil twin when it comes at the cost of usability, or so becomes the accessibility when security is overlooked for the sake of utility. However, having malicious threats all around in today’s computing, security always deserves a closer attention.
You can realize better security using the evidence-based security and code access security mechanisms. The advantage of the .NET Framework is that most application code can simply reuse the infrastructure. Also there are instances when further security is required, built either by enhancing the security system or by using new ad hoc methods.
The first and foremost of the Microsoft .NET Framework Secure Coding Guidelines is that you should create blocks to obstruct malicious code from copying files that you don’t wish to share. Also, one must be careful enough to find a balance between security and usability in various scenarios by using the code.
Below explained gives an overview to many ways you can design a code to work with the security system.
Security-neutral code does not mess with the security system, meaning it only runs with whatever permissions it receives. Although applications that fail to catch security exceptions can result in an unhanded exception, security-neutral code still takes advantage of the .NET Framework security technologies.
There are many highlights in a security-neutral library that you need to understand in the security-coding. Your library acts as a tool for other codes to access some files or resources, which are rather elusive. Wherever you expose a resource, your code must do a security check before giving rights to perform a task or an operation.
Non-reusable Application Code
There are simple security systems where you don’t need a special coding. This applies when the code is part of an application that will not be called by other code. Nevertheless, one has to watch out for malicious code that may call your code. While code access security might stop malicious code from accessing resources, such code could still can read sensitive information.
Also, if your code accepts user input from the Internet or other unreliable sources, you must be careful about malicious input.
The topic of Microsoft .NET Framework Secure Coding Guidelines covers diverse topics from Securing Exception Handling, Security and User Input, Security and Remoting Considerations, Security and Serialization, to Dangerous Permissions and Policy Administration, and Security and Set up Issues and so on. Take a tour on the web to get more information on this.