|
Posted by Brian Delaney [MSFT] on November 8, 2006, 10:03 am
Please log in for more thread options Hi Michael,
>And how about protection of the network transport of GPO?
Are you referring to the application of a GPO over the network or
modifying? As far as I know by default all that is done to secure both is
SMB signing is required on Windows Server 2003 SP1 (possibly RTM as well)
and can be set to required on Windows 2000. SMB signing helps to prevent
an SMB session from being highjacked once established.
Hope this helps,
Brian Delaney
Microsoft Canada
--
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>Date: Wed, 08 Nov 2006 00:49:21 +0100
>User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.13)
Gecko/20060417
>X-Accept-Language: en-us, en
>MIME-Version: 1.0
>Newsgroups: microsoft.public.windows.server.security
>Subject: Re: GPO for trusted root CA certs
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>
>Brian,
>
>thanks for your quick answer.
>
>Brian Delaney [MSFT] wrote:
>>
>> So, I guess you could say that it secured in two ways. First of all you
>> have to have permissions to write to the SYSVOL\Policies folder to
>> create/modify a GPO and secondly you have to have permissions to the
gplink
>> and gpoptions attribute at the level you wish to link the policy.
>
>And how about protection of the network transport of GPO?
>
>Ciao, Michael.
>
|