Which items are examples of insecure services, protocols, or ports?

Which items are examples of insecure services, protocols, or ports?

• A. FTP, Telnet, POP3, IMAP, and SNMP v1 and v2.
• B. HTTPS, SSH, SFTP, SMTPS.
• C. DNSSEC, TLS, IPsec.
• D. SMTP with STARTTLS and FTPS.

Answer: (A)

In PCI contexts, insecure services, protocols, or ports are ones that transmit data or credentials in the clear or rely on weak authentication, making them easy targets for eavesdropping or tampering. The set of items listed first includes several classic examples of such insecure options: FTP and Telnet both send all data, including usernames and passwords, without encryption, so any intercepted traffic can reveal sensitive information. POP3 and IMAP, when used without encryption, likewise transmit credentials in plaintext. SNMP versions 1 and 2 use community strings that travel in the clear, offering little protection against sniffing or unauthorized access. Because these protocols lack robust in-transit security, they’re considered insecure and should be avoided or replaced with secure alternatives (like SSH instead of Telnet, HTTPS/IMAPS/FTPS equivalents, or SNMPv3 for strong authentication and encryption). The other choices describe protocols and services that are designed with encryption or stronger authentication, so they’re not categorized as insecure.

In PCI contexts, insecure services, protocols, or ports are ones that transmit data or credentials in the clear or rely on weak authentication, making them easy targets for eavesdropping or tampering. The set of items listed first includes several classic examples of such insecure options: FTP and Telnet both send all data, including usernames and passwords, without encryption, so any intercepted traffic can reveal sensitive information. POP3 and IMAP, when used without encryption, likewise transmit credentials in plaintext. SNMP versions 1 and 2 use community strings that travel in the clear, offering little protection against sniffing or unauthorized access. Because these protocols lack robust in-transit security, they’re considered insecure and should be avoided or replaced with secure alternatives (like SSH instead of Telnet, HTTPS/IMAPS/FTPS equivalents, or SNMPv3 for strong authentication and encryption). The other choices describe protocols and services that are designed with encryption or stronger authentication, so they’re not categorized as insecure.