Network Management

1
Network Management

• Security Disaster Recovery

2
Objectives

• Introduction
• Why networks need security
• Types of Security Threats
• Network Controls
• Risk Assessment
• Develop a Control Spreadsheet
• Identify and Document the Controls
• Evaluate the Networks Security
• Controlling Disruption, Destruction and Disaster
• Preventing Disruption, Destruction and Disaster
• Detecting Disruption, Destruction and Disaster
• Correcting Disruption, Destruction and Disaster
• Controlling Unauthorized Access
• Preventing Unauthorized Access
• Detecting Unauthorized Access
• Correcting Unauthorized Access

3
Introduction

• Security is a major networking concern. 90 of
  the respondents to the 2000 Computer Security
  Institute/FBI Computer Crime and Security Survey
  reported security breaches in the last 12 months.
  
• Information Week estimates the annual cost of
  security losses worldwide at 1.6 trillion.
• It means more than preventing a hacker from
  breaking into your computer, it also includes
  being able to recover from temporary service
  problems, or from natural disasters (next slide).

4
Threats to Network Security
5
Types of Security Threats

• Disruptions are the loss or reduction in network
  service.
• Some disruptions may also be caused by or result
  in the destruction of data.
• Natural (or manmade) disasters may occur that
  destroy host computers or large sections of the
  network.
• Unauthorized access is often viewed as hackers
  gaining access to organizational data files and
  resources. However, most unauthorized access
  incidents involve employees.
• Security incidents are increasing at 100 per
  year! (CERT)

6
Network Controls

• Developing a secure network means developing
  mechanisms that reduce or eliminate the threats
  to network security, called controls.
• There are three types of controls
• Preventative controls - mitigate or stop a person
  from acting or an event from occurring (e.g.
  passwords).
• Detective controls - reveal or discover unwanted
  events (e.g., auditing software).
• Corrective controls - rectify an unwanted event
  or a trespass (e.g., reinitiating a network
  circuit).

7
Network Controls

• It is not enough to just establish a series of
  controls personnel need to be designated as
  responsible for network control and security.
• This includes developing controls, ensuring that
  they are operating effectively, and updating or
  replacing controls.
• Controls must also be periodically reviewed to
• ensure that the control is still present
  (verification)
• determine if the control is working as specified
  (testing)

8
Risk Assessment

• Risk assessment is the process of making a
  network more secure, by comparing each security
  threat with the control designed to reduce it.
• One way to do this is by developing a control
  spreadsheet (next slide).
• Network assets are listed down the side.
• Threats are listed across the top of the
  spreadsheet.
• The cells of the spreadsheet list the controls
  that are currently in use to address each threat.

9
 
Threats
  Sample control spreadsheet with some assets and
threats
10
Network Assets

• Network assets are the network components
  including hardware, software and data files.
• The value of an asset is not simply its
  replacement cost, it also includes personnel time
  to replace the asset along with lost revenue due
  to the absence of the asset.
• For example, lost sales because a web server is
  down.
• Mission critical applications are also important
  assets. These are programs on an information
  system critical to business operations.

11
 
 Types of Assets
12
Security Threats

• A network security threat is any potentially
  adverse occurrence that can harm or interrupt the
  systems using the network, or cause a monetary
  loss to an organization.
• Once the threats are identified they are then
  ranked according to their occurrence.

13
Common Security Threats
14
Identifying and Documenting Controls

• Once the specific network threats and controls
  have been identified, you can begin working on
  the network controls.
• Each network component should be considered along
  with the specific threats to it.
• Controls to address those threats are then listed
  in terms of how each control will prevent, detect
  and/or correct that threat.

15
 
Threats
Sample control spreadsheet listing assets,
threats, and controls
16
Sample control spreadsheet list of controls  

• Controls
• 1. Disaster Recovery Plan
• 2. Halon fire system in server room. Sprinklers
  in rest of building
• 3. Not on or below ground level
• 4. Uninterruptible Power Supply (UPS) on all
  major network servers
• 5. Contract guarantees from inter-exchange
  carriers
• 6. Extra backbone fiber cable laid in different
  conduits
