Home > Articles

This chapter is from the book

This chapter is from the book

Security Administration—The Importance of a Security Policy

  • Describe, recognize, or select good administrative maintenance and change-control issues and tools.

A comprehensive security policy shouldn't be limited only to your computer network. A good security policy encompasses a range of activities across your entire organization, including workstation configuration, logon procedures, and building access procedures.

WARNING

Educate Users One of the biggest stumbling blocks to implementing your security policy is the users and their knowledge of security issues (or lack thereof). Many users consider security issues trivial or an unnecessary nuisance. Make sure you provide a reason for implementing each policy instead of simply requiring that users blindly follow them. Awareness training should be part of every formal security plan. It should be mandatory for new employees and repeated at regular intervals to cover new threats that emerge.

Understanding Security Policies

In its simplest form, a security policy is a single document (or more commonly, a set of related documents) that describes the security controls that govern an organization's systems, behavior, and activities. At the highest level, security policies do not specify technologies or particular solutions. Instead, they seek to define a specific set of conditions to help protect a company's assets and its ability to conduct business.

In fact, any good security policy must address the following concerns:

  • Prevent waste or inappropriate use of organization resources (especially computing resources).

  • Limit or eliminate potential legal liability, be it from employees or third parties.

  • Preserve and protect valuable, confidential, or proprietary information from unauthorized access or disclosure.

Any well-crafted security policy is enshrined in written form, and provides a way to instruct employees about what kinds of behavior or resource usage are required and acceptable, and what is forbidden and unacceptable. A security policy defines marching orders for IT staff and security professionals to help them enact access controls, authentication methods, and accounting techniques. A good security policy also provides information for rank and file employees as to how to help protect their employer's assets and information, and provides guidelines as to acceptable (and unacceptable) practices and behavior.

Building Security Policies

Like most significant development efforts, building a security policy involves more than an afternoon's work. In fact, this effort is best described using a formal life-cycle model. That is, most security policies cycle through three phases of activity, more or less continuously:

  • Development. At some point, a security policy must be created for the first time, or changed so significantly from a previous incarnation that it might as well be a first effort. The activity that drives the formulation of a security policy is called risk assessment, where the fundamental goal behind a security policy is to identify potential sources of risk, and then determine ways to eliminate, reduce, or transfer such risks. Because a broad audience—including executives, IT staff, and end users—must be able to read and understand a security policy, it's important to make it as simple and readable as possible.

  • Enactment and enforcement. After a security policy has been defined, it must be deployed. This requires not only enacting its provisions and requirements, but also communicating clearly that it is desirable for all employees to heed its provisions. Although this may seem harsh, it's also often necessary to state—and when necessary, to impose—consequences for those who either fail to heed or knowingly violate the terms and requirements of the policy. This explains why many employers clearly state such consequences in employee handbooks, employment agreements, and other documentation that employees must read and heed on the job.

  • Monitoring and maintenance. As in most life-cycle models, this phase is the most active of the three. In other words, IT and security professionals must make sure that security policies are monitored and updated to remain relevant to today's activities and concerns—and ultimately, to manage today's and anticipate and forestall tomorrow's potential risks.

Creating a security policy is the result of completing a set of interlocking activities. Risk assessment comes first and foremost, wherein key business resources, assets, activities, and capabilities are identified, and ways to manage potential exposure to loss or harm are considered.

Next, it's necessary to identify various roles in an organization, in which each role requires its own certain kinds of access to an organization's resources and assets. Thus, you might choose to identify executives, IT staff, salespeople, marketing staff, development staff, and technical support staff as roles sufficiently unique such that each warrants creating its own individual security profile. Of course, a consequence of this activity is that you must analyze each such group's security profile, determine which resources they may access, and what kinds of operations on those resources they will be allowed to perform.

The following list represents a basic, recommended set of steps to follow and build on to create a security policy. Keep in mind that this list is by no means complete or exhaustive. Much of the information gathered in these steps is based on security fundamentals that you learn in the following chapters of this book and during your security research for your own organization's network.

Step by step

