GeekArticles
Microsoft
.NET Security


How to Avoid Creating a Network Security Hole with Your Windows Server-Based App
Nowadays it's quite common for us to write server-based applications. These apps differ from desktop applications in many ways - one of the most important of which is how they handle security. For a desktop application, security is easy. The application runs in the security context of the user who loaded it. Whatever the user has rights to, the desktop app has rights to, and nothing more. Server-based applications, on the other hand, run all the time and have their own security context, in addition to others they may impersonate.
Sponsored Links
Read Next: SQL Injection
Related Topics
.NET Security
- How To Implement Secure TCP Communications in Microsoft .NET 2.0
- How to Avoid Creating a Network Security Hole with Your Windows Server-Based App
- SQL Injection
- Cryptography: It's For Your Own Good
- Implementing Security For Web Applications
- Microsoft: ISA Vulnerability Could Allow Internet Content Spoofing
- Secure Service-Oriented Architectures
- Securing XML in the .NET Framework
- End-to-End Application Security
- Random Salt - Preparing for real-world eventualities