• 7. Virus checking software present on the network
• 8. Extensive user training on viruses and
  reminders in monthly newsletter
• 9. Strong password software
• 10. Extensive user training on password security
  and reminders in monthly newsletter
• 11. Application Layer firewall

17
Evaluate the Networks Security

• The last step in designing a control spreadsheet
  is evaluating the adequacy of the controls and
  the degree of risk associated with each threat.
• Based on this, priorities can be decided on for
  dealing with threats to network security.
• The assessment can be done by the network
  manager, but it is better done by a team of
  experts chosen for their in-depth knowledge about
  the network and environment being reviewed.

18
Preventing Disruption, Destruction and Disaster

• Preventing disruptions, destructions and
  disasters mean addressing a variety of threats
  including
• Creating network redundancy
• Preventing natural disasters
• Preventing theft
• Preventing computer virus attacks
• Preventing denial-of-service attacks

19
Network Redundancy

• The key to in preventing or reducing disruption,
  destruction and disaster - is redundancy.
• Examples of components that provide redundancy
  include
• Uninterruptible power supplies (UPS)
• Fault-tolerant servers
• Disk mirroring
• Disk duplexing
• Redundancy can be built into other network
  components as well.

20
Preventing Natural Disasters

• Disasters are different from disruptions since
  the entire site can be destroyed.
• The best solution is to have a completely
  redundant network that duplicates every network
  component, but in a different location.
• Generally speaking, preventing disasters is
  difficult. The most fundamental principle is to
  decentralize the network resources.
• Other steps depend on the type of disaster to be
  prevented.

21
Preventing Theft

• Equipment theft can also be a problem if
  precautions against it are not taken.
• Industry sources indicate that about 1 billion
  is lost each year to theft of computers and
  related equipment.
• For this reason, security plans should include an
  evaluation of ways to prevent equipment theft.

22
Preventing Computer Viruses

• Special attention must be paid to preventing
  viruses that attach themselves to other programs
  and spread when the programs are executed.
• Macroviruses attach themselves to documents and
  become active when the files are opened are also
  common. Anti-virus software packages are
  available to check disks and files to ensure that
  they are virus-free.
• Incoming e-mail messages are the most common
  source of viruses. Attachments to incoming e-mail
  should be routinely checked for viruses.
• The use of filtering programs that clean
  incoming e-mail is also becoming common.

23
Detecting Disruption, Destruction Disaster

• One function of network monitoring software is to
  alert network managers to problems so that these
  can be corrected.
• Detecting minor disruptions can be more
  difficult.
• The network should also routinely log fault
  information to enable network managers to
  recognize minor service problems.
• In addition, there should be a clear procedure by
  which network users can report problems.

24
Disaster Recovery Plans (DRP)

• The goal of the disaster recovery plan (DRP) is
  to plan responses to possible disasters,
  providing for partial or complete recovery of all
  data, application software, network components,
  and physical facilities.
• Critical to the DRP are backup and recovery
  controls that enable an organization to recover
  its data and restart its application software
  should some part of the network fail.
• The DRP should also address what to do in a
  variety of situations, such as, if the main
  database is destroyed or if the data center is
  destroyed.

25
Elements of a Disaster Recovery Plan

• Names of responsible individuals
• Staff assignments and responsibilities
• List of priorities of fix-firsts
• Location of alternative facilities.
• Recovery procedures for data communications
  facilities, servers and application systems.
• Actions to be taken under various contingencies.
• Manual processes.
• Updating and Testing procedures.
• Safe storage of data, software and the disaster
  recovery plan itself.

26
Two-Level Disaster Recovery Plans

• Most large organizations have a two-level
  disaster recovery plan.
• Level 1 When they build networks they build
  enough capacity and have enough spare equipment
  to recover from a minor disaster, such as loss of
  a major server or portion of the network.
• Level 2 most large organizations rely on
  professional disaster recovery firms to provide
  second level support for major disasters.

27
Disaster Recovery Firms

• Many large organizations outsource their disaster
  recovery efforts to disaster recovery firms.