3.1 Designing a Security Policy

  1. Determine whether your company already has security policies in any form. If it has security policies in place, review them and make changes as necessary to update them to meet current needs and to reflect any new principles or additional security measures that you have developed. This is an ongoing process that must be updated as the security in your organization changes. If you don't already have them in place, now is the time to convince upper management of their importance (the importance of the policies, that is—upper management is certainly aware of their own importance!). You need their support to successfully implement a policy. After you've won them over, put together a multidisciplinary team composed of representatives from all departments in the organization to help you compose the policy. It's much more likely that the policy will be practical and effective if the users assist in developing it.

  2. Determine the scope of the policy. Will it pertain to the entire corporation, a specific division or department, or just relate to a specific activity or system?

  3. Outline user guidelines that may dictate a particular direction in the security policy—for example, email-usage restrictions. If your company has a network-usage policy in place that limits access to certain information on the servers or does not permit sending personal email, it may affect how you design and implement your security policies. For example, you may want to install and configure a firewall to prevent users from accessing certain Web sites that users are not allowed to view. If your company does not have a network-usage policy, consider working with users and management to determine what defines appropriate use of network resources.

  4. Assess current minimum requirements for security based on installed servers, services, operating system software, and other equipment. This varies from site to site, but using everything that you gathered in the first three steps and based on the long-term security goal of the company, you can usually determine the minimum acceptable level of security. This can entail something as simple as ensuring that users change their passwords every 30 days and installing antivirus software on every workstation and server.

Using the information gathered in Steps 1–4, you can more readily create a security policy. You must ensure that such a document contains enough information to be useful, but not so much information that the intended audience has a hard time understanding it. The policy should be a high-level document that doesn't contain so much detail that it requires constant updating. This general policy must include items, such as:

  • Password policies

  • What to do in case of an intrusion

  • What operating system and software updates must be installed, and how often

TIP

Exam Tip: Password Policies Password policies are an extremely important component of any strong security policy. For this reason, your TICSA exam may contain several questions on this topic. Review the "Password Policies" section of Chapter 8 before taking the exam.

In addition, you must define consequences for users who do not follow the policy. In short, anything that must be put into words and followed by an organization's users, IT staff, and management must be recorded here. Even something as minor as specifying that users must shut down their systems before leaving at the end of the day should be considered and, if called for, included in the policy.

Recruit Users and Management to Review the Security Policy

After the policy is created, ask other members of the IT staff and, if possible, other management personnel to assess that policy for accuracy and completeness. You must continue this review process throughout the life of the policy to keep it up to date.

You should also select a group of users (with a wide range of skills and experiences) to test its implementation. You'll be able to detect most bugs or growing pains before rolling it out to the entire organization.

Within that selected group, educate them about the "hows and whys" of the security policy, and implement it as necessary. Allow these users to try out these policies and provide feedback. You should record their comments as well as comments from the IT staff who support them during this test phase.

After you complete the testing phase, use any pertinent information from your testers and the IT staff to make whatever changes are necessary to clarify, simplify, or streamline that policy. You can then ask the same group or a different group of users to test the policy again. Only when you are confident that your policy will work for your entire user population, should you educate the entire user base and implement the finalized policy. Quite often, you're better off implementing that policy one group at a time to avoid a high volume of support calls from users who have issues with new security policies.

TIP

Exam Tip: System Administration, Networking, and Security (SANS) Be sure to investigate the previously mentioned items found on the System Administration and Network Security (SANS) Institute's Security Policy Process Web pages. This site serves as a great reference for security policies and contains detailed examples of important security policies. You may want to visit this site and view one or more of the examples to gain a thorough understanding of this topic before tackling the TICSA exam.

Keep up with the changes to your organization, configuration, and user needs to ensure that your security policy is current and effective. Most experts recommend that such policies be reviewed as part of routine monthly maintenance activities; in smaller organizations, quarterly reviews may be adequate.

Security Policy Examples

As mentioned earlier in this chapter, a security policy is quite likely to be implemented as a collection of documents, rather than as a single monolithic document. Here, we provide a list of typical documents that will together comprise an organization's security policy, along with pointers to numerous sample security policy templates (blanks that are ready for you to fill out) and examples (actual or sanitized security policy documents) online.

TIP

Exam Tip: Security Policies The TICSA exam consists of multiple-choice questions, so it won't ask you to write a security policy, but you should be familiar with the various items that should be covered by such a policy. Review the following list before taking the exam.

A typical collection of security policy documents is likely to include some or all of the items found on the SANS Institute Web Site (http://www.sans.org/newlook/resources/policies/policies.htm#template), depending on an organization's size, infrastructure, and needs.

Pearson IT Certification Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from Pearson IT Certification 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 Pearson IT Certification 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 Adobe Press. 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.pearsonitcertification.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