Restricted routing infrastructures PPT

Restricted routing infrastructures PPT

• 1.
  Restricted Routing Infrastructures By A.SaiCharan K.Shiva Chandra M.Bhanu Chandar Reddy
• 2.
  INTRODUCTION • In thisproject we design an infrastructure for preventing the un trusted parties getting access to the routing information. • Also we are achieving flexible and efficient communication. However there are some difficulties in doing so they are the new security vulnerability that is introduced. • The flexible control plane of these infrastructures can be exploited to launch many types of powerful attacks with little effort. • In this project, we make several contributions towards studying security issues in forwarding infrastructures (FIs).
• 3.
  Functional Requirements • TheValid user enter into login to send data to available network system • The user enter valid username and password to enter into Login Page • Client is a system which send a request to transfer a file to the server which is connected • Server is a system which provides acknowledgement to the client, Once the server received the file.
• 4.
  Non-Functional Requirements Better componentdesign to get better performance at peak time The system is more reliable. Flexible service based architecture will be highly desirable for future extension
• 5.
  Existing System • Inthe existing system work group list won’t populate or is in complete. Says network resources are unavailable or sites permission problem. • The system doesn’t understood sharing files among all range of system IP address. • There is no interface designed to search the files on a specific LAN. High level views of the system network activity are not provided by the existing system.
• 6.
  Proposed Systems • Inthe system we are going to develop a infrastructure that can prevent the end user in having control over the routing. • And also the infrastructure that is developed is the forwarding infrastructure. FI Model • Identifiers and Forwarding Entries  • Packet Routing Functions • Packet Matching: • Packet Header Update: Threat Model • Security Assumptions. • Attacker Threat Model 
• 7.
  Modules Login Module Assigning Rule SecuringFile Sending the file Receiving File
• 8.
  Environment • Operating System:- Microsoft Windows XP/2000 or • • • • • • Higher Data Base: Microsoft SQL Server 2005/2008 Development Tools: Microsoft Visual Studio .Net 2008/2010 Documentation Tools: MS Office 2007/2010 Drawing Tools: IBM Rational Rose Enterprise, MS Office Visio 2007 User Interface: Windows Forms Code Behind: VC#.NET
• 9.
  Requirements Hardware Requirements:  PIV2.8 GHz Processor and Above  RAM 1GB and Above  HDD 40 GB Hard Disk Space and Above Software Requirements:  WINDOWS OS (XP / 2000 / 2000 Server / 2003 Server)  Visual Studio .Net 2008/2010 Enterprise/Professional Edition  MS.Net Framework 3.5  SQL Server 2005/2008 Enterprise Edition
• 10.
  Choosing File
• 11.
  Assigning Rule
• 12.
  Acknowledgement
• 13.
  CONCLUSION It is concludedthat the application works well and satisfy the users.  The application is tested very well and errors are properly debugged.  The site is simultaneously accessed from more than one system. Simultaneous login from more than one place is tested.
• 14.
  THANK YOU