Protocols Flashcards
DHCP
Dynamic Host Configuration Protocol. IOS DHCP Secured IP Address Assignment, combats DHCP spoofing attacks, use case network address allocation attack scenarios
NTP
Network Time Protocol - use case in time synchronization - port 123, or 1023
DNS
Domain Name System - uses TCP/UDP Port 53. resolves Internet names to IP addresses. Consists of clients and servers that provide name translation services.
Uses authoritative servers that host DNS zones, which are the domain namespaces of the org and the subdomains and hosts. Can be primary or secondary servers. Zone file is a mapping of host names to IP addresses and is used to make the name-to-IP address translation
Most common attack - DNS cache poisoning
DNS-SEC
Domain Name System Security Extensions - also uses Port 53. Used with secure domain name resolution and for preventing cache poisoning
RRSIG - resource record signature
DNSKEY record
NSEC - next secure secord
NSEC3 - enables DNS resolvers to verify hash values stored
SNMPv3
Simple Network Management Protocol, version 3 - all versions use UDP ports 161, 162. Basis for many network management tools. Uses SNMP agents that respond to queries, can send traps. SNMPv1 and SNMPv2 lacked security, just clear passwords. version 3 has robust flexible encryption
SSH
Secure Shell protocol - uses TCP port 22. Direct replacement for Telnet and other non-secure remote terminal programs. Designed to run in a tunneling mode, enables any application to run in an encrypted SSH tunnel. Don’t use Telnet
FTP
File Transfer Protocol - uses TCP Ports 20, 21. Enables file upload and download from an FTP server. Inherently non-secure, unencrypted.
FTPS
File Transfer Protocol, Secure. Uses TCP Port 990. Secure FTP that can be used over a Secure Sockets Layer (SSL) or Transport Layer Security (TLS) secure session connection.
SFTP
SSH File Transfer Protocol, functions similarly to normal FTP, but all data is encrypted through an SSH tunnel on port 22. Not the same as FTP or FTPS, does not use SSL or TLS. More common than FTPS
SRTP
Secure Real-time Transport Protocol (SRTP) - uses the same port number as RTP - UDP 5004. Critical component of telephone over IP (VoIP). RTP is insecure.
HTTP
Hypertext Transfer Protocol (HTTP) - runs on Port 80. enables users to access Web resources on the Internet. not secure by itself.
HTTPS
Hypertext Transfer Protocol over SSL/TLS - runs on TCP port 443. sends normal HTTP traffic over an encrypted SSL or TLS connection. HTTPS essential for e-commerce, subscription services.
SSL
Secure Sockets Layer - encryption, authentication services between hosts. TCP port 443.
TLS
Transport Layer Security - TCP port 443. More secure upgrade of SSL, very similar though. Require a back and forth interaction, a SSL/TLS handshake.
1. Client hello. 2. Server hello. 3. Key exchange. 4. Finish
POP3
Post Office Protocol, version 3 - port 110. Non-secure e-mail client protocol used to receive email through client apps. download all the email in the box, then delete the mail from the server. only one connection at a time to the user’s inbox.
IMAP4
Internet Message Access Protocol version 4 - Port 143. Non-secure client e-mail protocol, more widely used than POP3. Can connect to an organizational or Web-based e-mail server, download email messages. Allows multiple connections to the server from multiple user clients, e-mail not automatically deleted from server.