{"id":1292,"date":"2004-02-27T00:00:00","date_gmt":"2004-02-27T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/02\/27\/brainier-networking-gear-to-the-rescue\/"},"modified":"2021-12-30T11:39:07","modified_gmt":"2021-12-30T11:39:07","slug":"brainier-networking-gear-to-the-rescue","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/02\/27\/brainier-networking-gear-to-the-rescue\/","title":{"rendered":"Brainier networking gear to the rescue"},"content":{"rendered":"<p>Networking equipment makers are adding &#8220;intelligence&#8221; to their gear in an effort to protect bandwidth resources from being hijacked by spammers, denial-of-service attackers and peer-to-peer application users.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>TurnTide, a 20-person company based in Conshohocken, Penn., is the latest to take this approach.  Last week, the start-up introduced an &#8220;antispam router,&#8221; which it claims can eliminate up to 90 percent of unsolicited messages.<\/p>\n<p>Unlike spam filters&#8211;which sit near e-mail servers, examining every e-mail message and quarantining those that look bad&#8211;the antispam router looks at the actual packets and determines which ones are likely to have come from a spammer.  Using features inherent in the TCP\/IP (Transmission Control Protocol\/Internet Protocol), it can limit the amount of traffic being sent from these sources.<\/p>\n<p>Ensuring quality of service and implementing security are usually done at the periphery of the network. But as networks get flooded with millions of unwanted e-mail, peer-to-peer traffic, and denial of service attacks, network operators need tools to control how much traffic comes onto their networks.  <\/p>\n<p>More info: http:\/\/zdnet.com.com\/2100-1103_2-5166589.html<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-1292","post","type-post","status-publish","format-standard","hentry","category-product"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1292","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=1292"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1292\/revisions"}],"predecessor-version":[{"id":3779,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1292\/revisions\/3779"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1292"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1292"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1292"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}