• Disaster recovery firms offer a range of services
  from secure storage for backups, to a complete
  networked data center that clients can use should
  their network be destroyed by some disaster.
• Full services are not cheap, but may be
  worthwhile when millions of dollars of lost
  revenue may be at stake.

28
Preventing Intruder Access

• Four types of intruders attempt to gain
  unauthorized access to computer networks.
• 1. Casual hackers who only have limited
  knowledge of computer security.
• 2. Security experts whose motivation is the
  thrill of the hunt.
• 3. Professional hackers who break into corporate
  or government computers for specific purposes.
• 4. Organization employees who have legitimate
  access to the network but who gain access to
  information they are not authorized to use.

29
Preventing Unauthorized Access

• A proactive approach that includes routinely
  testing your security systems is key to
  preventing unauthorized access.
• Access related security issues include
• Security policies
• User profiles
• Physical security
• Dial-in security
• Firewalls
• Network address translation
• Encryption

30
Elements of a Security Policy

• Names of responsible individuals.
• Incident reporting system and response team.
• Risk assessment with priorities.
• Controls on access points to prevent or deter
  unauthorized external access.
• Controls within the network to ensure internal
  users cannot exceed their authorized access.
• An acceptable use policy.
• User training plan on security.
• Testing and updating plans.

31
User Profiles and Forms of Access

• The limits of what users have access to on a
  network are determined by user profiles assigned
  to each user account by the net manager.
• The profile specifies access details such as what
  data and network resources a user can access and
  the type of access (e.g., read, write, create,
  delete).
• Most access is still password based, that is,
  users gain access based on something they know.
• Many systems require users to enter a password in
  conjunction with something they have, such as a
  smart card. ATM cards work in this way.
• In high-security applications, users may be
  required to present something they are, such as a
  finger, hand or the retina of their eye for
  scanning by a biometric system.

32
User Profiles Managing User Access

• User profiles can limit the allowable log-in
  days, time of day, physical locations, and the
  allowable number of incorrect log-in attempts.
• Creating accounts and profiles is simple, as they
  are created when new personnel arrive.
• One security problem is often created because
  network managers forget to remove user accounts
  when someone leaves an organization.

33
Managing Users

• It is important to screen and classify both users
  and data (need to know).
• The effect of any security software packages that
  restrict or control access to files, records, or
  data items should also be reviewed.
• Adequate user training on network security should
  be provided through self-teaching manuals,
  newsletters, policy statements, and short
  courses.
• A well publicized security campaign can also help
  deter potential intruders.

34
Physical Security

• Physical security means implementing access
  controls so only authorized personnel have access
  to areas where network equipment is located.
• Each network component should have its own level
  of physical security.
• Two important areas of concern are network
  cabling and network devices.
• Network cables should be secured behind walls.
• Network devices such as hubs and switches should
  be secured in locked wiring closets.

35
Dial-In Security

• Any organization that permits staff members to
  access its networks via dial-in modems opens
  itself to a broader range of intruders.
• One strategy is to routinely change modem
  numbers.
• Another strategy is to use call-back modems
  automatic number identification (ANI) so only
  users dialing in from authorized locations are
  granted access.
• One-time passwords provide a strategy for
  traveling employees who cant use call-back
  modems and automatic number identification.

36
Firewalls

• Firewalls are used to prevent intruders on the
  Internet from making unauthorized access and
  denial of service attacks to your network.
• A firewall is a router, gateway, or special
  purpose computer that examines packets flowing
  into and out of the organizations network
  (usually via the Internet or corporate Intranet),
  restricting access to that network.
• The two main types of firewalls are packet level
  firewalls and application-level firewalls.

37
Packet Filters

• A packet-level firewall (or packet filter)
  examines the source and destination address of
  packets that pass through it, only allowing
  packets that have acceptable addresses to pass.
• Since each packet is examined separately, the
  firewall cant understand what the senders goal
  is.
• Packet filters may be vulnerable to IP spoofing,
  accomplished by changing the source address on
  incoming packets from their real address to an
  address inside the organizations network.
