Bobcares

Ways of improving security in Litespeed

by | Jul 21, 2012

LiteSpeed Web Server is the leading high-performance, high-scalability web server . It is completely Apache interchangeable, so it can quickly replace in your existing web delivery platform. The important security features and its configurations are given below:

a) SSL (Litespeed administration security)

We need to secure the administration area. We will do this by adding a SSL connection to the administration port and configuring the server to accept connections to that port from our IP only (or from a group of IPs).

b) DDoS Protection

LiteSpeed web server is much less vulnerable to HTTP Denial Of Service(DoS) and Distributed Denial of Service (DDoS) attacks, thanks to the IP level throttling, connection accounting and its outstanding performance and scalability.


This is a server level setting that affects all virtual hosts. Virtual host setting will not override the server setting. If you want to block a certain IP or network, put * or ALL in “Allowed List” and list the blocked IP or network in Denied List. If you want to only allow certain IP or sub-network, put * or ALL in Denied List and list the allowed IP or sub-network in Allowed List. The setting of the smallest scope that fits for an IP will be used to determine whether to block or allow. Trusted IP or sub-network must be specified in the Allowed List by adding a trailing “T”. Trusted IP or sub-network is not affected by connection/throttling limits. Only server level access control can set up trusted IP/sub-network.

c) SuEXEC


This is another way of security. In this we have to enable SuEXEC in LiteSpeed server with applications including CGI, FastCGI, LSAPI, PHP, Python, RubyOnRails.

d) File system protection

LiteSpeed web server will serve a static file only if the following conditions are satisfied:

# “.ht*” and “.svn*” are not allowed in a decoded URL, this will deny accessing some important hidden files and directories.
# The file permission must configured with the required permissions.
# The file will not be in the Access Denied Directory list
# It does not contain symbolic links, if symbolic linking is not allowed.

e) Chroot Jail
“chroot” can change the root directory for a process. A changed root process and its children process cannot access any file beyond the new root directory. It is like putting a process in a jail, so this mechanism is called “chroot jail”. The litespeed webserver run inside the chroot jail.

The above is a very rough outline of the Litespeed web server, and if you have any questions, we would be happy to talk to you! 🙂


About the Author :

Manu George E works as a Software Engineer in Bobcares. He joined Bobcares back in March 2011. He loves reading books, watching movies and listening to music in his free time.




0 Comments

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF