Examkin

Question

Difficulty: MediumHost, Network, and Architecture Vulnerabilities

Match each enterprise host or infrastructure security scenario to the underlying vulnerability or architectural weakness it represents.

  • An embedded storage controller accessible via Telnet and HTTP across the general user workstation VLAN.Cleartext Management & Insecure Protocols
  • A legacy enterprise server running an operating system that has reached End-of-Life (EOL) without extended security updates.Unsupported / Legacy System
  • A hypervisor management interface directly reachable from all non-administrative employee subnets.Improper Network Segmentation
  • A network switch deployed into production retaining factory-configured administrative login accounts.Default Configuration & Credentials

Answer

The scenarios match their respective security weaknesses as follows: Telnet and HTTP management maps to Cleartext Management & Insecure Protocols; End-of-Life OS maps to Unsupported / Legacy System; hypervisor interface accessible to user subnets maps to Improper Network Segmentation; and factory login accounts map to Default Configuration & Credentials.
Each scenario directly maps to its primary host and infrastructure vulnerability category: Telnet and HTTP communicate without transport encryption (Cleartext Management & Insecure Protocols); EOL systems lack vendor patch support (Unsupported / Legacy System); hypervisors accessible across general user subnets lack network isolation (Improper Network Segmentation); and factory administrative logins leave systems exposed to unauthorized access (Default Configuration & Credentials).

Step-by-Step Solution

1
Analyze each scenario's technical properties and security flaw.
Identify cleartext transport protocols (Telnet/HTTP), unpatched software lifecycle status (EOL), flat network exposure of host management, and unmanaged factory credentials.
Categorizing the specific technical failure allows mapping each host and infrastructure risk to standard security vulnerability categories.
2
Map the technical failures to their core host and infrastructure vulnerability classifications.
Connect cleartext management traffic to insecure protocols, EOL status to unsupported systems, unrestricted hypervisor routing to improper segmentation, and factory logins to default configurations.
Correlate host lifecycle, network access boundaries, and credential baselines against established enterprise security weakness classifications.

Key Concept

Host, Network, and Architecture Vulnerabilities
Rate this question

Topics

Host, Network, and Architecture Vulnerabilities