Re: Starting up: What contracts, agreements, waivers, etc do you use?

bartholomewbj_at_comcast.net
Date: 06/22/04

  • Next message: Martin Murray-Brown: "RE: Starting up: What contracts, agreements, waivers, etc do you use?" 
    To: pen-test@securityfocus.com
Date: Tue, 22 Jun 2004 10:54:45 +0000

    I would definitely go with the standard NDAs and the liability statements. One thing I personally would do, and I suggest everyone who is venturing out on their own do as well, is to consult a lawyer who has done this for other companies in the past. Sit down with them, go through everything you/your company expect to do, and have them draft up the leagl papers/binders for you.

    Once this is done for the first time, you will always have them for future use. There are a lot of things out there that people don't think of (i.e. - loopholes, laws, etc.), and a lawyer is just the person who would know them.

    I also suggest keeping a legal representation handy in the case of something going wrong. Not a bad idea, and it really costs next to nothing unless you use them.

    Good luck on your venture. The hardest part IMHO is finding the clients.

  • Next message: Martin Murray-Brown: "RE: Starting up: What contracts, agreements, waivers, etc do you use?"

    Relevant Pages

    • Re: OpenQM vs. Everything Else
      ... many MV VARs insist on keeping costs so low for their ... Pick/MV VARs, and by and large the VARs have been delivering. ... if clients are willing to pay extra for something that's not ...
      (comp.databases.pick)
    • Re: Multiple Sites and Multiple DCs
      ... > My vote is for SMTP services that registers themself by site and a change ... you can semi-force> clients at DC-less sites to use DCs at specific sites. ... > Actually the value of a DC-less site to define costs is pretty> doubtful -- since all the KCCs-DCs in the actual sites will> just use the lowest costs anyway and this site will be irrelevant> to replication except for the sum of the costs -- one might as> well just put in the direct Site Link with the sum. ...
      (microsoft.public.win2000.active_directory)
    • Re: Multiple Sites and Multiple DCs
      ... > My vote is for SMTP services that registers themself by site and a change ... you can semi-force> clients at DC-less sites to use DCs at specific sites. ... > Actually the value of a DC-less site to define costs is pretty> doubtful -- since all the KCCs-DCs in the actual sites will> just use the lowest costs anyway and this site will be irrelevant> to replication except for the sum of the costs -- one might as> well just put in the direct Site Link with the sum. ...
      (microsoft.public.windows.server.active_directory)
    • Re: Multiple Sites and Multiple DCs
      ... The problem with SMTP is that both clients and servers much ... >> algorithm uses site link costs when ascertaining the closest site. ...
      (microsoft.public.windows.server.active_directory)
    • Re: Multiple Sites and Multiple DCs
      ... The problem with SMTP is that both clients and servers much ... >> algorithm uses site link costs when ascertaining the closest site. ...
      (microsoft.public.win2000.active_directory)