Chapter 10: Security and Personalization - Practical Intranet Development [Electronic resources] نسخه متنی

Chapter 10: Security and Personalization

Overview

Author: Jeffrey Haas

Intranet security options

Security policies

User directories and personalization

This chapter explains why securing an intranet is important and outlines a variety of approaches that can be taken. Once the decision about security has been made, you'll likely find that the personalization issue has simultaneously been decided. This is because the user identification process inherent in a security authorization scheme will naturally extend to customizing that user's experience according to their security profile or other extended settings. Then, when basic customization is occurring, it's not a very significant theoretical step towards complete personalization (by either the system or the users themselves).

It's important to remember that security can be implemented without personalization, but the opposite is not true. If your intranet's personalization engine isn't absolutely certain who your users are, customization with integrity will be impossible. That's why it's important for us to discuss intranet security first.

Intranet security isn't just about keeping people out. You should certainly consider the implications of placing sensitive business data on your intranet and what might happen if it falls into the wrong hands, but there are other aspects to consider as well. A secure intranet can empower your organization by giving employees an opportunity to freely share and exchange information for projects and corporate initiatives. If you can guarantee that limited groups of users will have access to sensitive data (year-end financial results or salary increases that are being discussed, for example), then all the benefits of interactivity and collaboration that are inherent to web-based applications can take effect.

If intranet users know that their data will only be accessible to appropriate parties, the adoption rate of functional areas will skyrocket. Strong security policies can make insecure users feel secure in their use of your intranet. Payroll, benefits, and training areas of a business, for example, could be integrated into an intranet and embraced by users if this sense of security existed, resulting in substantial cost savings for your company.

"If intranet users know that their data will only be accessible to appropriate parties, the adoption rate of functional areas will skyrocket"