 |
 |
Screenshots |
|
|
|
Downloads |
|
|
|
Resources |
|
|
|
|
|
|
|
|
|
 |
|
|
As with any software product or network environment,
IntraLaunch is only as secure as you decide to make it. We understand
IntraLaunch may present a small security concern and have outlined a few steps below that would remove the already
minimal risk IntraLaunch may present.
 Customers who purchase a site license
can request a "secured" version of IntraLaunch
that will only work within a specific URL/domain. For example, a customer will receive a
custom build of IntraLaunch that will will only operate if the URL present in the web browser's location/address bar
starts with one of the following:
http://yourintranet.company.com/
https://yourintranet.company.com/
http://domain.company.com/portal/
file:
This provides an extra level of saftey and completely eliminates any minimal security risk associated with IntraLaunch making it the most secure
yet flexible solution available. You can specify your URL
when ordering online, or contact support.
- ActiveX is a security risk by itself. Its recommended that you disable
ActiveX in the "Internet" zone, and enable
ActiveX in the "Local intranet" zone only for specific sites including your Intranet. To do
this - from the Internet Explorer menu, click Tools, then Internet Options, then click
the Security tab to see a list of zones.
This will disable ActiveX content for the Internet. Then make sure you have ActiveX enabled for the Local intranet zone. Then add your
companies web server or Intranet address to the "Local intranet" Sites as shown below.
This will allow ActiveX and IntraLaunch to work inside of your Intranet only.
- Having your firewall filter and stop all packets with any number of IntraLaunch key words such as its ClassID (CLSID:0AE533FE-B805-4FD6-8AE1-A619FBEE7A23 for the trial version)
will stop web pages with IntraLaunch objects from even reaching the browser to begin with.
- The Internet Explorer Administration Kit
from Microsoft will allow you to better control IE setting and restrictions for
a large number workstations. Although untested, you should also be able to use this
to disable specific ActiveX content
or stop IntraLaunch/Particle Software components from running outside of the "Local intranet" zone.
|
