Page History
...
Each snapshot is a listing of permission settings on a SQL Server instance at a particular point in time. Snapshots help you assess and manage your security settings. This provides a powerful tool you can use to diagnose security problems and quickly see where changes occur.
The Snapshot Summary displays the following sections:
- Snapshot properties. Gives general information about the snapshot, the status, the collection time, the duration, whether it is its marked as a baseline snapshot or not, and any additional comments.
- Audit Summary. Displays the main summary information retrieved by the snapshot such as number of objects, permissions, databases, logins, windows accounts, OS controlled windows groups, and whether Weak Password Detection is enabled or not (Click here to enable/disable Weak Health Detection)
- Accounts. Windows accounts, OS Windows accounts, Suspect Windows accounts, Suspect OS Windows accounts, Unavailable databases, and Filters.
...
Baseline snapshots are snapshots that will not be deleted in the grooming process. To mark snapshots as baseline, you can right-click the snapshot and choose Mark as Baseline.
When a snapshot should be marked as baseline | Importance |
---|---|
When you take your first snapshot | To have a starting point to use to identify changes to permissions over time |
At the end of the month, quarter, or year | To track compliance to your database security policies |
When you implement a new security model | To identify unwanted changes or issues with the new model |
When you notice problems or irregularities in permission settings in a snapshot | To analyze the issue to correct problems and change permissions settings |
Tip | ||
---|---|---|
| ||
To view which snapshot is marked as baseline, click the respective SQL Server. The Audit History section of the Server Summary properties displays a list of all snapshots in this server where you can find a Baseline column that informs you which snapshot is marked as a baseline and which ones are not. |
...
In this situation, the server account specified on the Audited SQL Server Properties window should be an account that has been granted access to these external domains. This can be accomplished by either setting up two-way trusts between the account's domain and the external domains, or by creating pass-through accounts on all the external domains.
Scroll pdf ignore | |||
---|---|---|---|
IDERA Website | Products | Buy | Support | Community | About Us | Resources | Legal |