Planning your security model
A security model, just like a metadata model, has long-ranging implications. It's much easier to spend a few more days planning when you still have no content in the system than trying to migrate your content into a new model later.
This said, it's still better to go ahead with your best guess than get stuck in a planning stage forever! And yes, you can change your security model at any time—I'll show you how to mass-update your content in Chapter 9, Migrating Configuration.
The best way to get started is by reviewing the things that affect security.
Things that affect security
When using multiple security components together such as role-based, account-based, Web Content Management, and others you may decide to place more emphasis on one of the "locks" and keep others relatively open. For instance, when you rely on accounts to control your access to content hierarchies, you may decide to place most of your content into the Public
security group.
Also, when planning...