Authenticate Remote Commands
LOW MODERATE HIGHRequirements NIST SOURCE
Implement [mechanisms] to authenticate [remote commands].
Discussion (NIST Supplemental Guidance)
Authenticating remote commands protects against unauthorized commands and the replay of authorized commands. The ability to authenticate remote commands is important for remote systems for which loss, malfunction, misdirection, or exploitation would have immediate or serious consequences, such as injury, death, property damage, loss of high value assets, failure of mission or business functions, or compromise of classified or controlled unclassified information. Authentication mechanisms for remote commands ensure that systems accept and execute commands in the order intended, execute only authorized commands, and reject unauthorized commands. Cryptographic mechanisms can be used, for example, to authenticate remote commands.
Implementation Guidance
Original engineering commentary written for this explorer — not NIST source text and not authoritative guidance.
No engineering interpretation has been authored for AC-17(10) yet. This section is architected to receive it — see the Requirements and Assessment sections above for the authoritative NIST source content in the meantime.
Assessment
Assessment Objectives
- mechanisms implemented to authenticate remote commands are defined;
- remote commands to be authenticated by mechanisms are defined;
- <AC-17(10)_ODP[01] mechanisms> are implemented to authenticate <AC-17(10)_ODP[02] remote commands>.
Examine
[SELECT FROM: Access control policy; procedures addressing authentication of remote commands; system design documentation; system configuration settings and associated documentation; system audit records; system security plan; other relevant documents or records].
Interview
[SELECT FROM: System/network administrators; organizational personnel with information security responsibilities; system developers].
Test
[SELECT FROM: Mechanisms implementing authentication of remote commands].
Overlays
STIGs & CCIs
No STIG checks or CCI mappings are currently loaded for AC-17(10). This section is architected to display, per product: STIG ID, Finding ID, Severity, Title, Description, Check, Fix, CCI, and NIST control mapping — but nothing is populated here until a real DISA STIG/CCI dataset is ingested.
Learn more about STIG/CCI integration →Evidence
Categorized from the SP 800-53A "Examine"/"Test" artifact list above by keyword — not an authoritative NIST evidence list.
Policy
- Access control policy
- system security plan
Configuration
- system design documentation
- system configuration settings and associated documentation
Testing
- Mechanisms implementing authentication of remote commands
Other Records
- procedures addressing authentication of remote commands
- system audit records
- other relevant documents or records