| Control Domain |
Control |
Name |
MetadataId |
Category |
Title |
Owner |
Requirements |
Description |
Info |
Policy# |
| FedRAMP_High_R4 |
AC-17(4) |
FedRAMP_High_R4_AC-17(4) |
FedRAMP High AC-17 (4) |
Access Control |
Privileged Commands / Access |
Shared |
n/a |
The organization:
(a) Authorizes the execution of privileged commands and access to security-relevant information via remote access only for [Assignment: organization-defined needs]; and
(b) Documents the rationale for such access in the security plan for the information system.
Supplemental Guidance: Related control: AC-6. |
link |
5 |
| FedRAMP_Moderate_R4 |
AC-17(4) |
FedRAMP_Moderate_R4_AC-17(4) |
FedRAMP Moderate AC-17 (4) |
Access Control |
Privileged Commands / Access |
Shared |
n/a |
The organization:
(a) Authorizes the execution of privileged commands and access to security-relevant information via remote access only for [Assignment: organization-defined needs]; and
(b) Documents the rationale for such access in the security plan for the information system.
Supplemental Guidance: Related control: AC-6. |
link |
5 |
| hipaa |
0902.09s2Organizational.13-09.s |
hipaa-0902.09s2Organizational.13-09.s |
0902.09s2Organizational.13-09.s |
09 Transmission Protection |
0902.09s2Organizational.13-09.s 09.08 Exchange of Information |
Shared |
n/a |
Remote (external) access to the organization's information assets and access to external information assets (for which the organization has no control) is based on clearly defined terms and conditions. |
|
14 |
| NIST_SP_800-171_R2_3 |
.1.15 |
NIST_SP_800-171_R2_3.1.15 |
NIST SP 800-171 R2 3.1.15 |
Access Control |
Authorize remote execution of privileged commands and remote access to security-relevant information. |
Shared |
Microsoft and the customer share responsibilities for implementing this requirement. |
A privileged command is a human-initiated (interactively or via a process operating on behalf of the human) command executed on a system involving the control, monitoring, or administration of the system including security functions and associated security-relevant information. Security-relevant information is any information within the system that can potentially impact the operation of security functions or the provision of security services in a manner that could result in failure to enforce the system security policy or maintain isolation of code and data. Privileged commands give individuals the ability to execute sensitive, security-critical, or security-relevant system functions. Controlling such access from remote locations helps to ensure that unauthorized individuals are not able to execute such commands freely with the potential to do serious or catastrophic damage to organizational systems. Note that the ability to affect the integrity of the system is considered security-relevant as that could enable the means to by-pass security functions although not directly impacting the function itself. |
link |
5 |
| NIST_SP_800-53_R4 |
AC-17(4) |
NIST_SP_800-53_R4_AC-17(4) |
NIST SP 800-53 Rev. 4 AC-17 (4) |
Access Control |
Privileged Commands / Access |
Shared |
n/a |
The organization:
(a) Authorizes the execution of privileged commands and access to security-relevant information via remote access only for [Assignment: organization-defined needs]; and
(b) Documents the rationale for such access in the security plan for the information system.
Supplemental Guidance: Related control: AC-6. |
link |
5 |
| NIST_SP_800-53_R5 |
AC-17(4) |
NIST_SP_800-53_R5_AC-17(4) |
NIST SP 800-53 Rev. 5 AC-17 (4) |
Access Control |
Privileged Commands and Access |
Shared |
n/a |
(a) Authorize the execution of privileged commands and access to security-relevant information via remote access only in a format that provides assessable evidence and for the following needs: [Assignment: organization-defined needs]; and
(b) Document the rationale for remote access in the security plan for the system. |
link |
5 |