Chapter 3 Objective 3.1 Insecure Protocols Telnet → Port 23 → Telnet transmits data in plaintext, vulnerable to MITM & Eavesdropping Secure Alternative → SSH → Port 22 → SSH provides encrypted communication FTP → Port 21 → FTP transmits data in plaintext, vulnerable to interception & tampering Secure Alternative → FTPS (FTP Secure) → Port 990 / 989 → Uses SSL / TLS for encryption SFTP (SSH File Transfer Protocol) → Port 22 → Uses SSH for file transfer HTTP → Port 80 → HTTP transmits data in plaintext Secure Alternative → HTTPS → HTTP Secure → Port 443 → Uses SSL / TLS SMTP → Port 25 → SMTP transmits emails in plaintext, vulnerable to interception & unauthorized access Secure Alternative → SMTPS → SMTP Secure → Port 465 → use SSL/TLS to encrypt email communications SMTP with STARTTLS → Port 587 → use SSL/TLS to encrypt email communications POP3 → Port 110 → POP3 transmits emails in plaintext, vulnerable to eavesdropping Secure Alternative → POP3S → POP3 Secure → Port 995 → uses SSL/TLS IMAP → Port 143 → IMAP transmits data in plaintext, vulnerable to interception Secure Alternative → IMAPS (IMAP Secure) → Port 993 → uses SSL / TLS SNMP v1/v2 → Port 161/162 → Lacks encryption, vulnerable to interception & tampering Secure Alternative → SNMPv3 → Port 161/162 → Adds encryption, authentication & integrity protection to data LDAP → Port 389 → LDAP transmits data in plaintext, vulnerable to interception & tampering Secure Alternative → LDAPS (LDAP Secure) → Port 636 → Uses SSL/TLS for encrypt directory service Protocols DNS Security Extensions (DNSSEC) → Provides validation for DNS responses It adds Resource Record Signature (RRSIG) (Digital Signature) to each record RRSIG provides data integrity & authentication for DNS replies Helps to prevent DNS poisoning attack S/MIME → Secure/Multipurpose Internet Mail Extensions Used to digitally sign & encrypt an email Uses both asymmetric & symmetric encryption SRTP → Secure Real Time Protocol → Uses port 5004 RTP → Real Time Protocol → Delivers audio & video over IP networks SRTP provides encryption, message authentication & integrity for RTP LDAPS → LDAP over TLS uses port 636 FTPS → FTP, Secure → uses TLS to encrypt FTP traffic SNMPv3 → Simple Network Management Protocol → Monitors & manages network devices such as routers & switches Uses port 161/162 Can modify devices’ configuration & can check device report status SNMPv3 agents installed on devices send information to SNMP manager via notifications known as traps Flood guard sends SNMP trap messages in response to an alert SNMP Usage → Commonly used to gather information from routers, switches, and other network devices → It provides information about a device’s status, including CPU and memory utilization, as well as many other useful details about the device IPSec → Used to encrypt IP traffic Authentication Header → IPSec uses AH to allow each conversation hosts to authenticate with each other before exchanging the data AH provides authentication & integrity Encryption → IPSec includes Encapsulating Security Payload (ESP) to encrypt data & provide confidentiality IPSec uses Internet Key Exchange (IKE) to authenticate clients in the IPSec conversation → Internet key exchange (IKE) is used to set up security associations (SAs) on each end of the tunnel....