KB: Web Interface Security - Revision history

Dina at 12:55, 8 July 2020

2020-07-08T12:55:04Z

← Older revision		Revision as of 12:55, 8 July 2020
Line 1:		Line 1:
	==Introduction==		==Introduction==
	When using the open Internet in order to process and receive customer related transactions between your workstation and the ~~CommitCRM~~ database, the need to upgrade the communication security may arise in order to safeguard your customer information from being read by any unrelated parties. Using Secure Socket Layer Encryption (SSL), you can lock your server from communicating with anybody that does not have an encryption certificate issued by you.		When using the open Internet in order to process and receive customer related transactions between your workstation and the RangerMSP database, the need to upgrade the communication security may arise in order to safeguard your customer information from being read by any unrelated parties. Using Secure Socket Layer Encryption (SSL), you can lock your server from communicating with anybody that does not have an encryption certificate issued by you.

	__TOC__		__TOC__
Line 6:		Line 6:
	<br>		<br>
	==Is SSL Enough?==		==Is SSL Enough?==
	In order to enhance security we usually suggest users to work over SSL - the ~~CommitCRM~~ Web Interface fully supports SSL Encryption which help protect from 3rd party eavesdropping on your communication. Furthermore, we suggest that when issuing passwords, you should issue complex passwords that would be difficult to read from a keyboard while someone is typing it.		In order to enhance security we usually suggest users to work over SSL - the RangerMSP Web Interface fully supports SSL Encryption which help protect from 3rd party eavesdropping on your communication. Furthermore, we suggest that when issuing passwords, you should issue complex passwords that would be difficult to read from a keyboard while someone is typing it.
	For more information see [[KB:_Creating_a_new_SSL_Certificate_for_the_Web_Interface\|Creating a new SSL Certificate for the Web Interface]].		For more information see [[KB:_Creating_a_new_SSL_Certificate_for_the_Web_Interface\|Creating a new SSL Certificate for the Web Interface]].

Line 19:		Line 19:
	==See Also==		==See Also==
	*[[KB:_Creating_a_new_SSL_Certificate_for_the_Web_Interface\|Creating a new Certificate for the Web Interface]]		*[[KB:_Creating_a_new_SSL_Certificate_for_the_Web_Interface\|Creating a new Certificate for the Web Interface]]
	*[[Web_Interface\|~~CommitCRM~~ Web Interface User Manual]]		*[[Web_Interface\|RangerMSP Web Interface User Manual]]

	[[Category:KB\|Security]]		[[Category:KB\|Security]]

Robert at 10:50, 1 September 2013

2013-09-01T10:50:37Z

← Older revision		Revision as of 10:50, 1 September 2013
Line 6:		Line 6:
	<br>		<br>
	==Is SSL Enough?==		==Is SSL Enough?==
	In order to enhance security we usually suggest users to work over SSL - the ~~Commit~~ Web Interface fully supports SSL Encryption which help protect from 3rd party eavesdropping on your communication. Furthermore, we suggest that when issuing passwords, you should issue complex passwords that would be difficult to read from a keyboard while someone is typing it.		In order to enhance security we usually suggest users to work over SSL - the CommitCRM Web Interface fully supports SSL Encryption which help protect from 3rd party eavesdropping on your communication. Furthermore, we suggest that when issuing passwords, you should issue complex passwords that would be difficult to read from a keyboard while someone is typing it.
	For more information see [[KB:_Creating_a_new_SSL_Certificate_for_the_Web_Interface\|Creating a new SSL Certificate for the Web Interface]].		For more information see [[KB:_Creating_a_new_SSL_Certificate_for_the_Web_Interface\|Creating a new SSL Certificate for the Web Interface]].

Line 19:		Line 19:
	==See Also==		==See Also==
	*[[KB:_Creating_a_new_SSL_Certificate_for_the_Web_Interface\|Creating a new Certificate for the Web Interface]]		*[[KB:_Creating_a_new_SSL_Certificate_for_the_Web_Interface\|Creating a new Certificate for the Web Interface]]
	*[[Web_Interface\|~~Commit~~ Web Interface User Manual]]		*[[Web_Interface\|CommitCRM Web Interface User Manual]]

	[[Category:KB\|Security]]		[[Category:KB\|Security]]

Reno: /* Additional Methods */

2010-01-18T20:39:47Z

Additional Methods

