Topic 11A Flashcards
Application Security
How are HTTP and Telnet insecure protocols
They transmit data in clear text format
In contrast, secure protocols, like HTTPS and SSH (as alternatives to HTTP and TELNET), use encryption to protect transmitted data and improve security.
Why are secure protocols sometimes difficult to work with?
They are more complex to implement and manage.
HTTPS requires obtaining a valid SSL/TLS certificate from a certificate authority (CA). After obtaining the appropriate certificate, it must be correctly installed and configured on a server, which requires more skill, time, and planning than simply enabling and using HTTP.
the correct handling of cryptographic keys, including processes regarding how they are created, stored, distributed, and revoked.
Troubleshooting issues come as administrators cannot easily inspect the content of data packets when troubleshooting issues, and the configuration of secure software and operating systems is more complicated and prone to misconfiguration
TCP (Transmission Control Protocol) and UDP (User Datagram Protocol)
TCP is connection-oriented and provides reliability, ordering, and error-checking, making it suitable for applications requiring high levels of reliability.
UDP is connectionless, making it faster than TCP and more suitable for real-time applications like video streaming, telephony, and gaming, where occasional packet loss is less impactful.
Secure Sockets Layer (SSL)
developed by Netscape in the 1990s to address the lack of security in HTTP.
SSL proved very popular with the industry and was quickly adopted as a standard named Transport Layer Security (TLS)
Secures network apps and can be used as a VPN
Transport Layer Security (TLS)
Security protocol that uses certificates for authentication and encryption to protect web communications and other application protocols.
To implement TLS, a server is assigned a digital certificate signed by some trusted certificate authority (CA). The certificate proves the server’s identity (assuming that the client trusts the CA) and validates the server’s public/private key pair.
The server uses its key pair and the TLS protocol to agree on mutually supported ciphers with the client and negotiate an encrypted communications session.
Still safe to use. Newer than SSL.
TLS version 1.3 was approved in 2018. One of the main features of TLS 1.3 is the removing the ability to perform downgrade attacks by preventing the use of unsecure features and algorithms from previous versions.
cipher suite
the algorithms supported by both the client and server to perform the different encryption and hashing operations required by the protocol.
hash key derivation function (HKDF)
HKDF is the mechanism by which the shared secret established by D-H key agreement is used to derive symmetric session keys.
network directory
lists the subjects (principally users, computers, and services) and objects (such as directories and files) available on the network plus the permissions that subjects have over objects.
Facilitates authentication and authorization, and it is critical that it be maintained as a highly secure service. Most directory services are based on the Lightweight Directory Access Protocol (LDAP)
Generally two levels of access will need to be granted on the directory: read-only access (query) and read/write access (update).
LDAP (Lightweight Directory Access Protocol) and ways to authenticate it.
The basic protocol provides no security and all transmissions are in plaintext
No Authentication—means anonymous access is granted to the directory
.
Simple Bind—means the client must supply its distinguished name (DN) and password, but these are passed as plaintext.
Simple Authentication and Security Layer (SASL)—means the client and server negotiate the use of a supported authentication mechanism, such as Kerberos. The STARTTLS command can be used to require encryption (sealing) and message integrity (signing). This is the preferred mechanism for Microsoft’s Active Directory (AD) implementation of LDAP.
LDAP Secure (LDAPS)—means the server is installed with a digital certificate, which it uses to set up a secure tunnel for the user credential exchange. LDAPS uses port 636.
Simple Network Management Protocol (SNMP)
framework for management and monitoring
SNMP consists of an SNMP monitor and agents.
The agent is a process (software or firmware) running on a switch, router, server, or other SNMP-compatible network device.
This agent maintains a database called a management information base (MIB) that holds statistics relating to the activity of the device. Can initiate a trap operation where it informs management systems of a notable event
The SNMP monitor (a software program) provides a location from which network activity can be overseen. It monitors all agents by polling them at regular intervals for information from their MIBs and displays the information for review. Displays trap alerts
SNMP guidelines to follow
SNMP community names are sent in plaintext and so should not be transmitted over the network if there is any risk that they could be intercepted.
Use difficult-to-guess community names; never leave the community name blank or set to the default.
Use access control lists to restrict management operations to known hosts (that is, restrict to one or two host IP addresses).
Use SNMP v3 whenever possible, and disable older versions of SNMP. SNMP v3 supports encryption and strong user-based authentication.
Disable SNMP if not in use
File Transfer Protocol (FTP)
typically configured with several public directories, hosting files, and user accounts. Most HTTP servers also function as FTP servers, and FTP services, accounts, and directories may be installed and enabled by default when you install a web server.
Is plaintext. Can be secured with SSH that supports SFTP
Secure File Transfer Protocol (SFTP)
encrypting the authentication and data transfer between client and server. In SFTP, a secure link is created between the client and server using Secure Shell (SSH) over TCP port 22.
Hard to configure with firewalls between server and client
Other means to secure FTP
Explicit TLS (FTPES)—uses the AUTH TLS command to upgrade an unsecure connection established over port 21 to a secure one. This protects authentication credentials. The data connection for the file transfers can also be encrypted (using the PROT command).
Implicit TLS (FTPS)—negotiates an SSL/TLS tunnel before the exchange of any FTP commands. This mode uses the secure port 990 for the control connection.
Simple Mail Transfer Protocol (SMTP)
specifies how mail is sent from one system to another.