Secure Management and Remote Access
- Explain protecting administrative planes and remote connections
- Apply the idea to evidence from a realistic technology scenario
- Justify a decision using security, reliability, cost, and user impact
Secure Management and Remote Access
Management access deserves stronger controls than ordinary use: encrypted protocols, multifactor authentication, dedicated management networks, limited source addresses, named accounts, centralized logs, and prompt patching. Remote access should expose only what users need.
Decision lens
Strong technical decisions connect evidence → mechanism → impact → response. Identify what the evidence shows, explain the system behavior that produced it, state the likely effect on people or data, and choose a response that addresses the cause without creating unnecessary disruption.
A router accepts internet-facing Telnet connections using one shared administrator account.
- 1.Telnet exposes credentials and commands in clear text.
- 2.Internet exposure increases attack opportunity.
- 3.Use SSH or a managed secure channel through VPN or a bastion host.
- 4.Require named MFA-protected accounts and restrict management sources.
Why are named administrator accounts preferable to one shared account?
Which response best demonstrates complete reasoning about protecting administrative planes and remote connections?
For a scenario about protecting administrative planes and remote connections, identify the decisive evidence before naming a response. A defensible conclusion here is: Remove Telnet and shared credentials, restrict reachability, and log accountable encrypted administration.
Answer the 2 checkpoints as you read.
Sign in to save your progress