DESIGN AND IMPLEMENTATION OF NETWORK SECURITY

  • 0 Review(s)

Product Category: Projects

Product Code: 00002941

No of Pages: 55

No of Chapters: 5

File Format: Microsoft Word

Price :

₦3000

  • $

ABSTRACT

Network Security is essential to any organization. This has been previously done by manual method. But this project is aimed at computerized Network Security to make the work easier. This is possible because of the advance improvement in information technology as pertaining programming language; because this is achieved by the help of visual basic programming language and other programming language. For the first few decades of their existence, computer\ networks were primarily used by university researchers for sending e-mail and by corporate employees for sharing printers. Under these conditions, security did not get a lot of attention. But now, as millions of ordinary citizens are using networks for banking, shopping, and filing their tax returns, network security is looming on the horizon as a potentially massive problem. The requirements of information security within an organization have undergone two major changes in the last several decades before the widespread use of data processing equipment the security of information felt to be valuable to an organization was provided primarily by physical and administrative means with the introduction of computer the need for automated tools for protecting files and other information stored on the computer became an evident .this is especially the case for a shared system such as time sharing system and the need is even more acute for systems that can be accessed for a public telephone or a data network the generic name for the collection of tools to protect data and to thwart hackers is ―computer security‖. Network Security is a broad topic and covers a multitude of sins. In its simplest form, it is concerned with making sure that nosy people cannot read, or worse yet, secretly modify messages intended for other recipients. It is concerned with people trying to access remote services that they are not authorized to use. Most security problems are intentionally caused by malicious people trying to gain some benefit, get attention, or to harm someone. Network security problems can be divided roughly into four closely intertwined areas: secrecy, authentication, non repudiation, and integrity control. Secrecy, also called confidentiality, has to do with keeping information out of the hands of unauthorized users. This is what usually comes to mind when people think about network security. Authentication deals with determining whom you are talking to before revealing sensitive information or entering into a business deal. Non repudiation deals with signatures.

 

TABLE OF CONTENT

Title page                                                                                                    i

Certification                                                                                                ii

Dedication                                                                                                  iii

Acknowledgement                                                                                      iv

Abstract                                                                                                      v

Table of content                                                                                          vii

 

CHAPTER ONE

1.0 Introduction                                                                                          1

1.1 Statement of the problem                                                                     5

1.2 Purpose of study                                                                                  6

1.3 Aims and objective of the study                                                           6

1.4 Scope of study                                                                                               6

1.5 Constraints                                                                                           6

1.6 Assumptions                                                                                        7

1.7 Definition of terms                                                                               7

 

CHAPTER TWO

2.0 Literature review                                                                                  9

 

CHAPTER THREE

3.0 Description and analysis of the existing system                                   15

3.1 Fact Finding Method Used                                                                             15

3.2 Objective of the existing system                                                           15

3.3 Organizational chart                                                                                       17

3.4 Input/process/output analysis                                                              18

3.5 Information flow diagram                                                                     20

CHAPTER FOUR

4.0 Design of new system                                                                           21

4.1 Output specification and design                                                           21

4.2 Input specification and design                                                              21

4.3 File design                                                                                            22

4.4 Procedure chat                                                                                      23

4.5 System flowchart                                                                                  24

 

CHAPTER FIVE

5.0 Implementation                                                                                    26

5.1 Program design                                                                                     26

5.2 Program flowcharts                                                                              28

5.3 Documentation                                                                                     29

5.4 Recommendation & Conclusion                                                           30

5.4.1  Recommendation                                                                              30

5. 4.2Conclusion                                                                                        30

5.5 Summary                                                                                              32

Reference                                                                                                    35

Appendix I                                                                                                 36

Appendix II                                                                                                          37

Output display                                                                                           42

 

CHAPTER ONE

1.0    INTRODUCTION

Several recent proposals have argued for giving third parties and end-users control over routing in the network infrastructure. Some examples of such routing architectures include TRIAD [6], i3 [30], NIRA [39], Data Router [33], and Network Pointers [34]. While exposing control over routing to third-parties departs from conventional network architecture, these proposals have shown that such control significantly increases the flexibility and extensibility of these networks.

