Your SlideShare is downloading. ×
0
Antony review
Antony review
Antony review
Antony review
Antony review
Antony review
Antony review
Antony review
Antony review
Antony review
Antony review
Antony review
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Antony review

263

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
263
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  1. Detecting Network Traffic Anomalies through Packet Header Data <ul><li>NAME :ANTONY JEBERSON .D </li></ul><ul><li>REG NO :074501502002 </li></ul><ul><li>GUIDED BY </li></ul><ul><li>Mrs.SHIELA FREEDA.MCA,MPhil., </li></ul><ul><li>ASSISTANT PROFESSOR OF MCA DEPT. </li></ul>
  2. ABSTRACT <ul><li>This paper proposes a traffic anomaly detector, operated in postmortem and in real- </li></ul><ul><li>time, by passively monitoring packet headers of traffic. The frequent attacks on </li></ul><ul><li>network infrastructure, using various forms of denial of service attacks, have led to an </li></ul><ul><li>increased need for developing techniques for analyzing network traffic. If efficient </li></ul><ul><li>analysis tools were available, it could become possible to detect the attacks, anomalies </li></ul><ul><li>and to take action to contain the attacks appropriately before they have had time to </li></ul><ul><li>propagate across the network. In this paper, we suggest a technique for traffic anomaly </li></ul><ul><li>detection based on analyzing correlation of destination IP addresses in outgoing traffic </li></ul><ul><li>at an egress router. This address correlation data are transformed using discrete wavelet </li></ul><ul><li>transform for effective detection of anomalies through statistical analysis. Results from </li></ul><ul><li>trace-driven evaluation suggest that proposed approach could provide an effective </li></ul><ul><li>means of detecting anomalies close to the source. We also present a multidimensional </li></ul><ul><li>indicator using the correlation of port numbers and the number of flows as a means of </li></ul><ul><li>detecting anomalies.. </li></ul>
  3. EXISTING SYSTEM: <ul><li>There is no well established existing system to prevent the network traffic. Many approaches have been studied to detect, prevent and mitigate malicious network traffic </li></ul><ul><li>such as IDS (intrusion detection system), try to apply previously established rules against incoming traffic to detect and identify potential DoS attacks close to the victim’s network. </li></ul><ul><li>Work in [43] relies on input data from multiple sources (i.e., all links in a network), while our work focuses on a single link at a time </li></ul>
  4. PROPOSED SYSTEM <ul><li>We focus on analyzing the traffic at an egress router. Monitoring traffic at a source network enables early detection of attacks </li></ul><ul><li>Ingress filtering protects the flow of traffic entering into an internal network under administrative control </li></ul><ul><li>Egress filtering controls the flow of traffic leaving the administered network. Thus, internal machines are typically the origin of this outbound traffic in view of an egress filter </li></ul><ul><li>. </li></ul><ul><li>With such filtering in place, we can focus on destination addresses and port numbers of the outgoing traffic for analysis purposes. </li></ul>
  5. SCOPE OF PROJECT <ul><li>The main aim of the project is to reduce the traffic caused in the network </li></ul><ul><li>while transmitting data’s using egress router and ingress router. </li></ul><ul><li>MODULES </li></ul><ul><li>LOGIN </li></ul><ul><li>CLIENT </li></ul><ul><li> INGRESS ROUTER </li></ul><ul><li>EGRESS ROUTER </li></ul><ul><li>FILE SENDING </li></ul>
  6. DESCRIPTION OF THE MODULES <ul><li>Login: </li></ul><ul><li>In this module the user are allowed to sign up as a new user. Once the user signs in there is a separate log maintained for the particular user. </li></ul><ul><li>The existing user can sign in to perform the operation. </li></ul><ul><li>Client: </li></ul><ul><li>The user who wants to send a file is treated as client. Before selecting a file to send, the client has to provide his details to the server. The client is restricted to choose the file which creates traffic in the network. </li></ul><ul><li>Ingress router: </li></ul><ul><li> Ingress filtering protects the flow of traffic entering into an internal network under administrative control. Once the user signs in to the application his details are stored in the server. After choosing a particular file the details of file is gathered in order to prevent traffic. </li></ul>
  7. <ul><li>Egress router: </li></ul><ul><li>In this module the activities of user after choosing a file is </li></ul><ul><li>checked. An separate log is created for the user. Here all the details including </li></ul><ul><li>size and type of the file he chooses is stored. If he chooses the file which may </li></ul><ul><li>create traffic. the error count in his account gets added. </li></ul><ul><li>File Sending: </li></ul><ul><li>Server checks the size and type of the file chosen by the client. If the </li></ul><ul><li>server finds that it may create traffic then server provide request to the client </li></ul><ul><li>to choose another file. If the client tries to send the file which may create </li></ul><ul><li>traffic for more than 3times, the server disconnects his connection. </li></ul>
  8. DESIGN OF MODULES LOGIN FOR SERVER
  9. SERVER
  10. SEND FILE
  11. ANY QURIES ?
  12. THANK YOU!

×