Re: TS access and Virus issue

From: Steven L Umbach (n9rou_at_n0-spam-for-me-comcast.net)
Date: 10/19/04 

Date: Tue, 19 Oct 2004 17:28:29 GMT

If you can give that user TS access without being a local administrator, you
can minimize the risk. Otherwise is someone gets control of his computer
they may get control of your computer. If you can do such for that user,
make sure that you use complex passwords on your computer and enable an
account lockout policy that has a threshold of no less than ten bad
attempts. As far a viruses , you can greatly reduce the risk if you disable
clipboard and other mappings in the RDP properties for client settings
which would however affect all users connecting via TS. You can configure
RDP properties in Terminal Services Configuration/connections. I would also
make sure that the built in administrator account is not allowed to logon
through TS in it's account properties and consider giving the user logon
time restrictions if possible to minimize risk of someone trying to gain
access at times when there is no reason to allow that user access such as
nights and weekends perhaps or simply dictate to him the hours that he can
access the computer via TS. --- Steve

"Bjarni" <Bjarni@discussions.microsoft.com> wrote in message
news:9BCDE136-8F99-4CD4-B6C2-C9EAE7C93E1B@microsoft.com...
>I have a vendor that wants to have access to an application on my server, I
> was thinking about using TS, but I have concerns over viruses coming from
> the
> vendors network. This is a financial database that the vendor would be
> connecting to and he would not have access to any other areas of the
> server.
> Is my concern about viruses valid, or do I have nothing to worry about? I
> am
> also worried about overall security on the vendor site, if I give him
> access
> to my server and he has security breach then my security is breached
> also..
> right?. Hope someone can help me by shedding light on these issues

Relevant Pages

  • Re: It takes two to tango
    ... great nation was founded with freedom in mind, and this freedom is what we ... likely going to reproduce it so the vendor should be able to reproduce it). ... ASSUME the risk of making any information public. ... which melted the CPU onto the motherboard causing a downtime of 4 hours. ...
    (Bugtraq)
  • Re: Barack Obama Pits Space Explorers Against School Children
    ... control Iran and control al-Qaeda? ... There are lies associated with terror too. ... United States or some other major power. ... increase the existential risk, not reduce it. ...
    (sci.space.policy)
  • Re: Decompiler.NET reverse engineers your CLS compliant code
    ... > much of a risk that you may get hit by a bus tomorrow and won't need the ... of becoming useless in the unfortunate case that the vendor dissappears. ... >> with that kind of licensing. ... It does nothing to keep prices low ...
    (microsoft.public.dotnet.languages.vb)
  • Re: [Full-disclosure] To disclose or not to disclose
    ... If the issue really involves critical infrastructure you can ... organizations to step in and pressure the vendor to fix the issue ... put the security companies customer at risk. ...
    (Full-Disclosure)
  • To Provide a Patch or to Service Pack?
    ... information and assessed the risk to me and my organization, ... So what are the motivations for going down the service pack path as oppossed ... The vendor is attempting to save money which is not a bad thing. ... customers will not be greatly exposed to any risk so it is generally safe to ...
    (Bugtraq)