OWASP Backend Security Project SQLServer Hardening - Revision history

GPederzini1: /* Linked Servers */

2008-08-28T12:50:03Z

‎Linked Servers

2008-08-07T22:17:06Z

‎References

2008-08-07T22:12:05Z

‎References

2008-08-07T22:11:51Z

‎References

2008-08-07T22:11:34Z

‎References

2008-08-07T22:11:19Z

‎References

2008-08-07T11:30:22Z

‎System Stored Procedure

2008-08-06T22:44:19Z

‎Roles and Schemas

2008-08-06T21:27:26Z

‎Symmetric Keys

2008-08-06T21:22:48Z

‎Symmetric Keys

@@ Line 425: / Line 425: @@
   DBCC TRACEON (3625, -1)
-=== Linked Servers ===
 === Execution Context ===

← Older revision		Revision as of 22:17, 7 August 2008
Line 708:		Line 708:

	http://support.microsoft.com/kb/932881/en-us		http://support.microsoft.com/kb/932881/en-us
		+
		+	http://msdn.microsoft.com/en-us/library/ms161948.aspx
		+
		+	http://www.mombu.com/microsoft/sql-server-security/t-security-confusion-with-db-chaining-in-2005-287837.html
		+
		+	http://weblogs.sqlteam.com/dang/archive/2008/02/09/Security-with-Ownership-Chains.aspx

@@ Line 705: / Line 705: @@
 = References =
 http://www.microsoft.com/sql/technologies/security/default.mspx
 http://support.microsoft.com/kb/932881/en-us

@@ Line 706: / Line 706: @@
 = References =
 http://www.microsoft.com/sql/technologies/security/default.mspx
 http://support.microsoft.com/kb/932881/en-us

@@ Line 706: / Line 706: @@
 = References =
 http://www.microsoft.com/sql/technologies/security/default.mspx
 http://support.microsoft.com/kb/932881/en-us

← Older revision		Revision as of 22:11, 7 August 2008
Line 705:		Line 705:

	= References =		= References =
		+	http://www.microsoft.com/sql/technologies/security/default.mspx
		+	http://support.microsoft.com/kb/932881/en-us

← Older revision		Revision as of 11:30, 7 August 2008
Line 271:		Line 271:

	REVOKE ALTER SETTINGS TO userToConnect		REVOKE ALTER SETTINGS TO userToConnect
		+
		+	Another extended stored procedure that must be mitigated is the one used to write in the Windows Registry. It's in the master database. Every created login belong to the database role "public". So to avoid that a login, with the public role in the master database could execute xp_regwrite, it's possible to revoke che EXECUTE right to the public role with
		+
		+	REVOKE EXECUTE TO public

	== Database Administration ==		== Database Administration ==

@@ Line 387: / Line 387: @@
   GO
   EXEC sp_addrolemember N'Role1', N'userName1'
   GO

@@ Line 679: / Line 679: @@
   CLOSE SYMMETRIC KEY symKeyA
   CLOSE SYMMETRIC KEY symKeyB
 === Passphrases ===

@@ Line 657: / Line 657: @@
 It's a little different when it's time to cypher a plain text with a symKeyB, protected by symKeyA, protected by asymKeyC (...)
-Symply the operations must be done from the most internal level until the external. In this case:
+Simply the operations must be done from the most internal level until the external. In this case:
 ) open the symKeyA protected by asymKeyC