Home > Articles > Security > Network Security

  • Print
  • + Share This
This chapter is from the book

Operational Strategy

At this point, we have addressed some basic factors in identifying the focus and scope of the team. The next major section of the puzzle to consider is the team's operational strategy. Specifically, will the team be strictly reactive or both proactive and reactive in nature? If it is reactive only, the team would strictly respond to computer incidents as they are detected or reported from the constituency. Tools such as intrusion detection systems (IDSs) may be used to monitor for and detect unauthorized activity as it happens. (Some IDSs can also be configured to help stop an attack in progress.)

It is very difficult, and sometimes ineffective, for a team to remain completely reactive. For example, if an incident affects a number of systems, it may be a prudent measure to proactively examine other systems that do not appear to have been affected. This activity ensures that no damage was inflicted and confirms that proper safeguards are in place to prevent the systems from being affected in the future. Although prevention programs are difficult to justify because it is nearly impossible to quantify the number of incidents prevented, it stands to reason that an incident that is prevented consumes fewer resources than one that must be investigated.2

If the team is to be both proactive and reactive in nature, then services such as risk assessments, vulnerability analysis, and training may be included in the capabilities offered by the team. The number of tasks assigned to the team will have a direct impact on the number of personnel and tools required for the team to be completely operational. Keep in mind that some of these services may be outsourced or scaled appropriately for the organization, depending on the projected return on the investment for the services that are offered. More detail on the types of services that the team may consider offering is provided later in this chapter.

Defining an Incident

Regardless of the strategy taken, the type of activity that is considered to be an incident should be clearly decided up front. It is strongly recommended that a clear, concise definition be developed for the “incidents” a team will address. Generic or vague definitions such as “unauthorized activity” leave too much room for interpretation and may negatively affect operations. For example, the number of personnel assigned to the team may prove insufficient for the volume of “unauthorized activity” reported and problems may be encountered in trying to enter and track the incident data in a database or trouble ticket system.

This question leads into a discussion on the very important topic of terminology. As this topic can be quite expansive, a separate chapter has been dedicated to this one piece of the puzzle. Refer to Chapter 3 for this discussion.

Tracking an Incident

Although this is still very early in the book, you should consider your incident tracking strategy to be a part of the foundation of the incident response team. The ability to track incidents is important for several reasons:

  • Management Reporting. The incident tracking system may be used as a tool to justify and report on the performance of the investment that has been made in the team and security tools. Reporting the type and severity of incidents encountered also helps upper management to gain a clear picture of the threats being realized in their environment. This information can then be used to focus efforts on specific areas, such as user awareness, antivirus software, and increased levels of defense, so as to improve the overall security posture of the organization.

  • Incident Triage. A mechanism for grouping incidents can lead to streamlining incident investigation activities, setting priorities for incidents, and correlating incident data.

  • Customer Service. The incident response team's reputation among its constituency is critical to its success. A team that permits incidents to “fall through the cracks” will lose favor with its constituency, and eventually management support. Management will naturally expect the team to handle incident information and evidence in a responsible, prudent manner. In addition to incident accountability, a team must have a well-planned method of keeping the affected constituency abreast of the status of the incident.

A dedicated database for tracking incidents, correlating activity data, and reporting statistics to upper management can be the most valuable tool that an incident response organization has at its disposal. Tracking processes and mechanisms must be established to follow the incident from the time it is reported to the time it is considered closed. Otherwise, if the team is very busy (as most are in today's environment), the chance for an incident to “fall through the cracks” is too great. Two or more tools may actually be required for this function, such as a triage tool that feeds data into a central database. The triage tool may be used for tracking open tickets, while the database is used for reviewing specific details about the activity.

Once the team is operational, the sources for reporting a computer incident to the team will typically have multiple origins. A team may accept incident reports via the telephone, e-mail, IDS, paging systems, law enforcement, or other sources. Not all information that is reported to a team as an “incident” will, in fact, turn out to be a real incident, just as a call to the emergency 911 telephone system may not be an emergency. (Note: 911 is the code used within the United States for emergency calls to police, fire, and medical officials. Other codes are used in different countries, such as 0, 411, and 119.)

As activity is reported from various sites or systems, mechanisms for correlating various aspects of it need to be available. For example, how often does a specific IP address show up? Have any other attacks on a specific target been reported? How many scans of a particular port number have been detected?

Finally, statistics can be a wonderful tool for any team. A database can help to quickly identify useful data, such as the number of reports received, number of open incidents, number of false reports processed, number of times that a particular Internet service provider's (ISP) addresses have attacked systems in the team's constituency, and much more. These statistics can, in turn, help to identify specific threats to the systems that the team is trying to protect as well as justify the need for the team or additional resources moving forward. (Granted, statistics can be manipulated in many ways, but it is very difficult to dispute facts that are very well defined with a good deal of granularity.)

Counting Incidents

A similar issue that must be addressed is how incidents will be counted. It is not uncommon for an attacker to gain unauthorized access to multiple sites within the same time frame or deny services to more than one system at once. A good example was the distributed denial-of-service attacks launched in February 2000. Over the course of three days, computer systems at Yahoo!, buy.com, eBay, CNN.com, amazon.com, ZDNet.com, E*Trade, Datek online, and Excite were all affected by the attack.3 Depending on the accounting procedures implemented by an incident response team, these attacks could have been combined into one incident or tracked separately as nine incidents with similar patterns.

Combining the activity that appears to be attributable to the same person or group of persons can help with the correlation of the activity. Conversely, by grouping the activity together, important statistics may be lost. Most teams will combine the activity that appears to come from the same source. In that case, it is recommended that the database or means of tracking statistics have enough granularity built in to depict the number of targets affected by the attack.

  • + Share This
  • 🔖 Save To Your Account

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