The SecOps Group CNSP Practice Exam - 62 Unique Questions
Latest Questions CNSP Guide to Prepare Free Practice Tests
The SecOps Group CNSP Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
| Topic 6 |
|
| Topic 7 |
|
| Topic 8 |
|
| Topic 9 |
|
| Topic 10 |
|
| Topic 11 |
|
NEW QUESTION # 36
Which of the aforementioned SSL/TLS protocols are considered to be unsafe?
- A. TLSv1.0 and TLSv1.1
- B. SSLv2 and SSLv3
- C. Both A and B
- D. SSLv2, SSLv3, TLSv1.0, TLSv1.1, TLSv1.2, and TLSv1.3
Answer: C
Explanation:
SSL/TLS protocols secure network communication, but older versions have vulnerabilities:
SSLv2 (1995): Weak ciphers, no handshake integrity (e.g., MITM via DROWN attack, CVE-2016-0800). Deprecated by RFC 6176 (2011).
SSLv3 (1996): Vulnerable to POODLE (CVE-2014-3566), weak block ciphers (e.g., RC4). Deprecated by RFC 7568 (2015).
TLSv1.0 (1999, RFC 2246): Inherits SSLv3 flaws (e.g., BEAST, CVE-2011-3389), weak CBC ciphers. Deprecated by PCI DSS (2018) and RFC 8996 (2021).
TLSv1.1 (2006, RFC 4346): Improved over 1.0 but lacks modern cipher suites (e.g., AEAD). Deprecated with 1.0 by RFC 8996.
TLSv1.2 (2008, RFC 5246): Secure with strong ciphers (e.g., AES-GCM), widely used today.
TLSv1.3 (2018, RFC 8446): Latest, removes legacy weaknesses, mandatory forward secrecy.
Why other options are incorrect:
A: Correct but incomplete without B.
B: Correct but incomplete without A.
D: Incorrectly includes TLSv1.2 and 1.3, which are secure and recommended.
Real-World Context: POODLE forced mass SSLv3 disablement in 2014; TLS 1.0/1.1 deprecation hit legacy systems in 2021.
NEW QUESTION # 37
In a Linux-based architecture, what does the /mnt directory contain?
- A. System configuration files and initialization scripts
- B. Temporary-mounted filesystems
- C. Loadable driver modules needed to boot the system
- D. System files which represent the current state of the kernel
Answer: B
Explanation:
The Linux Filesystem Hierarchy Standard (FHS), per FHS 3.0, defines directory purposes:
/mnt: Designated for temporarily mounted filesystems, typically by system administrators.
Use: Mount points for removable media (e.g., USB drives: mount /dev/sdb1 /mnt/usb) or network shares (e.g., NFS).
Nature: Transient, user-managed, not persistent across reboots (unlike /etc/fstab mounts).
Contrast:
/media: Auto-mounts removable devices (e.g., by desktop environments like GNOME).
/mnt vs. /media: /mnt is manual, /media is system-driven.
Technical Details:
Empty by default; subdirectories (e.g., /mnt/usb) are created as needed.
Permissions: Typically root-owned (0755), requiring sudo for mounts.
Security Implications: Misconfigured /mnt mounts (e.g., world-writable) risk unauthorized access. CNSP likely covers mount security (e.g., nosuid option).
Why other options are incorrect:
B . System config/init scripts: Found in /etc (e.g., /etc/passwd, /etc/init.d).
C . Driver modules: Located in /lib/modules/<kernel-version>.
D . Kernel state: Resides in /proc (e.g., /proc/cpuinfo).
Real-World Context: Admins mount ISOs at /mnt during server provisioning (e.g., mount -o loop image.iso /mnt).
NEW QUESTION # 38
Which SMB (Server Message Block) network protocol versions are vulnerable to the EternalBlue (MS17-010) Windows exploit?
- A. Both SMBv1 and SMBv2
- B. SMBv1 only
- C. SMBv2 only
- D. SMBv3 only
Answer: B
Explanation:
EternalBlue (MS17-010) is an exploit targeting a buffer overflow in Microsoft's SMB (Server Message Block) implementation, leaked by the Shadow Brokers in 2017. SMB enables file/printer sharing:
SMBv1 (1980s): Legacy, used in Windows NT/XP.
SMBv2 (2006, Vista): Enhanced performance/security.
SMBv3 (2012, Windows 8): Adds encryption, multichannel.
Vulnerability:
EternalBlue exploits a flaw in SMBv1's SRVNET driver (srv.sys), allowing remote code execution via crafted packets. Microsoft patched it in March 2017 (MS17-010).
Affected OS: Windows XP to Server 2016 (pre-patch), if SMBv1 enabled.
Proof: WannaCry/NotPetya used it, targeting port 445/TCP.
SMBv1 Only: The bug resides in SMBv1's packet handling (e.g., TRANS2 requests). SMBv2/v3 rewrote this code, immune to the specific overflow.
Microsoft: Post-patch, SMBv1 is disabled by default (Windows 10 1709+).
Security Implications: CNSP likely stresses disabling SMBv1 (e.g., via Group Policy) and patching, as EternalBlue remains a threat in legacy environments.
Why other options are incorrect:
B, C: SMBv2/v3 aren't vulnerable; the flaw is SMBv1-specific.
D: SMBv2 isn't affected, only SMBv1.
Real-World Context: WannaCry's 2017 rampage hit unpatched SMBv1 systems (e.g., NHS), costing billions.
NEW QUESTION # 39
You are performing a security audit on a company's infrastructure and have discovered that the domain name system (DNS) server is vulnerable to a DNS cache poisoning attack. What is the primary security risk?
- A. The primary risk is that an attacker could manipulate the cache of the web server or proxy server to return incorrect content for a specific URL or web page.
- B. The primary risk is that an attacker could redirect traffic to a malicious website and steal sensitive information.
Answer: B
Explanation:
DNS cache poisoning, also known as DNS spoofing, involves an attacker injecting false DNS records into a resolver's cache, altering how domain names resolve.
Why A is correct: The primary risk is that an attacker can redirect users to malicious websites (e.g., phishing or malware sites) by poisoning the DNS cache with fake IP addresses. This can lead to credential theft, data exfiltration, or malware distribution. CNSP identifies this as the core threat of DNS cache poisoning, aligning with real-world attack vectors.
Why other option is incorrect:
B . Manipulate the cache of the web server or proxy server: This describes web cache poisoning, a different attack targeting HTTP caches, not DNS servers. DNS cache poisoning affects DNS resolution, not web or proxy server caches directly.
NEW QUESTION # 40
Which one of the following services is not a UDP-based protocol?
- A. SSH
- B. NTP
- C. IKE
- D. SNMP
Answer: A
Explanation:
Protocols are defined by their transport layer usage (TCP or UDP), impacting their security and performance characteristics.
Why D is correct: SSH (Secure Shell) uses TCP (port 22) for reliable, connection-oriented communication, unlike the UDP-based options. CNSP contrasts TCP and UDP protocol security.
Why other options are incorrect:
A: SNMP uses UDP (ports 161, 162) for lightweight network management.
B: NTP uses UDP (port 123) for time synchronization.
C: IKE (IPsec key exchange) uses UDP (ports 500, 4500).
NEW QUESTION # 41
What RID is given to an Administrator account on a Microsoft Windows machine?
- A. 0
- B. 1
- C. 2
- D. 3
Answer: C
Explanation:
In Windows, security principals (users, groups) are identified by a Security Identifier (SID), formatted as S-1-<authority>-<domain>-<RID>. The RID (Relative Identifier) is the final component, unique within a domain or machine. For local accounts:
RID 500: Assigned to the built-in Administrator account on every Windows machine (e.g., S-1-5-21-<machine>-500).
Created during OS install, with full system privileges.
Disabled by default in newer Windows versions (e.g., 10/11) unless explicitly enabled.
RID 501: Guest account (e.g., S-1-5-21-<machine>-501), limited access.
Technical Details:
Stored in SAM (C:\Windows\System32\config\SAM).
Enumeration: Tools like wmic useraccount or net user reveal RIDs.
Domain Context: Domain Admins use RID 512, but the question specifies a local machine.
Security Implications: RID 500 is a prime target for brute-forcing or pass-the-hash attacks (e.g., Mimikatz). CNSP likely advises renaming/disabling it (e.g., via GPO).
Why other options are incorrect:
A . 0: Reserved (e.g., Null SID, S-1-0-0), not a user RID.
C . 501: Guest, not Administrator.
D . 100: Invalid; local user RIDs start at 1000 (e.g., custom accounts).
Real-World Context: Post-compromise, attackers query RID 500 (e.g., net user Administrator) for privilege escalation.
NEW QUESTION # 42
You are performing a security audit on a company's network infrastructure and have discovered the SNMP community string set to the default value of "public" on several devices. What security risks could this pose, and how might you exploit it?
- A. Both A and B.
- B. None of the above.
- C. The potential risk is that an attacker could use the SNMP protocol to gather sensitive information about the devices. You might use a tool like Snmpwalk to query the devices for information.
- D. The potential risk is that an attacker could use the SNMP protocol to modify the devices' configuration settings. You might use a tool like Snmpset to change the settings.
Answer: C
Explanation:
SNMP (Simple Network Management Protocol) uses community strings as a basic form of authentication. The default read-only community string "public" is widely known, and if left unchanged, it exposes devices to unauthorized access. The primary risk with "public" is information disclosure, as it typically grants read-only access, allowing attackers to gather sensitive data (e.g., device configurations, network topology) without altering settings.
Why A is correct: With the "public" string, an attacker can use tools like snmpwalk to enumerate device details (e.g., system uptime, interfaces, or software versions) via SNMP queries. This aligns with CNSP's focus on reconnaissance risks during security audits, emphasizing the danger of default credentials enabling passive data collection.
Why other options are incorrect:
B: While modifying settings is a risk with SNMP, the default "public" string is typically read-only. Changing configurations requires a read-write community string (e.g., "private"), which isn't implied here. Thus, snmpset would not work with "public" alone.
C: Since B is incorrect in this context, C (both A and B) cannot be the answer.
D: The risk in A is valid, so "none of the above" is incorrect.
NEW QUESTION # 43
What is the response from an open UDP port which is behind a firewall (port is open on the firewall)?
- A. A SYN Packet
- B. A FIN Packet
- C. No response
- D. ICMP message showing Port Unreachable
Answer: C
Explanation:
UDP (User Datagram Protocol), per RFC 768, is connectionless, lacking TCP's handshake or acknowledgment mechanisms. When a UDP packet reaches a port:
Closed Port: The host typically sends an ICMP "Destination Port Unreachable" (Type 3, Code 3) unless suppressed (e.g., by firewall or OS settings).
Open Port: If a service is listening (e.g., DNS on 53/UDP), it processes the packet but doesn't inherently reply unless the application protocol requires it (e.g., DNS sends a response).
Scenario: An open UDP port behind a firewall, with the firewall rule allowing traffic (e.g., permit udp any host 10.0.0.1 eq 123). The packet reaches the service, but UDP itself doesn't mandate a response. Most services (e.g., NTP, SNMP) only reply if the packet matches an expected request. In this question's generic context (no specific service), no response is the default, as the firewall permits the packet, and the open port silently accepts it without feedback.
Security Implications: This silence makes UDP ports harder to scan (e.g., Nmap assumes "open|filtered" for no response), but exposed open ports risk amplification attacks (e.g., DNS reflection). CNSP likely contrasts UDP's behavior with TCP for firewall rule crafting.
Why other options are incorrect:
A . ICMP message showing Port Unreachable: Occurs for closed ports, not open ones, unless the service explicitly rejects the packet (rare).
C . A SYN Packet: SYN is TCP-specific (handshake initiation), irrelevant to UDP.
D . A FIN Packet: FIN is TCP-specific (connection closure), not UDP.
Real-World Context: Testing UDP 53 (DNS) with dig @8.8.8.8 +udp yields a response, but generic UDP probes (e.g., nc -u) often get silence.
NEW QUESTION # 44
What ports does an MSSQL server typically use?
- A. 1433/TCP, 2433/UDP, and 3433/TCP
- B. 1533/TCP, 1434/UDP, and 2434/TCP
- C. 1433/TCP, 1434/UDP, and 1434/TCP
- D. 1433/TCP, 2433/UDP, and 1434/TCP
Answer: C
Explanation:
Microsoft SQL Server (MSSQL) relies on specific ports for its core services, as defined by Microsoft and registered with IANA:
1433/TCP: The default port for the SQL Server Database Engine. Clients connect here for querying databases (e.g., via ODBC or JDBC). It's a well-known port, making it a frequent target for attacks if exposed.
1434/UDP: Used by the SQL Server Browser Service, which listens for incoming requests and redirects clients to the correct port/instance (especially for named instances). It's critical for discovering dynamic ports when 1433 isn't used.
1434/TCP: Less commonly highlighted but used in some configurations, such as dedicated admin connections (DAC) or when the Browser Service responds over TCP for specific instances. While 1433/TCP is the primary engine port, 1434/TCP can be involved in multi-instance setups.
Technical Details:
Ports can be customized (e.g., via SQL Server Configuration Manager), but these are defaults.
Named instances often use dynamic ports (allocated from the ephemeral range), with the Browser Service (1434/UDP) guiding clients to them.
Firewalls must allow these ports for MSSQL to function externally, posing risks if not secured (e.g., brute-force attacks on 1433/TCP).
Security Implications: CNSP likely covers MSSQL port security, as vulnerabilities like SQL Slammer (2003) exploited 1434/UDP misconfigurations. Hardening includes restricting access, changing defaults, and monitoring traffic.
Why other options are incorrect:
A . 1433/TCP, 2433/UDP, 3433/TCP: 2433/UDP and 3433/TCP are not MSSQL standards; they're likely typos or unrelated ports.
C . 1433/TCP, 2433/UDP, 1434/TCP: 2433/UDP is incorrect; 1434/UDP is the Browser Service port.
D . 1533/TCP, 1434/UDP, 2434/TCP: 1533/TCP and 2434/TCP aren't associated with MSSQL; they deviate from documented defaults.
Real-World Context: Tools like netstat -an | find "1433" on Windows confirm MSSQL's port usage during audits.
NEW QUESTION # 45
Which of the following techniques can be used to bypass network segmentation during infrastructure penetration testing?
- A. DNS tunneling
- B. Covert channels
- C. All of the above
- D. VLAN hopping
Answer: C
Explanation:
Network segmentation isolates network zones for security, but certain techniques can circumvent these controls, a focus of CNSP penetration testing.
Why D is correct:
A: DNS tunneling encodes data in DNS queries, bypassing segmentation via legitimate DNS traffic.
B: VLAN hopping exploits switch misconfigurations (e.g., double tagging) to access other VLANs.
C: Covert channels use hidden communication paths (e.g., timing channels) to evade segmentation.
All are valid techniques per CNSP for testing segmentation controls.
Why other options are incomplete: A, B, or C alone exclude other viable methods, making D the comprehensive answer.
NEW QUESTION # 46
The application is showing a TLS error message as a result of a website administrator failing to timely renew the TLS certificate. But upon deeper analysis, it appears that the problem is brought on by the expiration of the TLS certificate. Which of the following statements is correct?
- A. The communication between the browser and the server is still over TLS.
- B. The communication between the browser and the server is now no longer over TLS.
Answer: B
Explanation:
TLS (Transport Layer Security) secures communication (e.g., HTTPS) using certificates, per RFC 8446. A certificate includes:
Validity Period: Start and end dates (e.g., "Not After: March 8, 2025").
Purpose: Authenticates the server and encrypts the session.
Scenario: An expired TLS certificate (e.g., past "Not After" date). Modern browsers (e.g., Chrome, Firefox) validate certificates during the handshake:
ClientHello: Browser initiates TLS.
ServerHello: Server sends its certificate.
Validation: Browser checks expiration, CA trust, etc.
If expired, browsers reject the handshake, displaying errors (e.g., "NET::ERR_CERT_DATE_INVALID"). No session key is negotiated, and communication doesn't proceed over TLS. Users may bypass warnings (e.g., "Advanced > Proceed"), but this is unencrypted or uses a fallback (not standard TLS), breaking security guarantees.
Security Implications: Expired certificates expose sites to MITM attacks, as trust is lost. CNSP likely emphasizes certificate management (e.g., automation with Let's Encrypt) to avoid this.
Why other options are incorrect:
B . The communication is still over TLS: False; an expired certificate halts the TLS handshake in compliant browsers. Legacy systems might negotiate insecurely, but this isn't "TLS" per standards.
Real-World Context: The 2019 Equifax breach partially stemmed from expired certificates missing vulnerabilities.
NEW QUESTION # 47
What kind of files are "Dotfiles" in a Linux-based architecture?
- A. Driver files
- B. Hidden files
- C. System files
- D. Library files
Answer: B
Explanation:
In Linux, file visibility is determined by naming conventions, impacting how files are listed or accessed in the file system.
Why D is correct: "Dotfiles" are files or directories with names starting with a dot (e.g., .bashrc), making them hidden by default in directory listings (e.g., ls requires -a to show them). They are commonly used for user configuration, as per CNSP's Linux security overview.
Why other options are incorrect:
A: Library files (e.g., in /lib) aren't inherently hidden.
B: Driver files (e.g., kernel modules in /lib/modules) aren't dotfiles by convention.
C: System files may or may not be hidden; "dotfiles" specifically denotes hidden status.
NEW QUESTION # 48
In the context of the SSH (Secure Shell) public-private key authentication mechanism, which key is uploaded to the server and which key is used by the end-user for authentication?
- A. The private key is uploaded to the server and the public key is used by the end user for authentication.
- B. The public key is uploaded to the server and the private key is used by the end user for authentication.
Answer: B
Explanation:
SSH (Secure Shell), per RFC 4251, uses asymmetric cryptography (e.g., RSA, ECDSA) for secure authentication:
Key Pair:
Public Key: Freely shareable, used to encrypt or verify.
Private Key: Secret, used to decrypt or sign.
Process:
User generates a key pair (e.g., ssh-keygen -t rsa -b 4096).
Public Key is uploaded to the server, appended to ~/.ssh/authorized_keys (e.g., via ssh-copy-id).
Private Key (e.g., ~/.ssh/id_rsa) stays on the user's machine.
Authentication: Client signs a challenge with the private key; server verifies it with the public key.
Technical Details:
Protocol: SSH-2 (RFC 4253) uses a Diffie-Hellman key exchange, then public-key auth.
Files: authorized_keys (server, 0644 perms), private key (client, 0600 perms).
Security: Private key exposure compromises all systems trusting the public key.
Security Implications: CNSP likely stresses key management (e.g., passphrases, rotation) and server-side authorized_keys hardening (e.g., PermitRootLogin no).
Why other options are incorrect:
B: Uploading the private key reverses the model, breaking security-anyone with the server's copy could authenticate as the user. Asymmetric crypto relies on the private key remaining secret.
Real-World Context: GitHub uses SSH public keys for repository access, with private keys on user devices.
NEW QUESTION # 49
Which SMB (Server Message Block) network protocol version introduced support for encrypting SMB traffic?
- A. None of the above
- B. SMBv3
- C. SMBv1
- D. SMBv2
Answer: B
Explanation:
The SMB protocol, used for file and printer sharing, has evolved across versions, with significant security enhancements in later iterations.
Why C is correct: SMBv3, introduced with Windows 8 and Server 2012, added native support for encrypting SMB traffic. This feature uses AES-CCM encryption to protect data in transit, addressing vulnerabilities in earlier versions. CNSP notes SMBv3's encryption as a critical security improvement.
Why other options are incorrect:
A . SMBv1: Lacks encryption support and is considered insecure, often disabled due to vulnerabilities like WannaCry exploitation.
B . SMBv2: Introduces performance improvements but does not support encryption natively.
D . None of the above: Incorrect, as SMBv3 is the version that introduced encryption.
NEW QUESTION # 50
What is the response from an open UDP port which is not behind a firewall?
- A. A SYN packet
- B. A FIN packet
- C. No response
- D. ICMP message showing Port Unreachable
Answer: C
Explanation:
UDP's connectionless nature means it lacks inherent acknowledgment mechanisms, affecting its port response behavior.
Why B is correct: An open UDP port does not respond unless an application explicitly sends a reply. Without a firewall or application response, the sender receives no feedback, per CNSP scanning guidelines.
Why other options are incorrect:
A: ICMP Port Unreachable indicates a closed port, not an open one.
C: SYN packets are TCP-specific, not UDP.
D: FIN packets are also TCP-specific.
NEW QUESTION # 51
Which built-in Windows utility can be used to verify the validity of a Kerberos ticket?
- A. Klist
- B. Kerberos Manager
- C. Netsh
- D. Kerbtray
Answer: A
Explanation:
Kerberos is the default authentication protocol in Windows Active Directory environments, and tickets are used to prove identity. Verifying ticket validity involves checking their status, expiration, and attributes, which requires a built-in tool available in modern Windows systems.
Why A is correct: Klist is a command-line utility included in Windows (since Vista/2008) that lists cached Kerberos tickets and their details, such as validity period and renewal status. CNSP recognizes it as the standard tool for Kerberos ticket management in security audits.
Why other options are incorrect:
B: Kerbtray is a graphical tool from the Windows Resource Kit, not a built-in utility, and is outdated.
C: Netsh manages network configurations, not Kerberos tickets.
D: "Kerberos Manager" is not a recognized built-in Windows utility; it's a fictitious name.
NEW QUESTION # 52
How many octets are there in an IPv6 address?
- A. 0
- B. 1
- C. 2
- D. 3
Answer: C
Explanation:
An IPv6 address, defined in RFC 4291, is a 128-bit address designed to replace IPv4's 32-bit scheme, vastly expanding address space (2^128 vs. 2^32). An octet is 8 bits (1 byte). To calculate octets in IPv6:
128 bits ÷ 8 bits/octet = 16 octets.
Representation:
IPv6 is written as eight 16-bit hexadecimal blocks (e.g., 2001:0db8:85a3:0000:0000:8a2e:0370:7334), separated by colons.
Each block is 16 bits (2 bytes), so 8 blocks = 16 octets.
Contrast with IPv4 (e.g., 192.168.0.1), which has 4 octets (32 bits).
Technical Note: Your original input flagged this question's phrasing as potentially misleading, suggesting "octets" is an IPv4 term, while IPv6 uses "16-bit groups" or "hextets." While technically accurate (RFC 4291 uses "16-bit blocks"), "octets" remains a common, if informal, term in security contexts for byte-wise analysis (e.g., packet crafting). CNSP might use "octets" to test byte-level understanding, though "groups" is more precise for IPv6. Here, 16 octets (128 bits) is correct either way.
Security Implications: IPv6's larger address space complicates scanning (e.g., Nmap struggles with 2^128 possibilities) but introduces risks like misconfigured Neighbor Discovery Protocol (NDP). Understanding its structure aids in firewall rules and IDS signatures.
Why other options are incorrect:
B . 32: Implies 256 bits (32 × 8), far exceeding IPv6's 128-bit design.
C . 64: Suggests 512 bits (64 × 8), unrelated to IPv6 or any IP standard.
D . 128: Misinterprets octets as bits; 128 bits = 16 octets, not 128 octets.
Real-World Context: IPv6 packet analysis (e.g., Wireshark) breaks addresses into 16 octets for raw data inspection.
NEW QUESTION # 53
Which of the following is a valid DNS record type?
- A. SRV record
- B. NAPTR record
- C. All of the above
- D. TXT record
Answer: C
Explanation:
DNS (Domain Name System) records define how domain names are mapped to various types of data, each serving a specific purpose in network operations. The question asks for valid DNS record types, and all listed options are recognized.
Why D is correct:
A . NAPTR record: The Naming Authority Pointer (NAPTR) record is used for service discovery and mapping domain names to services, protocols, and ports (e.g., in SIP or ENUM systems).
B . SRV record: The Service (SRV) record specifies the hostname and port for specific services (e.g., LDAP, XMPP), aiding in service location.
C . TXT record: The Text (TXT) record stores arbitrary text data, often for SPF, DKIM, or domain verification.
All are valid DNS record types per RFC standards and CNSP documentation, making "All of the above" the correct answer.
Why other options are incomplete: A, B, or C alone exclude other valid types listed, so D is the most comprehensive response.
NEW QUESTION # 54
Which of the following services do not encrypt its traffic by default?
- A. SSH
- B. DNS
- C. All of these
- D. FTPS
Answer: B
Explanation:
Encryption ensures confidentiality and integrity of network traffic. Analyzing defaults:
A . DNS (Domain Name System):
Default: Unencrypted (UDP/TCP 53), per RFC 1035. Queries/responses (e.g., "google.com → 142.250.190.14") are plaintext.
Modern Options: DNS over HTTPS (DoH, TCP 443) or DNS over TLS (DoT, TCP 853) encrypt, but aren't default in most systems (e.g., pre-2020 Windows).
B . SSH (Secure Shell):
Default: Encrypted (TCP 22), per RFC 4251. Uses asymmetric (e.g., RSA) and symmetric (e.g., AES) crypto for all sessions.
C . FTPS (FTP Secure):
Default: Encrypted (TCP 21 control, dynamic data ports). Extends FTP with SSL/TLS (e.g., RFC 4217), securing file transfers.
Technical Details:
DNS: Plaintext exposes queries to eavesdropping (e.g., ISP snooping) or spoofing (e.g., cache poisoning).
SSH/FTPS: Encryption is baked into their standards; disabling it requires explicit misconfiguration.
Security Implications: Unencrypted DNS risks privacy and integrity (e.g., Kaminsky attack). CNSP likely pushes DoH/DoT adoption.
Why other options are incorrect:
B, C: Encrypt by default.
D: False, as only DNS lacks default encryption.
Real-World Context: The 2013 Snowden leaks exposed DNS monitoring; DoH uptake (e.g., Cloudflare 1.1.1.1) counters this.
NEW QUESTION # 55
What is the response from an open TCP port which is not behind a firewall?
- A. A SYN packet
- B. A RST and an ACK packet
- C. A SYN and an ACK packet
- D. A FIN and an ACK packet
Answer: C
Explanation:
TCP's three-way handshake, per RFC 793, establishes a connection:
Client → Server: SYN (Synchronize) packet (e.g., port 80).
Server → Client: SYN-ACK (Synchronize-Acknowledge) packet if the port is open and listening.
Client → Server: ACK (Acknowledge) completes the connection.
Scenario: An open TCP port (e.g., 80 for HTTP) with no firewall. When a client sends a SYN to an open port (e.g., via telnet 192.168.1.1 80), the server responds with a SYN-ACK packet, indicating willingness to connect. No firewall means no filtering alters this standard response.
Packet Details:
SYN-ACK: Sets SYN and ACK flags in the TCP header, with a sequence number and acknowledgment number.
Example: Client SYN (Seq=100), Server SYN-ACK (Seq=200, Ack=101).
Security Implications: Open ports responding with SYN-ACK are easily detected (e.g., Nmap "open" state), inviting exploits if unneeded (e.g., Telnet on 23). CNSP likely stresses port minimization and monitoring.
Why other options are incorrect:
A . A FIN and an ACK packet: FIN-ACK closes an established connection, not a response to a new SYN.
B . A SYN packet: SYN initiates a connection from the client, not a server response.
D . A RST and an ACK packet: RST-ACK rejects a connection (e.g., closed port), not an open one.
Real-World Context: SYN-ACK from SSH (22/TCP) confirms a server's presence during reconnaissance.
NEW QUESTION # 56
......
Correct and Up-to-date The SecOps Group CNSP BrainDumps: https://exampdf.dumpsactual.com/CNSP-actualtests-dumps.html