← Older revision		Revision as of 20:39, 18 January 2010
Line 12:		Line 12:

	==Additional Methods==		==Additional Methods==
	Limiting unneeded privileges is also a sound suggestion that could prevent long term damage to the system, in the event that employee credentials fall into unauthorized hands, so if somebody gains malicious access to the system, that person would have limited access, at best. It's also recommended to make sure your employees change their Web password often, and if a worker stops working in your company, make sure to disable their Web Users.		Limiting unneeded privileges is also a sound suggestion that could prevent long term damage to the system, in the event that employee credentials fall into unauthorized hands, so if somebody gains malicious access to the system, that person would have limited access, at best. It's also recommended to make sure your employees change their Web password often, and if a worker stops working in your company, make sure to disable their Web Users.<br>
	For more information, learn about managing your employee and customer ~~[[Main_Page#Privileges\|~~Privileges]].		For more information, [[Main_Page#Privileges\|learn about managing your employee and customer Privileges]].

	<br>		<br>

Reno: /* Additional Methods */

2010-01-18T20:39:02Z

Additional Methods

← Older revision		Revision as of 20:39, 18 January 2010
Line 13:		Line 13:
	==Additional Methods==		==Additional Methods==
	Limiting unneeded privileges is also a sound suggestion that could prevent long term damage to the system, in the event that employee credentials fall into unauthorized hands, so if somebody gains malicious access to the system, that person would have limited access, at best. It's also recommended to make sure your employees change their Web password often, and if a worker stops working in your company, make sure to disable their Web Users.		Limiting unneeded privileges is also a sound suggestion that could prevent long term damage to the system, in the event that employee credentials fall into unauthorized hands, so if somebody gains malicious access to the system, that person would have limited access, at best. It's also recommended to make sure your employees change their Web password often, and if a worker stops working in your company, make sure to disable their Web Users.
			For more information, learn about managing your employee and customer [[Main_Page#Privileges\|Privileges]].

	<br>		<br>

	==See Also==		==See Also==
	*[[KB:_Creating_a_new_SSL_Certificate_for_the_Web_Interface\|Creating a new Certificate for the Web Interface]]		*[[KB:_Creating_a_new_SSL_Certificate_for_the_Web_Interface\|Creating a new Certificate for the Web Interface]]

Reno: /* Is SSL Enough? */

2010-01-18T20:35:41Z

Is SSL Enough?

← Older revision		Revision as of 20:35, 18 January 2010
Line 7:		Line 7:
	==Is SSL Enough?==		==Is SSL Enough?==
	In order to enhance security we usually suggest users to work over SSL - the Commit Web Interface fully supports SSL Encryption which help protect from 3rd party eavesdropping on your communication. Furthermore, we suggest that when issuing passwords, you should issue complex passwords that would be difficult to read from a keyboard while someone is typing it.		In order to enhance security we usually suggest users to work over SSL - the Commit Web Interface fully supports SSL Encryption which help protect from 3rd party eavesdropping on your communication. Furthermore, we suggest that when issuing passwords, you should issue complex passwords that would be difficult to read from a keyboard while someone is typing it.
	For more information see [[KB:_Creating_a_new_SSL_Certificate_for_the_Web_Interface\|~~KB:~~ Creating a new SSL Certificate for the Web Interface]].		For more information see [[KB:_Creating_a_new_SSL_Certificate_for_the_Web_Interface\|Creating a new SSL Certificate for the Web Interface]].

	<br>		<br>

	==Additional Methods==		==Additional Methods==
	Limiting unneeded privileges is also a sound suggestion that could prevent long term damage to the system, in the event that employee credentials fall into unauthorized hands, so if somebody gains malicious access to the system, that person would have limited access, at best. It's also recommended to make sure your employees change their Web password often, and if a worker stops working in your company, make sure to disable their Web Users.		Limiting unneeded privileges is also a sound suggestion that could prevent long term damage to the system, in the event that employee credentials fall into unauthorized hands, so if somebody gains malicious access to the system, that person would have limited access, at best. It's also recommended to make sure your employees change their Web password often, and if a worker stops working in your company, make sure to disable their Web Users.

Reno: Created page with '==Introduction== When using the open Internet in order to process and receive customer related transactions between your workstation and the CommitCRM database, the need to upgra…'

2010-01-18T20:26:33Z

Created page with '==Introduction== When using the open Internet in order to process and receive customer related transactions between your workstation and the CommitCRM database, the need to upgra…'

New page

==Introduction==
When using the open Internet in order to process and receive customer related transactions between your workstation and the CommitCRM database, the need to upgrade the communication security may arise in order to safeguard your customer information from being read by any unrelated parties. Using Secure Socket Layer Encryption (SSL), you can lock your server from communicating with anybody that does not have an encryption certificate issued by you.

__TOC__

<br>
==Is SSL Enough?==
In order to enhance security we usually suggest users to work over SSL - the Commit Web Interface fully supports SSL Encryption which help protect from 3rd party eavesdropping on your communication. Furthermore, we suggest that when issuing passwords, you should issue complex passwords that would be difficult to read from a keyboard while someone is typing it.
For more information see [[KB:_Creating_a_new_SSL_Certificate_for_the_Web_Interface|KB: Creating a new SSL Certificate for the Web Interface]].

<br>
==Additional Methods==
Limiting unneeded privileges is also a sound suggestion that could prevent long term damage to the system, in the event that employee credentials fall into unauthorized hands, so if somebody gains malicious access to the system, that person would have limited access, at best. It's also recommended to make sure your employees change their Web password often, and if a worker stops working in your company, make sure to disable their Web Users.

<br>
==See Also==
*[[KB:_Creating_a_new_SSL_Certificate_for_the_Web_Interface|Creating a new Certificate for the Web Interface]]
*[[Web_Interface|Commit Web Interface User Manual]]

[[Category:KB|Security]]