Detecting static routes in a network
A detection mechanism is disclosed for identifying peers transmitting network traffic towards a cloud provider using routing prefixes that were not advertised for that peer. Once detected, an alarm condition can occur and the peer notified to remove any static route configurations. In one embodiment...
Gespeichert in:
| Hauptverfasser: | , , , , , , , |
|---|---|
| Format: | Patent |
| Sprache: | eng |
| Schlagworte: | |
| Online-Zugang: | Volltext bestellen |
| Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
| container_end_page | |
|---|---|
| container_issue | |
| container_start_page | |
| container_title | |
| container_volume | |
| creator | Neacsu, Valentin Iulian Negm, Ahmed Palladino, Michael W Ambalavanan, Suresh Morales Hernandez, Christine Estefania Groarke, Fiachra John Krishnan, Keerthi Scholl, Thomas Bradley |
| description | A detection mechanism is disclosed for identifying peers transmitting network traffic towards a cloud provider using routing prefixes that were not advertised for that peer. Once detected, an alarm condition can occur and the peer notified to remove any static route configurations. In one embodiment, a collector server computer can be used to acquire routing prefixes advertised to a peer. A second server computer can be used to obtain network traffic received from the peer. A comparison can then be made between the advertised prefixes and the network traffic being received. If network traffic is being received for unadvertised prefixes, then an alarm condition can occur. The detection mechanism can regularly inspect active traffic flows against BGP route advertisements at fixed intervals. For peers that are identified that are not in compliance with route advertisements, the alarm condition can occur for follow-up remediation. |
| format | Patent |
| fullrecord | <record><control><sourceid>epo_EVB</sourceid><recordid>TN_cdi_epo_espacenet_US11985064B1</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><sourcerecordid>US11985064B1</sourcerecordid><originalsourceid>FETCH-epo_espacenet_US11985064B13</originalsourceid><addsrcrecordid>eNrjZFBxSS1JTS7JzEtXKC5JLMlMVijKLy1JLVbIzFNIVMhLLSnPL8rmYWBNS8wpTuWF0twMim6uIc4euqkF-fGpxQWJyalAlfGhwYaGlhamBmYmTobGxKgBAAzkJuQ</addsrcrecordid><sourcetype>Open Access Repository</sourcetype><iscdi>true</iscdi><recordtype>patent</recordtype></control><display><type>patent</type><title>Detecting static routes in a network</title><source>esp@cenet</source><creator>Neacsu, Valentin Iulian ; Negm, Ahmed ; Palladino, Michael W ; Ambalavanan, Suresh ; Morales Hernandez, Christine Estefania ; Groarke, Fiachra John ; Krishnan, Keerthi ; Scholl, Thomas Bradley</creator><creatorcontrib>Neacsu, Valentin Iulian ; Negm, Ahmed ; Palladino, Michael W ; Ambalavanan, Suresh ; Morales Hernandez, Christine Estefania ; Groarke, Fiachra John ; Krishnan, Keerthi ; Scholl, Thomas Bradley</creatorcontrib><description>A detection mechanism is disclosed for identifying peers transmitting network traffic towards a cloud provider using routing prefixes that were not advertised for that peer. Once detected, an alarm condition can occur and the peer notified to remove any static route configurations. In one embodiment, a collector server computer can be used to acquire routing prefixes advertised to a peer. A second server computer can be used to obtain network traffic received from the peer. A comparison can then be made between the advertised prefixes and the network traffic being received. If network traffic is being received for unadvertised prefixes, then an alarm condition can occur. The detection mechanism can regularly inspect active traffic flows against BGP route advertisements at fixed intervals. For peers that are identified that are not in compliance with route advertisements, the alarm condition can occur for follow-up remediation.</description><language>eng</language><subject>ELECTRIC COMMUNICATION TECHNIQUE ; ELECTRICITY ; TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHICCOMMUNICATION</subject><creationdate>2024</creationdate><oa>free_for_read</oa><woscitedreferencessubscribed>false</woscitedreferencessubscribed></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktohtml>$$Uhttps://worldwide.espacenet.com/publicationDetails/biblio?FT=D&date=20240514&DB=EPODOC&CC=US&NR=11985064B1$$EHTML$$P50$$Gepo$$Hfree_for_read</linktohtml><link.rule.ids>230,308,776,881,25542,76290</link.rule.ids><linktorsrc>$$Uhttps://worldwide.espacenet.com/publicationDetails/biblio?FT=D&date=20240514&DB=EPODOC&CC=US&NR=11985064B1$$EView_record_in_European_Patent_Office$$FView_record_in_$$GEuropean_Patent_Office$$Hfree_for_read</linktorsrc></links><search><creatorcontrib>Neacsu, Valentin Iulian</creatorcontrib><creatorcontrib>Negm, Ahmed</creatorcontrib><creatorcontrib>Palladino, Michael W</creatorcontrib><creatorcontrib>Ambalavanan, Suresh</creatorcontrib><creatorcontrib>Morales Hernandez, Christine Estefania</creatorcontrib><creatorcontrib>Groarke, Fiachra John</creatorcontrib><creatorcontrib>Krishnan, Keerthi</creatorcontrib><creatorcontrib>Scholl, Thomas Bradley</creatorcontrib><title>Detecting static routes in a network</title><description>A detection mechanism is disclosed for identifying peers transmitting network traffic towards a cloud provider using routing prefixes that were not advertised for that peer. Once detected, an alarm condition can occur and the peer notified to remove any static route configurations. In one embodiment, a collector server computer can be used to acquire routing prefixes advertised to a peer. A second server computer can be used to obtain network traffic received from the peer. A comparison can then be made between the advertised prefixes and the network traffic being received. If network traffic is being received for unadvertised prefixes, then an alarm condition can occur. The detection mechanism can regularly inspect active traffic flows against BGP route advertisements at fixed intervals. For peers that are identified that are not in compliance with route advertisements, the alarm condition can occur for follow-up remediation.</description><subject>ELECTRIC COMMUNICATION TECHNIQUE</subject><subject>ELECTRICITY</subject><subject>TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHICCOMMUNICATION</subject><fulltext>true</fulltext><rsrctype>patent</rsrctype><creationdate>2024</creationdate><recordtype>patent</recordtype><sourceid>EVB</sourceid><recordid>eNrjZFBxSS1JTS7JzEtXKC5JLMlMVijKLy1JLVbIzFNIVMhLLSnPL8rmYWBNS8wpTuWF0twMim6uIc4euqkF-fGpxQWJyalAlfGhwYaGlhamBmYmTobGxKgBAAzkJuQ</recordid><startdate>20240514</startdate><enddate>20240514</enddate><creator>Neacsu, Valentin Iulian</creator><creator>Negm, Ahmed</creator><creator>Palladino, Michael W</creator><creator>Ambalavanan, Suresh</creator><creator>Morales Hernandez, Christine Estefania</creator><creator>Groarke, Fiachra John</creator><creator>Krishnan, Keerthi</creator><creator>Scholl, Thomas Bradley</creator><scope>EVB</scope></search><sort><creationdate>20240514</creationdate><title>Detecting static routes in a network</title><author>Neacsu, Valentin Iulian ; Negm, Ahmed ; Palladino, Michael W ; Ambalavanan, Suresh ; Morales Hernandez, Christine Estefania ; Groarke, Fiachra John ; Krishnan, Keerthi ; Scholl, Thomas Bradley</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-epo_espacenet_US11985064B13</frbrgroupid><rsrctype>patents</rsrctype><prefilter>patents</prefilter><language>eng</language><creationdate>2024</creationdate><topic>ELECTRIC COMMUNICATION TECHNIQUE</topic><topic>ELECTRICITY</topic><topic>TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHICCOMMUNICATION</topic><toplevel>online_resources</toplevel><creatorcontrib>Neacsu, Valentin Iulian</creatorcontrib><creatorcontrib>Negm, Ahmed</creatorcontrib><creatorcontrib>Palladino, Michael W</creatorcontrib><creatorcontrib>Ambalavanan, Suresh</creatorcontrib><creatorcontrib>Morales Hernandez, Christine Estefania</creatorcontrib><creatorcontrib>Groarke, Fiachra John</creatorcontrib><creatorcontrib>Krishnan, Keerthi</creatorcontrib><creatorcontrib>Scholl, Thomas Bradley</creatorcontrib><collection>esp@cenet</collection></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext_linktorsrc</fulltext></delivery><addata><au>Neacsu, Valentin Iulian</au><au>Negm, Ahmed</au><au>Palladino, Michael W</au><au>Ambalavanan, Suresh</au><au>Morales Hernandez, Christine Estefania</au><au>Groarke, Fiachra John</au><au>Krishnan, Keerthi</au><au>Scholl, Thomas Bradley</au><format>patent</format><genre>patent</genre><ristype>GEN</ristype><title>Detecting static routes in a network</title><date>2024-05-14</date><risdate>2024</risdate><abstract>A detection mechanism is disclosed for identifying peers transmitting network traffic towards a cloud provider using routing prefixes that were not advertised for that peer. Once detected, an alarm condition can occur and the peer notified to remove any static route configurations. In one embodiment, a collector server computer can be used to acquire routing prefixes advertised to a peer. A second server computer can be used to obtain network traffic received from the peer. A comparison can then be made between the advertised prefixes and the network traffic being received. If network traffic is being received for unadvertised prefixes, then an alarm condition can occur. The detection mechanism can regularly inspect active traffic flows against BGP route advertisements at fixed intervals. For peers that are identified that are not in compliance with route advertisements, the alarm condition can occur for follow-up remediation.</abstract><oa>free_for_read</oa></addata></record> |
| fulltext | fulltext_linktorsrc |
| identifier | |
| ispartof | |
| issn | |
| language | eng |
| recordid | cdi_epo_espacenet_US11985064B1 |
| source | esp@cenet |
| subjects | ELECTRIC COMMUNICATION TECHNIQUE ELECTRICITY TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHICCOMMUNICATION |
| title | Detecting static routes in a network |
| url | https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-01-28T14%3A11%3A54IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-epo_EVB&rft_val_fmt=info:ofi/fmt:kev:mtx:patent&rft.genre=patent&rft.au=Neacsu,%20Valentin%20Iulian&rft.date=2024-05-14&rft_id=info:doi/&rft_dat=%3Cepo_EVB%3EUS11985064B1%3C/epo_EVB%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_id=info:pmid/&rfr_iscdi=true |