Security Policy
Here, security does not mean prevention of data loss due to technical failure, but preventing unauthroized access to data. Critical and confidential data is always a potential target for data abuse. But this is not the only threat. It is not that uncommon that not properly protected data is accidentally corrupted or lost, that is why a sound security policy is a must.
Talking about security policy is relevant in a networked environment and with large amounts of data, all of which should not be accessible to everyone. Security should be planned, in order to determine which users have access to which information, and which operations they can perform. Steps in making a security plan:
- Make a list of all objects and actions that should be monitored.
- Make a list of all users and user groups.
- Draw relations between the two lists.
Based on the results, implement the security policy in PANTHEON.
 |
WARNING
- To prevent access through domain accounts, PANTHEON creates a SQL Server login for each PANTHEON user, but one that is different from the domain account. See SQL Server Logins in PANTHEON.
- A domain account and PANTHEON user account can be linked, so that successful domain login will allow the user to logon to PANTHEON without entering a password. See Automatic Domain User Logon.
- Access to data within PANTHEON ca be restricted using authorizations.
|
The following sections will detail important aspects of the system's functionality:
|
How upgrading affects databases
|
This section explains how can PANTHEON accect databases. |
|
SQL Server Logins in PANTHEON
|
In this section, we discuss about PANTHEON creating a SQL Server login for each PANTHEON user and login. |
|
Automatic Domain User Logon
|
Apart from logon with a user name and password, PANTHEON also support domain user logon. With this, users don't need separate accounts for PANTHEON logon, it is enough if they are logged into the domain. |