Q

Why are TCP/IP networks considered unsecured?

Learn why TCP/IP networks are considered unsecured from our networking security expert, Michael Gregg.

Why are TCP/IP networks not considered secure?
It's not as if designers work to build insecurities into protocols or operating systems. It is really more an issue of priorities. TCP/IP was designed with usability in mind.

In example, consider ARP; it is a two-step process that consists of a request and a response. Little thought was given at the time of the development of ARP that someone may actually send unsolicited ARP responses for the purpose of ARP poisoning. Other protocols and applications of TCP/IP also have security issues, such as ICMP, RIP, FTP, SNMP and Telnet.

Protocols like IPSec were not originally envisioned, and it is actually an add-on to IPv4.

For more information, view this tutorial on understanding TCP/IP from FreeSkills.com.

This was first published in February 2009

Dig deeper on Network Security Best Practices and Products

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

-ADS BY GOOGLE

SearchSDN

SearchEnterpriseWAN

SearchUnifiedCommunications

SearchMobileComputing

SearchDataCenter

SearchITChannel

Close