Security Basics mailing list archives
Re: Securing access to a web server best practices and suggestions
From: Rosslists <rosslists () krypsys com>
Date: Mon, 4 Jun 2012 23:28:19 +0200
Investigate F5 ASM if you already invested in BIG-IP? Ross Bushby CISSP Director Krypsys Mobile: 07771 994026 Phone: 0845 474 3031 Email: ross.bushby () krypsys com Web: www.krypsys.com Find out about Advanced Evasion Techniques at http://aet.stonesoft.com/krypsys This e-mail (and any attachments) may contain privileged and/or confidential information. If you are not the intended recipient, you must not use, copy, distribute or disclose the e-mail or any part of its contents or take any action in reliance on it. If you have received this e-mail in error, please contact the sender immediately, and delete it from your system. The information contained within is the sole responsibility of the author and any views or opinions do not necessarily represent those of the Company and its directors unless stated otherwise. On 2 Jun 2012, at 01:49, Luis Gutierrez <ip2work () gmail com> wrote:
I'd like to get some validation and best practice tips on the following scenario: We have some web applications that will be accessed via the Internet. We plan on using an F5 load balancer and LDAP calls to authenticate end users to the "fiction.corp domain". Users shall authenticate via their domain accounts. GPO is setup so that accounts lock out after 3 bad logon attempts. They unlock after 10 minutes. The F5 load balancer will be in the DMZ and the Firewall will only permit TCP/443 inbound from the Internet. Th eF5 will have access from the DMZ to an LDAP pool of three domain controllers (for authentication) that sit on our corporate LAN and port TCP/443 to a pool of web application servers also in the Corp LAN. The servers will be patched with the latest OS updates and the application as well. Any suggestions such as server hardening, patching, potential issues, are certainly welcome. Thank you in advance, luis ------------------------------------------------------------------------ Securing Apache Web Server with thawte Digital Certificate In this guide we examine the importance of Apache-SSL and who needs an SSL certificate. We look at how SSL works, how it benefits your company and how your customers can tell if a site is secure. You will find out how to test, purchase, install and use a thawte Digital Certificate on your Apache web server. Throughout, best practices for set-up are highlighted to help you ensure efficient ongoing management of your encryption keys and digital certificates. http://www.dinclinx.com/Redirect.aspx?36;4175;25;1371;0;5;946;e13b6be442f727d1 ------------------------------------------------------------------------
------------------------------------------------------------------------ Securing Apache Web Server with thawte Digital Certificate In this guide we examine the importance of Apache-SSL and who needs an SSL certificate. We look at how SSL works, how it benefits your company and how your customers can tell if a site is secure. You will find out how to test, purchase, install and use a thawte Digital Certificate on your Apache web server. Throughout, best practices for set-up are highlighted to help you ensure efficient ongoing management of your encryption keys and digital certificates. http://www.dinclinx.com/Redirect.aspx?36;4175;25;1371;0;5;946;e13b6be442f727d1 ------------------------------------------------------------------------
Current thread:
- Securing access to a web server best practices and suggestions Luis Gutierrez (Jun 04)
- RE: Securing access to a web server best practices and suggestions Dave Kleiman (Jun 04)
- Re: Securing access to a web server best practices and suggestions Rosslists (Jun 04)