Archive for March 2011

Secedit command

By on March 28, 2011
This entry is filed under SQL Server and tagged .

The secedit command is a command-line tool that is used to configure and analyze security of a database. The syntaxes of using the secedit command are as follows:

  1. secedit /configure/db/cfg/overwrite/areas/log/quiet This syntax is used to configure the security.
  2. secedit /analyze /db/cfg/overwrite/log/quiet This syntax is used to analyze the security.

The parameters used with the above command are as follows:

/db: It provides the path to the database that contains security template.
/cfg: It specifies the path to the security template that contains default security settings.
/overwrite: It is used to empty the database during the process of importing the security template.
/areas: It specifies the areas where the security is to be applied. If this argument is not specified, all security settings in the security database are applied to the system.
/log: It specifies a file that is used to log the status of the configuration process.
/quiet: It specifies that the configuration or the analysis process should take place without prompting a user.

Share

Differnet logs that can be viewed with Event Viewer

By on March 25, 2011
This entry is filed under Uncategorized and tagged .

There are following three logs that can be viewed with Event Viewer:

  • System log: It is used to record events logged by the Windows operating system components. For example, the failure of a driver or other component of the system to load during startup is recorded in the system log.
  • Security log: It is used to record security events, such as failed login attempts. This helps to track changes to the security system and identify possible breaches to security. As an example, attempts to log on to the system may be recorded in the security log, depending on the audit settings in the User Manager. Only members of the sysadmin fixed server role can view the security log.
  • Application log: It is used to record events that are logged by applications. For example, a database application might record a file error in the application log.
Share

Requirements that should be met by certificates in order to be used for service broker security.

By on March 24, 2011
This entry is filed under SQL Server and tagged .

The requirements that should be met by certificates in order to be used for service broker security are as follows:

  • The key modulus should be less than 2048.
  • The key length should be a multiple of 64 bits.
  • The entire certificate length should be less than 32 kilobytes (KB).
  • It is necessary to specify a subject name and validity dates.
Share

Security modes to configure linked server

By on March 23, 2011
This entry is filed under SQL Server and tagged .

A linked server can be configured in any one of the following security modes:

  • Self-mapping: It is a process in which queries are resolved against linked servers through security credentials. When a linked server is added through the sp_addlinkedserver stored procedure, self-mapping is added for all local logins. The same login and password must exist on the remote server. This is the default behavior. Self-mapping is supported for all Windows logins if the linked server supports Windows Authentication.
  • Delegation: It is a process in which a Windows user who is connected to an instance of SQL Server can connect to another instance of SQL Server. The connection can be made by forwarding the user credentials. In this process, the user account is impersonated when connection to other instances is made.
  • Remote Credentials: This mode allows the user to map local logins to remote logins on the external data source.
Share

Security roles

By on March 23, 2011
This entry is filed under SQL Server and tagged .

There are two primary security roles that should be set up for securing SSAS management activities. These security roles are SSAS server role and SSAS database role. The SSAS security is based on Windows authentication only. SQL authentication used by the SQL Server database engine is not used in SSAS security.

Share

Security policy

By on March 22, 2011
This entry is filed under SQL Server and tagged .

A security policy is a document that is created to secure and manage a database server of an organization. The document contains rules and standards, which are applied on the server to protect data and the server from unauthorized intervention. The document includes the database objects, database and the instances that are to be protected and the steps to protect them.

Share

uCertify’s St. Patrick’s Day Sale!

By on March 18, 2011
This entry is filed under uCertify News, Uncategorized and tagged .

uCertify is again ready to give a great offer on this St. Patrick’s Day. You may get lucky at this day as you may buy any 3 prepkits for just $219.99 which is equivalent to $73.33 per prepkit from uCertify.This offer is valid for first 300 customers only. So what are you waiting for Hurry up!!! and go to grab this offer. This offers lasts from March 17-March 21.

Choose from over 300 IT certification prepkits, each backed by our 100% money back guarantee.

Happy Shopping & Happy Learning!

Your uCertify Team

http://www.ucertify.com

Share

Security modes

By on March 17, 2011
This entry is filed under SQL Server and tagged .

Microsoft SQL Server authenticates users and logins through security modes. SQL Server supports two security modes:

  1. Windows Authentication Mode (Windows Authentication).
  2. Mixed Mode (both Windows Authentication and SQL Server Authentication).
Share

Security principals

By on March 16, 2011
This entry is filed under SQL Server and tagged .

Security principals include the objects such as users, logins, groups and roles. These objects use the database to store and retrieve data as per the permissions granted to them. Groups and roles also contain other security principals so they can also be termed as collections. Security principals exists at three levels as follows:

  1. Windows level: It includes Windows domain logins, Windows local logins and Windows groups.
  2. SQL Server level: It includes SQL Server logins and roles.
  3. Database level: It includes database users, application roles, and database roles.
Share

Security log

By on March 15, 2011
This entry is filed under SQL Server.

Security log is used by SQL Server to record security events, such as failed login attempts. It can be used to track security breaches and any changes that might be made to the security system. The security log can be viewed only by those users who are the members of sysadmin fixed server role.

Share
Older Entries »