Using such control, hosts can achieve many functions that are difficult to achieve in the Internet today. Examples of such functions include mobility, multicast, content routing, and service composition. Another somewhat surprising application is that such control can be used by hosts to protect themselves from packet-level denial-of-service (DOS) attacks [18], since, at the extreme, these hosts can remove the forwarding state that malicious hosts use to forward packets to the hosts. While each of these specific functions can be achieved using a specific mechanism—for example, mobile IP allows host mobility— we believe that these forwarding infrastructures (FIs) provide architectural simplicity and uniformity in providing several functions that makes them worth exploring. Forwarding infrastructures typically provide user control by either allowing source-routing (such as [6], [30], [39]) or allowing users to insert forwarding state in the infrastructure (such as [30], [33], [34]). Allowing forwarding entries enables functions like mobility and multicast that are hard to achieve using source-routing alone.

While there seems to be a general agreement over the potential benefits of user-controlled routing architectures, the security vulnerabilities that they introduce has been one of the important concerns that has been not addressed fully. The flexibility that the FIs provide allows malicious entities to attack both the FI as well as hosts connected to the FI.

For instance, consider i3 [30], an indirection-based FI which allows hosts to insert forwarding entries of the form (id,R), so that all packets addressed to id are forwarded to R. An attacker A can eavesdrop or subvert the traffic directed to a victim V by inserting a forwarding entry (idV ,A); the attacker can eavesdrop even when it does not have access to the physical links carrying the victim’s traffic. Alternatively, consider an FI that provides multicast; an attacker can use such an FI to amplify a flooding attack by replicating a packet several times and directing all the replicas to a victim. These vulnerabilities should come as no surprise; in general, the greater the flexibility of the infrastructure, the harder it is to make it secure.

In this project, we improve the security that flexible communication infrastructures which provide a diverse set of operations (such as packet replication) allow. Our main goal in this project is to show that FIs are no more vulnerable than traditional communication networks (such as IP networks) that do not export control on forwarding. To this end, we present several mechanisms that make these FIs achieve certain specific security properties, yet retain the essential features and efficiency of their original design. Our main defense technique, which is based on light-weight cryptographic constraints on forwarding entries, prevents several attacks including eavesdropping, loops, and traffic amplification. From earlier work, we leverage some techniques, such as challenge-responses and erasure-coding, to thwart other attacks.

NETWORK SECURITY

(NS) is an important aspect of any system. NETWORK SECURITY is the act of ensuring that an authenticated user accesses only what they are authorized to and no more. The bad news is that security is rarely at the top of people's lists, although mention terms such as data confidentiality, sensitivity, and ownership and they quickly become interested. The good news is that there is a wide range of techniques that you can apply to help secure access to your system. The bad news is that as Mitnick and Simon (2002) point out …the human factor is the weakest link. Security is too often merely an illusion, an illusion sometimes made even worse when gullibility, naivette, or ignorance come into play. The go on to say that security is not a technology problem – it’s a people and management problem. Having said that, my experience is that the technology factor and the people factor go hand in hand; you need to address both issues to succeed.

Access control is the ability to permit or deny the use of a particular resource by a particular entity. Access control mechanisms can be used in managing physical resources (such as a movie theater, to which only ticket holders should be admitted), logical resources (a bank account, with a limited number of people authorized to make a withdrawal), or digital resources (for example, a private text document on a computer, which only certain users should be able to read).

Banks are secured financial institutions. They are often housed in large buildings that are located in a commercial or residential area. Banks store money and other financial information and goods.

Money and valuables have been stored in banks since ancient times. As a result of the long history that banks have enjoyed, bank security has also been important for a long time. Some of the oldest banks in the world have the best security available. These banks include the Bank of Sweden, the Bank or England, Bank of America, and Swiss Banking.

Bank security usually includes a staff of security guards, a security system, and one or more vaults. Security guards are uniformed personnel that maintain high visibility and watch cameras and alarms. Cameras and alarms are usually top of the line systems in banks and other financial buildings. But these security elements are not exclusive to banks. Some of these elements can be found in other commercial buildings and even residential homes. Basic security starts with the locks. For a high level of security, windows and doors will need the best locks. After high quality locks are installed many property owners opt for a security system or even security cameras.