• While packet filters have strengthened their
  security since the first cases of IP spoofing, IP
  spoofing remains a problem.

38
Application-Level Firewalls

• An application-level firewall or application
  gateway acts as an intermediate host computer,
  separating a private network from the rest of the
  Internet, but it works on specific applications,
  such as Web site access.
• The application gateway acts as an intermediary
  between the outside client making the request and
  the destination server responding to that
  request, hiding individual computers on the
  network behind the firewall.
• Because of the increased complexity of what they
  do, application level firewalls require more
  processing power than packet filters which can
  impact network performance.

39
Network Address Translation

• Network address translation (NAT) is used to
  shield a private network from outside
  interference.
• An NAT proxy server uses an address table,
  translating network addresses inside the
  organization into aliases for use on the
  Internet. So, internal IP addresses remain
  hidden.
• Many organizations combine NAT proxy servers,
  packet filters and application gateways,
  maintaining their online resources in a DMZ
  network between the two

40
Typical network design using firewalls.
41
Denial Of Service

• Denial of service attacks involve the misuse of
  standard TCP/IP protocols connection processes
  so that the target responds in a way which
  maximises disruption - DOSs include
• SMURF attacks - a flood of ICMP echo requests
  (pings) - the target is listed as the source of
  the ping - lots of responses!
• FRAGGLE - as above but with UDP echo
• TCP SYN floods - repeated requests to establish a
  TCP connection to a nonexistent source - causes
  the target to run out of memory
• UNIX process table attacks - like a SYN flood but
  using Unix connections
• Finger of death attacks - like a SYN flood but
  with finger requests that are never disconnected
• A firewall gives little protection against DOS

42
Security Holes

• Security holes are made by flaws in network
  software that permit unintended access to the
  network. Operating systems often contain security
  holes, the details of which can be highly
  technical.
• Once discovered, knowledge about the security
  hole may be quickly circulated on the Internet.
• A race can then begin between hackers attempting
  to break into networks through the security hole
  and security teams working to produce a patch to
  eliminate the security hole.

43
Encryption

• Encryption systems include 4 main components
• Plaintext the unencrypted message
• An encryption algorithm that works like the
  locking mechanism to a safe
• A key that works like the safes combination
• Ciphertext is produced from the plaintext message
  by the encryption function.
• Decryption is the same process in reverse (like a
  modulation/demodulation), but it doesnt always
  use the same key or algorithm. Plaintext results
  from decryption.

44
Encryption Techniques

• There are three important encryption techniques
  now in use
• Symmetric or private key encryption
• Asymmetric or public key encryption
• Digital signatures, which are based on a
  variation of public key encryption.
• (SSL, IPSec are worth knowing about)

45
Detecting Unauthorized Access

• Since unauthorized access can not always be
  prevented, managers need to try to detect when it
  has occurred. This is done using one of three
  types of Intrusion Detection Systems (IDSs)
• Network-based IDSs install IDS sensors on network
  circuits and monitor packets
• Host-based IDSs monitor all activity on the
  server as well as incoming server traffic
• Application-based IDSs are a special form of
  host-based IDSs that monitor just one
  application, such as a Web server.

46
Detecting Intrusions

• Intrusion detection systems use two main
  techniques to determine if an intrusion is in
  progress
• Misuse detection compares monitored activities
  with signatures of known attacks. If an attack is
  recognized the IDS issues an alert.
• Anomaly detection operates in stable computing
  environments and looks for major deviations from
  the normal parameters of network operation.
  When one is detected, (e.g., a large number of
  failed logins), an alert is issued.
• IDSs are often used in conjunction with firewalls
  and other security tools

47
Intrusion Detection System
48
Correcting Unauthorized Access

• Once an unauthorized access is detected, the
  first step is to identify where the security
  breach occurred and fix it so that it will not
  reoccur.
• In order to deter such break-ins, there has been
  a stiffening of computer security laws and in the
  legal interpretation of other laws that pertain
  to computer networks.
• Many organizations have also taken their own
  steps to detect or deter intruders such by using
  entrapment techniques that lure hackers to a
  server with fake information and may even have
  special software to track the hackers origin.