Home > Articles > Security > General Security and Privacy

📄 Contents

  1. Use the Right Access Controls on Network Servers
  2. Use the Right Access Controls On Public Web Servers
Like this article? We recommend

Use the Right Access Controls On Public Web Servers

Most Web server host operating systems provide the ability to specify access privileges individually for files, devices, and other data or code objects stored on that host. Any information that a Web server can access using these controls can potentially be distributed to all users accessing an organization's public Web site. Web server software is likely to provide additional object, device, and file access controls specific to its operation. Consider two perspectives about how best to configure these access controls to protect information stored on a public Web server:

  • How to limit the Web server software's access

  • How to apply access controls specific to the Web server when more detailed levels of access control are required

Why This Is Important

A public Web server typically stores information intended for widespread publication. It may also store information requiring restricted access, such as server log files, system software and configuration files, applications software and configuration files, and password files.

Using the access controls provided by both the server operating system and the Web server software can reduce the likelihood of inadvertent disclosure or corruption of information and violations of confidentiality and integrity. In addition, using access controls to limit resource use can reduce the impact of a denial-of-service attack against your public Web site, a violation of availability.

How to Do It

Establish New User and Group Identities

Establish new user and group identities to be used exclusively by the Web server software. Make these new user and new group identities independent and distinct from all other users and groups. This is a prerequisite for implementing the access controls described below.

Although the server may have to run as root (UNIX) or administrator (Windows) initially to bind to port 80, do not allow the server to continue to run in this mode.

Identify the Protection Needed

The general approach for identifying required access controls for files, devices, and objects specific to Web servers is outlined above.

In addition, determine if the Web server's operating system provides the ability to limit files accessed by the Web services' processes. These processes should have read-only access to those files necessary to perform the service, and should have no access to other files (such as server log files). If this feature is not available, skip some of the following steps and implement other security controls (described below) to limit exposure.

Use Web server host operating system access controls to enforce the following rules:

  • Public Web content files can be read but not written by Web service processes.

  • The directories in which public Web content is stored cannot be written by Web service processes.

  • Public Web content files can be written only by processes authorized for Web server administration.

  • Web server log files can be written by service processes, but log files cannot be read or serve as Web content. Web server log files can be read only by administration processes.

  • Any temporary files created by Web service processes (such as those that might be generated in the creation of dynamic Web pages) are restricted to a specified and appropriately protected subdirectory.

  • Access to any temporary files created by Web service processes are limited to the service processes that created these files.

Some of these controls are reiterated below when they can be achieved using alternate methods.

Mitigate the Effects of Denial-of-Service (DoS) Attacks

Resource-intensive DoS attacks against a Web server host operating system can involve several approaches, including the following:

  • Taking advantage of the number of simultaneous network connections by quickly establishing connections up to the maximum permitted so that no new legitimate users can gain access

  • Filling primary memory with unnecessary processes to slow down the system and limit Web service availability

  • Filling file systems with extraneous and incorrect information (some systems will not function if specific assets such as file systems are unavailable)

Logging information generated by the Web server host operating system may help to recognize such attacks.

Institute the following controls to limit the use of resources by the Web server host operating system and thus mitigate the effects of DoS attacks:

  • Network connection time-outs (time after which an inactive connection is dropped) should be set to a minimum acceptable time setting. Established connections will then time out as quickly as possible, opening up new connections to legitimate users. This procedure only mitigates the effects, however; it does not defeat the attack. If the maximum allowable open connections (or connections that are half-open—that is, if the first part of the TCP handshake was successful) are set to a low number, an attacker can easily consume the available connections with bogus requests. By setting the maximum to a much higher number, the impact of such attacks may be reduced, but additional resources will be consumed.

  • Secure Web servers often impose self-limiting constraints, and are configured to make most processes unavailable. Assigning priorities to Web service processes can help to ensure that high-priority processes obtain sufficient resources, even while under attack. Note, however, that doing so may create the potential for a denial-of-service on the lower-priority services.

  • It is unusual to be able to fill the available disk space of Web servers. Requests are typically processed quickly, and other "writes" should be disabled. Create separate directories for log files and other information from system directories and user information. Establishing effective boundaries between these information objects can be accomplished by specifying separate partitions and/or disk locations.

These controls will not fully protect your Web server against DoS attacks. However, by reducing the impact of these attacks, the Web server may be able to "survive" during the time period when the DoS attacks are occurring.

Protect Sensitive and Restricted Information

Configure the public Web server so that it cannot serve files outside the specified file directory tree for public Web content. This may be a configuration choice, either in the server software or in how the server process is controlled by the operating system. As much as possible, ensure that such files (outside of the specified directory tree) cannot be served, even if users know the names (URLs) of those files.

Avoid the use of links or aliases in your public Web content file directory tree that point to files elsewhere on the server host or the network file system. If possible, disable the Web server software's capability to follow links and aliases. As stated earlier, Web server log files and configuration files should reside outside of the specified file directory tree for public Web content.

In the event that the public Web server needs to access files that are sensitive or restricted, refer to the practice Configure the Web Server to Use Authentication and Encryption Technologies in the references noted at the beginning of this article.

Configure Web Server Software Access Controls

To configure Web server software access controls, perform the following steps:

  • Define a single directory, and establish related subdirectories exclusively for Web server content files, including graphics but excluding CGI (Common Gateway Interface) scripts and other programs.

  • Define a single directory exclusively for all external programs executed as part of Web server content.

  • Disable the execution of CGI scripts that are not exclusively under the control of administrative accounts. This is accomplished by creating and controlling access to a separate directory intended to contain authorized CGI scripts.

  • Disable the use of hard or symbolic links as ordinary files and directories.

  • Define a complete Web content access matrix. Identify which pages are restricted and which pages are accessible (and by what user groups).

Most Web server software vendors provide directives or commands that can restrict user access to public Web server content files. For example, the Apache Web server software provides a Limit directive that restricts which optional access features (such as New, Delete, Connect, Head, and Get) are associated with each Web content file. The Apache Require directive supports restricting available content to authenticated users or groups.

Many of the directives or commands can be overridden on a per-directory basis. The convenience of being able to make local exceptions to global policy is offset by the threat of a security hole being introduced in a distant subdirectory, which could be controlled by a hostile user. We recommend disabling a subdirectory's capability to override top-level security directives unless that override is required.

Disable the Serving of Web Server File Directory Listings

A common implementation of the Web protocol (HTTP) specifies that a URL ending in a slash character be treated as a request for a listing of the files in the directory with that name. As a general rule, prohibit the Web server from responding to such requests, even if all the files in the directory can be read by the general public.

Such requests may indicate an attempt to locate information by means other than that intended by the Web site. Users may try this if they are having difficulty navigating through the site, or if a link appears to be broken. Intruders may attempt this action to locate information hidden by the Web site's interface. We recommend investigating requests of this type found in Web server log files.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020