Hyrax - Secure Installation Guidelines - Revision history

Ndp: /* Best Practices For Secure Installation */

2009-09-12T15:24:42Z

Best Practices For Secure Installation

← Older revision		Revision as of 15:24, 12 September 2009
Line 15:		Line 15:
	#* '''''Secure the logs, secure the configuration.'''''		#* '''''Secure the logs, secure the configuration.'''''
	# '''Run Hyrax as a Restricted user.''' - We strongly recommend that you run Hyrax as a restricted user. Running Hyrax as ''root'' or the ''super user'' is actively discouraged, as doing so creates the potential for dire consequences. What this means is that you should create a special user for bot the BES and Tomcat. These users should have restricted privileges and should only be allowed to write to the directories required by Tomcat and the BES.		# '''Run Hyrax as a Restricted user.''' - We strongly recommend that you run Hyrax as a restricted user. Running Hyrax as ''root'' or the ''super user'' is actively discouraged, as doing so creates the potential for dire consequences. What this means is that you should create a special user for bot the BES and Tomcat. These users should have restricted privileges and should only be allowed to write to the directories required by Tomcat and the BES.
			# '''Additional articles:'''
			#* Open Web Application Security Project (OWASP) article on how to secure Tomcat:
			#:: http://www.owasp.org/index.php/Securing_tomcat
			#* Tomcat 6 uses a different directory structure, has some logging changes, and has done away with the need for a deployment descriptor for a web app. There's an overview in this Covalent presentation:
			#::http://www.springsource.com/files/uploads/all/pdf_files/news_event/Intro_to_Tomcat6.pdf

	=Restricting System Access=		=Restricting System Access=

Ndp: /* Restricting System Access */

2009-01-11T19:25:12Z

Restricting System Access

← Older revision		Revision as of 19:25, 11 January 2009
Line 31:		Line 31:
	**[http://tomcat.apache.org/tomcat-6.0-doc/realm-howto.html Section 6: Configuring/Managing User Realms]		**[http://tomcat.apache.org/tomcat-6.0-doc/realm-howto.html Section 6: Configuring/Managing User Realms]
	**[http://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html Section 12: Configuring SSL]		**[http://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html Section 12: Configuring SSL]
	~~''(Note that Hyrax has not yet been tested against Tomcat 6.x)''~~

Ndp: /* Restricting System Access */

2007-11-07T10:27:41Z

Restricting System Access

← Older revision		Revision as of 10:27, 7 November 2007
Line 21:		Line 21:

	For Tomcat 5.x see:		For Tomcat 5.x see:
	* [[~~OLFS 1~~.~~2.0: Configuration#Security~~\| Our instructions for enabling Tomcat User Autentication]]		* [[Hyrax_-_OLFS_Configuration#Authentication_.26_Authorization \| Our instructions for enabling Tomcat User Autentication]]
	*[http://tomcat.apache.org/tomcat-5.5-doc/index.html Tomcat 5.x Documentation]		*[http://tomcat.apache.org/tomcat-5.5-doc/index.html Tomcat 5.x Documentation]
	**[http://tomcat.apache.org/tomcat-5.5-doc/realm-howto.html Section 6: Configuring/Managing User Realms]		**[http://tomcat.apache.org/tomcat-5.5-doc/realm-howto.html Section 6: Configuring/Managing User Realms]

Ndp: Hyrax: Secure Installation Guidelines moved to Hyrax - Secure Installation Guidelines

2007-11-07T06:30:01Z

Hyrax: Secure Installation Guidelines moved to Hyrax - Secure Installation Guidelines

← Older revision	Revision as of 06:30, 7 November 2007
(No difference)

Ndp: /* Best Practices For Secure Installation */

2007-10-05T03:04:14Z

Best Practices For Secure Installation

← Older revision		Revision as of 03:04, 5 October 2007
Line 14:		Line 14:
	#* ''Configuration Files'' - By default Hyrax comes with logging set up to record access and errors. This can be further reduced if one desires. However unrestricted access to the Hyrax configuration files could allow a hostile individual to turn on extensive logging in order to learn more about the system.		#* ''Configuration Files'' - By default Hyrax comes with logging set up to record access and errors. This can be further reduced if one desires. However unrestricted access to the Hyrax configuration files could allow a hostile individual to turn on extensive logging in order to learn more about the system.
	#* '''''Secure the logs, secure the configuration.'''''		#* '''''Secure the logs, secure the configuration.'''''
	# '''Run Hyrax as a Restricted user.''' - We strongly recommend that you run Hyrax as a restricted user. Running Hyrax as ''root'' or the ''super user'' is actively discouraged, as doing so creates the potential for dire ~~consequenes~~. What this means is that you should create a special user for bot the BES and Tomcat. These users should have restricted privileges and should only be allowed to write to the directories required by Tomcat and the BES.		# '''Run Hyrax as a Restricted user.''' - We strongly recommend that you run Hyrax as a restricted user. Running Hyrax as ''root'' or the ''super user'' is actively discouraged, as doing so creates the potential for dire consequences. What this means is that you should create a special user for bot the BES and Tomcat. These users should have restricted privileges and should only be allowed to write to the directories required by Tomcat and the BES.

	=Restricting System Access=		=Restricting System Access=

Ndp: /* Best Practices For Secure Installation */

2007-10-05T02:47:52Z

Best Practices For Secure Installation

← Older revision		Revision as of 02:47, 5 October 2007
Line 12:		Line 12:
	# '''Restrict Log and Configuration File Access''' - It is an unfortunate fact that many (if not most) IT security problems arise from within an organization and not from outside attacks. Given this situation it is important to restrict access to the log files generated, and the configuration files used, by Hyrax.		# '''Restrict Log and Configuration File Access''' - It is an unfortunate fact that many (if not most) IT security problems arise from within an organization and not from outside attacks. Given this situation it is important to restrict access to the log files generated, and the configuration files used, by Hyrax.
	#* ''Log Files'' - Logs can reveal how the code works and allow a hostile observer to interact with the server and view important details about the resulting effect.		#* ''Log Files'' - Logs can reveal how the code works and allow a hostile observer to interact with the server and view important details about the resulting effect.
	#* ''Configuration Files'' - By default Hyrax comes with logging set up to record access and errors. This can be further reduced if one desires. However unrestricted access to the Hyrax configuration files could allow a hostile individual to turn on extensive logging in order to learn more ~~baout~~ the system.		#* ''Configuration Files'' - By default Hyrax comes with logging set up to record access and errors. This can be further reduced if one desires. However unrestricted access to the Hyrax configuration files could allow a hostile individual to turn on extensive logging in order to learn more about the system.
	#* '''''Secure the logs, secure the configuration.'''''		#* '''''Secure the logs, secure the configuration.'''''
	# '''Run Hyrax as a Restricted user.''' - We strongly recommend that you run Hyrax as a restricted user. Running Hyrax as ''root'' or the ''super user'' is actively discouraged, as doing so creates the potential for dire consequenes. What this means is that you should create a special user for bot the BES and Tomcat. These users should have restricted privileges and should only be allowed to write to the directories required by Tomcat and the BES.		# '''Run Hyrax as a Restricted user.''' - We strongly recommend that you run Hyrax as a restricted user. Running Hyrax as ''root'' or the ''super user'' is actively discouraged, as doing so creates the potential for dire consequenes. What this means is that you should create a special user for bot the BES and Tomcat. These users should have restricted privileges and should only be allowed to write to the directories required by Tomcat and the BES.

Ndp: /* Best Practices For Secure Installation */

2007-10-05T02:38:56Z

Best Practices For Secure Installation

← Older revision		Revision as of 02:38, 5 October 2007
Line 9:		Line 9:

	# '''Always use a firewall''' - Keep your Hyrax server behind a firewall and configure the firewall to only forward requests to the appropriate port (typically 8080 for Tomcat and 80 for Apache) on your Hyrax system. Be sure to have the firewall block direct access to the BES.		# '''Always use a firewall''' - Keep your Hyrax server behind a firewall and configure the firewall to only forward requests to the appropriate port (typically 8080 for Tomcat and 80 for Apache) on your Hyrax system. Be sure to have the firewall block direct access to the BES.
	# '''~~Seperate~~ the BES and ~~Hyrax~~''' - We feel that it is better to run the BES on a second machine where '''only''' the BES port is open, and where the BES system is completely blocked by the firewall.		# '''Separate the BES and the OLFS''' - We feel that it is better to run the BES on a second machine where '''only''' the BES port is open, and where the BES system is completely blocked by the firewall.
	# '''Restrict Log and Configuration File Access''' - It is an unfortunate fact that many (if not most) IT security problems arise from within an organization and not from outside attacks. Given this situation it is important to restrict access to the log files generated, and the configuration files used, by Hyrax.		# '''Restrict Log and Configuration File Access''' - It is an unfortunate fact that many (if not most) IT security problems arise from within an organization and not from outside attacks. Given this situation it is important to restrict access to the log files generated, and the configuration files used, by Hyrax.
	#* ''Log Files'' - Logs can reveal how the code works and allow a hostile observer to interact with the server and view important details about the resulting effect.		#* ''Log Files'' - Logs can reveal how the code works and allow a hostile observer to interact with the server and view important details about the resulting effect.
Line 15:		Line 15:
	#* '''''Secure the logs, secure the configuration.'''''		#* '''''Secure the logs, secure the configuration.'''''
	# '''Run Hyrax as a Restricted user.''' - We strongly recommend that you run Hyrax as a restricted user. Running Hyrax as ''root'' or the ''super user'' is actively discouraged, as doing so creates the potential for dire consequenes. What this means is that you should create a special user for bot the BES and Tomcat. These users should have restricted privileges and should only be allowed to write to the directories required by Tomcat and the BES.		# '''Run Hyrax as a Restricted user.''' - We strongly recommend that you run Hyrax as a restricted user. Running Hyrax as ''root'' or the ''super user'' is actively discouraged, as doing so creates the potential for dire consequenes. What this means is that you should create a special user for bot the BES and Tomcat. These users should have restricted privileges and should only be allowed to write to the directories required by Tomcat and the BES.



	=Restricting System Access=		=Restricting System Access=

Ndp at 01:36, 21 September 2007

2007-09-21T01:36:10Z

← Older revision		Revision as of 01:36, 21 September 2007
Line 15:		Line 15:
	#* '''''Secure the logs, secure the configuration.'''''		#* '''''Secure the logs, secure the configuration.'''''
	# '''Run Hyrax as a Restricted user.''' - We strongly recommend that you run Hyrax as a restricted user. Running Hyrax as ''root'' or the ''super user'' is actively discouraged, as doing so creates the potential for dire consequenes. What this means is that you should create a special user for bot the BES and Tomcat. These users should have restricted privileges and should only be allowed to write to the directories required by Tomcat and the BES.		# '''Run Hyrax as a Restricted user.''' - We strongly recommend that you run Hyrax as a restricted user. Running Hyrax as ''root'' or the ''super user'' is actively discouraged, as doing so creates the potential for dire consequenes. What this means is that you should create a special user for bot the BES and Tomcat. These users should have restricted privileges and should only be allowed to write to the directories required by Tomcat and the BES.



	=Restricting System Access=		=Restricting System Access=

Ndp: /* Best Practices For Secure Installation */

2007-09-21T01:34:27Z

Best Practices For Secure Installation

← Older revision		Revision as of 01:34, 21 September 2007
Line 10:		Line 10:
	# '''Always use a firewall''' - Keep your Hyrax server behind a firewall and configure the firewall to only forward requests to the appropriate port (typically 8080 for Tomcat and 80 for Apache) on your Hyrax system. Be sure to have the firewall block direct access to the BES.		# '''Always use a firewall''' - Keep your Hyrax server behind a firewall and configure the firewall to only forward requests to the appropriate port (typically 8080 for Tomcat and 80 for Apache) on your Hyrax system. Be sure to have the firewall block direct access to the BES.
	# '''Seperate the BES and Hyrax''' - We feel that it is better to run the BES on a second machine where '''only''' the BES port is open, and where the BES system is completely blocked by the firewall.		# '''Seperate the BES and Hyrax''' - We feel that it is better to run the BES on a second machine where '''only''' the BES port is open, and where the BES system is completely blocked by the firewall.
	# '''Restrict Log and Configuration File Access''' - It is an unfortunate fact that many (if not most) IT security problems arise from within an organization and not from outside attacks. Given this situation it is important to restrict access to the log files generated by and configuration files used by Hyrax.		# '''Restrict Log and Configuration File Access''' - It is an unfortunate fact that many (if not most) IT security problems arise from within an organization and not from outside attacks. Given this situation it is important to restrict access to the log files generated, and the configuration files used, by Hyrax.
	#* ''Log Files'' - Logs can reveal how the code works and allow a hostile observer to interact with the server and view important details about the resulting effect.		#* ''Log Files'' - Logs can reveal how the code works and allow a hostile observer to interact with the server and view important details about the resulting effect.
	#* ''Configuration Files'' - By default Hyrax comes with logging set up to record access and errors. This can be further reduced if one desires. However unrestricted access to the Hyrax configuration files could allow a hostile individual to turn on extensive logging in order to learn more baout the system.		#* ''Configuration Files'' - By default Hyrax comes with logging set up to record access and errors. This can be further reduced if one desires. However unrestricted access to the Hyrax configuration files could allow a hostile individual to turn on extensive logging in order to learn more baout the system.
	#* '''''Secure the logs, secure the configuration.'''''		#* '''''Secure the logs, secure the configuration.'''''
	# '''Run Hyrax as a Restricted user.''' - We strongly recommend that you run Hyrax as a restricted user. Running Hyrax as ''root'' or the ''super user'' is actively discouraged, as doing so creates the potential for dire consequenes. What this means is that you should create a special user for bot the BES and Tomcat. These users should have restricted privileges and should only be allowed to write to the directories required by Tomcat and the BES.		# '''Run Hyrax as a Restricted user.''' - We strongly recommend that you run Hyrax as a restricted user. Running Hyrax as ''root'' or the ''super user'' is actively discouraged, as doing so creates the potential for dire consequenes. What this means is that you should create a special user for bot the BES and Tomcat. These users should have restricted privileges and should only be allowed to write to the directories required by Tomcat and the BES.



	=Restricting System Access=		=Restricting System Access=

Ndp at 01:32, 21 September 2007

2007-09-21T01:32:16Z

@@ Line 1: / Line 1: @@
-# Always use a firewall; for Hyrax, never allow direct access to the BES
+=Overview=
-# Better to run the BES on a second machine where only the BES port is open
+Security is an important and unfortunately complex issue. Any computer security expert will tell you that the best way to keep your systems secure is to never, ever, let them have network access. Obviously that's not really what you had in mind or you wouldn't be thinking about installing Hyrax. You can improve the security of Hyrax using a number of mechanisms, from following best practices for installation, to requiring secure authentication for the entire server.
-# Log issues: How to manage the log files
-# Run the BES and Tomcat as less privileged users
+'''Disclaimer:''' At OPeNDAP we consider security to be a top priority. However, we are not security experts. What follows is a summary of what we currently know to be the most effective methods for securing your Hyrax installation.