nerdexam
CompTIA

CAS-003 · Question #545

During a routine network scan, a security administrator discovered an unidentified service running on a new embedded and unmanaged HVAC controller, which is used to monitor the company's datacenter…

The correct answer is D. Implement SNMPv3 to secure communication. An unmanaged embedded HVAC controller running SNMP should be hardened by upgrading to SNMPv3, which replaces the insecure community string model with authenticated and encrypted communication.

Technical Integration of Enterprise Security

Question

During a routine network scan, a security administrator discovered an unidentified service running on a new embedded and unmanaged HVAC controller, which is used to monitor the company's datacenter Port state 161/UDP open 162/UDP open 163/TCP open The enterprise monitoring service requires SNMP and SNMPTRAP connectivity to operate. Which of the following should the security administrator implement to harden the system?

Options

  • APatch and restart the unknown services.
  • BSegment and firewall the controller's network
  • CDisable the unidentified service on the controller.
  • DImplement SNMPv3 to secure communication.
  • EDisable TCP/UDP PORTS 161 THROUGH 163

How the community answered

(26 responses)
  • A
    12% (3)
  • C
    4% (1)
  • D
    77% (20)
  • E
    8% (2)

Why each option

An unmanaged embedded HVAC controller running SNMP should be hardened by upgrading to SNMPv3, which replaces the insecure community string model with authenticated and encrypted communication.

APatch and restart the unknown services.

Embedded HVAC controllers are typically unmanaged and cannot be patched like standard servers, and restarting services does not address the inherent insecurity of older SNMP protocol versions.

BSegment and firewall the controller's network

Network segmentation is a valid defense-in-depth layer but does not secure the unencrypted SNMP protocol itself or eliminate the risk of credential interception on the segment.

CDisable the unidentified service on the controller.

Disabling the unidentified service on port 163/TCP is advisable but insufficient on its own, as it leaves the insecure SNMPv1/v2c communication on required ports 161 and 162 unaddressed.

DImplement SNMPv3 to secure communication.Correct

SNMPv3 introduces the User-based Security Model (USM) for authentication and the View-based Access Control Model (VACM) for authorization, replacing the cleartext community strings used by SNMPv1 and SNMPv2c. Since the enterprise monitoring service requires SNMP on port 161 and SNMPTRAP on port 162, those ports cannot be disabled, making protocol-level hardening the appropriate remediation. Implementing SNMPv3 secures the required monitoring communication without disrupting operational functionality.

EDisable TCP/UDP PORTS 161 THROUGH 163

Disabling ports 161 through 163 would break the required SNMP and SNMPTRAP connectivity that the enterprise monitoring service depends on, making this counterproductive to the stated operational requirement.

Concept tested: Hardening embedded SNMP devices by upgrading to SNMPv3

Source: https://datatracker.ietf.org/doc/html/rfc3414

Topics

#SNMPv3#IoT security#OT/ICS security#network segmentation

Community Discussion

No community discussion yet for this question.

Full CAS-003 Practice