securing the TS web access server 2008 agains the attacks
Hi
Almost every day I check 100's of unsuccessful logon attempts on my terminal server. TS Web access on server 2008 ent edition. Though I am using https/ssl certificate to encrypt my communications. My clients access this ts web access via 'https:/server.domainname.com'
How can I set up my configurations so that any one trying to establish connection via 'brute force, tsgrinder, etc etc which use dictionary attacks of various combinations should be disconnected after a couple of tries. I have also made unsuccessful logon attemps to 3 on this pariticular ts server local policy but still, attackers can establish and remain establish with this server. THere must be a way where anyone using these malicious programs should be disconnected automatically after a couple of attempts. How and where. I am trying to make this terminal server fully secured. Possible? Domain/enterprise admins have to waste alot of time to overcome security issues when easy articles like:
http://www.ethicalhacker.net/content/view/106/24/
are available.
Help plz
Almost every day I check 100's of unsuccessful logon attempts on my terminal server. TS Web access on server 2008 ent edition. Though I am using https/ssl certificate to encrypt my communications. My clients access this ts web access via 'https:/server.domainname.com'
How can I set up my configurations so that any one trying to establish connection via 'brute force, tsgrinder, etc etc which use dictionary attacks of various combinations should be disconnected after a couple of tries. I have also made unsuccessful logon attemps to 3 on this pariticular ts server local policy but still, attackers can establish and remain establish with this server. THere must be a way where anyone using these malicious programs should be disconnected automatically after a couple of attempts. How and where. I am trying to make this terminal server fully secured. Possible? Domain/enterprise admins have to waste alot of time to overcome security issues when easy articles like:
http://www.ethicalhacker.net/content/view/106/24/
are available.
Help plz
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
As an aside, the account lockout policies configured in Active Directory need to be applied to user accounts and not to the OU holding the TS servers.
I always recommend licensing the security technology package on an ISR -- it greatly expands the device's capabilites as a firewall and intrusion prevention device, which is really what you're looking for here. Once you have that licensed you're going to want to configure things like stateful packet inspection and NetFlow.
I always recommend licensing the security technology package on an ISR -- it greatly expands the device's capabilites as a firewall and intrusion prevention device, which is really what you're looking for here. Once you have that licensed you're going to want to configure things like stateful packet inspection and NetFlow.
ASKER
Here is where I am applying the policy (please see the image)
I have the license for Netflow (it only shows me the packets). May be to controll as you suggested I need security technology package on an ISR.
Well I think I should look for a solution via things which I alredy have. Please suggest if my policy is correctly applied. I have applied it on a GPO on a terminal server OU. RIght?
New-Picture--2-.bmp
I have the license for Netflow (it only shows me the packets). May be to controll as you suggested I need security technology package on an ISR.
Well I think I should look for a solution via things which I alredy have. Please suggest if my policy is correctly applied. I have applied it on a GPO on a terminal server OU. RIght?
New-Picture--2-.bmp
If your Active Directory functional level is Server 2008, you can use what's call "fine-grained password and lockout policies," which can be applied to security groups; if it's anything prior to 2008 then the only password policy that matters what's defined in the default policy. Fine-grained password policies are applied to users and global security groups, not to OUs.
For information about how this works take a look at http://technet.microsoft.com/en-us/library/cc770842%28WS.10%29.aspx
For information about how this works take a look at http://technet.microsoft.com/en-us/library/cc770842%28WS.10%29.aspx
ASKER
I have a firewall router cisco 2911, and its only forwarding ports 443 and 3389. I am using access-list 101. Is there anything more I can do with it? Help