Home > Articles > Software Development & Management

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

1.7 Cyber Warfare and the Open Electronic Society

What would happen to us if our computer systems suddenly stopped working for a few days? Nobody knows! Of course, given the redundancy and tolerence to failures in our computer systems, that is very unlikely to happen. Or is it? It is quite surprising what havoc a rather unimaginative virus attack can cause. And hackers seem to be able to invade corporate Web sites and government computers almost at will. The reality is that we do not know what is happening in our information systems minute by minute or day by day.

Cyber warfare involves the development of new ways to defend our IT layers against an increasing set of criminal and destructive activities. The battleground is the Internet and every corporate IT layer. These are some of the current problems:

  • Intrusions into computers. An intruder is someone who is not an authorized user and who anonymously gains privileged (or "root") access to a computer. The purposes for an intrusion vary widely and include the following examples:

    • Using a computer anonymously to set up a chat room for drug tra=cking

    • Accessing databases (supposedly secure) to steal information such as credit-card numbers

    • Using a network server to launch another kind of attack at some other site in the network

  • Denial-of-service attacks on Web sites and networks

  • Computer viruses, propagated from machine to machine by file transfers and e-mail messages

  • Spam, unsolicited e-mail, and other nuisance activities

Present security technologies such as encryption, firewalls, network-level intrusion detectors, and virus scanners defend against well-known, "textbook," criminal activities on the Web. When a new kind of attack is discovered, the IT security managers scramble to include it in their log file search scripts, and the security tools manufacturers try to add a defense against it to their products. But new tricks and techniques to exploit vulnerabilities in the defenses are being devised all the time. This kind of crude rearguard response we have at the moment—fix the defenses after we know what happened—is totally inadequate for dealing with the coming wave of electronic crime.

It is a total myth that it takes an expert or genius to break into a computer. Breaking and entering an operating system is something that's taught nowadays—it is a very good way to learn how operating systems and network protocols work. There are chat rooms on how to break in and scripted attacks that can be downloaded. The majority of those breaking into systems do not understand how their exploits work any better than a clerk understands how the operating system running his inventory program works.

When a new kind of intrusion is devised, it does take an understanding of the detailed workings of an operating system, or a network protocol, or an application program. From then on, that method of intrusion can be applied using scripts that carry out the steps of the method automatically.

Experts often publish new attacks on the Web to encourage manufacturers to plug the holes in their operating systems and application programs. But of course, the "crackers" and "kiddies" can read the expert's techniques too! And even when holes are plugged by the manufacturers, the patches are often not downloaded to many of the computers on the network. A vulnerable computer is usually the weak link into a subnet or a whole IT layer.

At present it is generally admitted by anyone in the know, including those who build or manage IT networks or advise on Internet policy, that our present abilities to defend our IT infrastructure against attacks, both old and new, are dismal. Let's list a few of the problems.

  1. We don't have powerful enough technology, even at the low level of network events, to detect nefarious activities in real time and cut them o'. And new ones are springing up all the time.

  2. At the network level, the current crop of detectors have absurdly high false alarm rates. We can't correlate the outputs from various network-level detection products to get a more accurate picture of whether or not an intrusion attempt is taking place. Correlation of the various detectors produced by the security industry would need a lot of planning and agreements. First, we need standards and conventions for the formats of detector outputs, so-called alerts. This first-step problem has been recognized by the Internet Engineering Task Force (IETF) and other organizations. We may have some standards for alerts and alarms soon. Then we need event processing technology beyond what is presently available from the security industry to do real-time correlation of alerts.

  3. Some kinds of attacks are di=cult, if not impossible, to detect at the network level. They would be easier to detect if we had application-level monitoring—but we don't. We don't have adequate monitoring to provide defensive tools with the kind of information they need. To do this, we need detectors that work at all levels of an IT system.

  4. New Internet applications and activities, such as global eCommerce, for example, present new opportunties for electronic theft and destruction. We need technologies that enable us defend at the highest levels in enterprise operations. Just imagine being able to mess with your competitor's electronic trading processes—insert a few false events supposedly coming from a partner at the "right" time, or intercept and divert process events between trading partners, or relay process events to competitors.

  5. We, as a society, have become far too dependent upon the Internet. Most of our essential services, from telecommunications and financial transactions to food distribution, now operate over the Internet and IT layers that are accessible from the Internet. In many cases there is no backup mode of operation, should the Internet be taken down. A denial-of-service attack on the Federal Reserve's Fedwire funds-transfer system could, if successful, bring the banking system to a standstill.

  6. Traditional security technology—firewalls, for example—and open eCommerce are in direct conflict.

The first four problems all indicate the need for event processing technology that applies across all levels of enterprise operations and applies uniformly to a wide range of the security industry's products. The fifth problem is a political and national policy problem, beyond the scope of this book.

But the sixth problem is one of the most perplexing problems with the Internet explosion—that is, the tension between traditional security based upon locking things up and denying access (firewalls, virtual private networks, and so on) and the need for open commerce. Industry analysts have written report after report on this problem, but the technology to allow openess, whereby anyone can communicate with anyone else and still have secure operations, just doesn't exist.

The sixth problem could become the great stalemate in developing visions like the global eCommerce vision. Unfortunately the "real" problem is not the sixth problem itself, but the lack of attention to it by the developers of grand visions. They are focused on making the vision happen. I have no doubt that the sixth problem can be solved. The question is whether a solution must be part of the infrastructure of the grand vision from the earliest designs, or whether it can be added piecemeal afterward when the cyber warfare really begins—rearguard actions all over again, but the stakes will be higher than ever.

There may be a lesson to be learned from the DARPAnet, the precursor of the Internet, which was built on open principles and little thought about misuse. The focus was on getting distributed communication networks to work. Could the DARPAnet have been designed di'erently, in hindsight, to make our present security problems easier to track, compartmentalize, and handle? Some experts feel that authentication should have been included in name servers from the very beginning, and that the messaging protocols should have been designed to always indicate the actual source of any message, no matter how many "hops" it makes in getting to its destination.

Following up on this early DARPAnet lesson, should the IT systems of the future be built with monitoring facilities and event feeds at every level from the network to the strategic level? And should they have backup duplication of essential monitoring and tracking facilities? This will be expensive, just like having security checkpoints at airports today. But it may become part of the cost of running the information society.

  • + 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