Security cameras are often a small part of a larger security system. Systems often include motion detectors, alarms, sensors, and cameras. Cameras are arguably the most important because they allow the property owner to see and record everything that happens in and around their building or property.

Cameras can be installed by a professional or by a property owner. For a large and elaborate system it may be best for a professional to do the work. But for a smaller and easy layout, a property owner should have no problem installing a system by following the manufactures instructions. If he does than there is usually a local installer that can be called to help finish the job.

 

1.1    STATEMENT OF THE PROBLEM

Owing to:

1. Fraudulent act of some customer/workers

2. Accessing the organizational data/information unauthorized

3. Sensitive nature of bank data/information

4. Valuable or costly items in bank

5. Increase in crime in our society

The need arise for the development of computerized NETWORK SECURITY to eliminate such problems.

1.2    PURPOSE OF STUDY

The main purpose of this project is to design a NETWORK SECURITY that will assist UBA in the area of ensuring effective security measures.

 

1.3    AIMS AND OBJECTIVES

This project will have the following aims and objectives:

·       Detecting security violations

·       Re-creating security incidents

·       To disallow unauthorized users

·       To safeguard the organizational data/information

·       To computerized the organizational security

·       To enhance the organizational security

·       To eliminate all forms of mistakes associated with security control

1.4    SCOPE OF STUDY

This research work will access the design and implementation of NETWORK SECURITY in UBA Lagos. It will look into the operations of this bank in the aspect of computerizing their security control system.

1.5    CONSTRAINTS

This project will be limited to the data available at hand, data outside the researcher will not be made use of.  The limitations militating against this research are financial constraints, time factor and other circumstances.

 

1.6    ASSUMPTIONS

Accuracy, efficiency and reliability is associated with Network Security.

For the purpose of this research, my assumptions can be stated as follows:

1. The application of computer related garget for security control

2. A computerized Network Security is effective and dependable

1.7    DEFINITION OF TERMS

1. Administration is an aspect of running the organization by devising systems which will run smoothly.

2. Client: This any process that request specific services from server processes.

3. Computer: This is an electrons machine that can accept; handle and manipulate data by performing arithmetic and logic operations without human intervention usually under the control of programmes.

4. Data: This is fore runner of information. It is unprocessed fact.

5. Database is a collection of information that is related to a particular subject or purpose.

6. Hardware: This is the electromechanical part of computer system.

7. Information: This is data that have been processed, interpreted and understood by the recipient of the message or report.

8. Internet is a collection of computer networks that operate to common standards and enable the computes and the program they run to communicate directly.

9. Server: This is a process that provides requested services for clients.

10. Software: This is a logically written program that hardware uses to perform it’s operation.

11. System is the collection of hardware, software, data information, procedures and people.

12. Website is a space or location customized by a company, organization or an individual which is locatable within an address on the internet.

Click “DOWNLOAD NOW” below to get the complete Projects

FOR QUICK HELP CHAT WITH US NOW!

+(234) 0814 780 1594

Buyers has the right to create dispute within seven (7) days of purchase for 100% refund request when you experience issue with the file received. 

Dispute can only be created when you receive a corrupt file, a wrong file or irregularities in the table of contents and content of the file you received. 

ProjectShelve.com shall either provide the appropriate file within 48hrs or send refund excluding your bank transaction charges. Term and Conditions are applied.

Buyers are expected to confirm that the material you are paying for is available on our website ProjectShelve.com and you have selected the right material, you have also gone through the preliminary pages and it interests you before payment. DO NOT MAKE BANK PAYMENT IF YOUR TOPIC IS NOT ON THE WEBSITE.

In case of payment for a material not available on ProjectShelve.com, the management of ProjectShelve.com has the right to keep your money until you send a topic that is available on our website within 48 hours.

You cannot change topic after receiving material of the topic you ordered and paid for.

Ratings & Reviews

0.0

No Review Found.


To Review


To Comment