ASP.NET has the built-in capability to address localization. Basically a web application has different set of resources to support different cultures. And it can select/render the contents with the right set of resources based on a user's culture.

ASP.NET 2.0 offers two mechanisms on selecting the right resources. One is called implicit localization, where an appropriate set of resources is automatically selected based on a user's language preferences contained within browser settings. All you need to do is make available the resources for each language/country and set the Culture="auto" and UICulture="auto" attributes in the Page directive. The other is explicit localization, where you can explicitly set the culture of a web application. To do that, you need to set the CurrentCulture and CurrentUICulture properties of the current thread in the Page_PreInit event. You may look at a short introduction on ASP.NET 2.0 localization at: http://www.ondotnet.com/pub/a/dotnet/2005/08/08/localizingaspnet20.html?page=1

Globalization can be defined as a need for web applications. It is the need to adapt the culture of a web interface to the user's culture. We have to address that need in our web applications in order to friendly and respectfully serve the global community. The question of how to address that need flexiblely and cost effectively is part of the discussion on web application architecture and design.

Some people have pushed the definition of globalization a little further. Under the stretched definition, globalization means adapting the web interfaces to not only the user's culture, but also the user's market segment or other characteristics. But I would call that kind of differentiation personalization. Personalization can be defined as a need to adapt the web interface layouts and web contents detailing product/service offerings, marketing messages, etc. to the characteristics of a group of users or an individual user. To offer personalization cost effectively and flexiblely would also require a good deal of consideration in application architecture and design. Though there are similiarities between globalilzation and personalization, I would suggest to confine the definition of globalization to adapting the culture of a web interface to the user's culture.

Localization is the set of processes and actions to localize a web interface to a user's culture. Localization means much more than translating the web contents from one language to another, such as name formatting, timestamp formatting and text directions.

1. Cross Site Scripting (XSS)

XSS flaws occur whenever an application takes user supplied data and sends it to a web browser without first validating or encoding that content. XSS allows attackers to execute script in the victim's browser which can hijack user sessions, deface web sites, possibly introduce worms, etc. Read more...

2. Injection Flaws

Injection flaws, particularly SQL injection, are common in web applications. Injection occurs when user-supplied data is sent to an interpreter as part of a command or query. The attacker's hostile data tricks the interpreter into executing unintended commands or changing data. Read more...

3. A3 - Malicious File Execution

Code vulnerable to remote file inclusion (RFI) allows attackers to include hostile code and data, resulting in devastating attacks, such as total server compromise. Malicious file execution attacks affect PHP, XML and any framework which accepts filenames or files from users. Read more...

4. Insecure Direct Object Reference

A direct object reference occurs when a developer exposes a reference to an internal implementation object, such as a file, directory, database record, or key, as a URL or form parameter. Attackers can manipulate those references to access other objects without authorization. Read more...

5. Cross Site Request Forgery (CSRF)

A CSRF attack forces a logged-on victim's browser to send a pre-authenticated request to a vulnerable web application, which then forces the victim's browser to perform a hostile action to the benefit of the attacker. CSRF can be as powerful as the web application that it attacks. Read more...

6. Information Leakage and Improper Error Handling

Applications can unintentionally leak information about their configuration, internal workings, or violate privacy through a variety of application problems. Attackers use this weakness to steal sensitive data, or conduct more serious attacks. Read more...

7. Broken Authentication and Session Management

Account credentials and session tokens are often not properly protected. Attackers compromise passwords, keys, or authentication tokens to assume other users' identities. Read more...

8. Insecure Cryptographic Storage

Web applications rarely use cryptographic functions properly to protect data and credentials. Attackers use weakly protected data to conduct identity theft and other crimes, such as credit card fraud. Read more...

9. Insecure Communications

Applications frequently fail to encrypt network traffic when it is necessary to protect sensitive communications. Read more...

10. Failure to Restrict URL Access

Frequently, an application only protects sensitive functionality by preventing the display of links or URLs to unauthorized users. Attackers can use this weakness to access and perform unauthorized operations by accessing those URLs directly. Read more...