AC-20(3)—Use of External Systems | Non-organizationally Owned Systems -- Restricted Use
>Control Description
>DoD Impact Level Requirements
No specific parameter values or requirements for this impact level.
>Discussion
Non-organizationally owned systems or system components include systems or system components owned by other organizations as well as personally owned devices. There are potential risks to using non-organizationally owned systems or components. In some cases, the risk is sufficiently high as to prohibit such use (see AC-20 b.).
In other cases, the use of such systems or system components may be allowed but restricted in some way. Restrictions include requiring the implementation of approved controls prior to authorizing the connection of non-organizationally owned systems and components; limiting access to types of information, services, or applications; using virtualization techniques to limit processing and storage activities to servers or system components provisioned by the organization; and agreeing to the terms and conditions for usage. Organizations consult with the Office of the General Counsel regarding legal issues associated with using personally owned devices, including requirements for conducting forensic analyses during investigations after an incident.
>Assessment Interview Topics
Questions assessors commonly ask
Process & Governance:
- •What formal policies and procedures govern the implementation of AC-20(3) (Non-Organizationally Owned Systems -- Restricted Use)?
- •Who are the designated roles responsible for implementing, maintaining, and monitoring AC-20(3)?
- •How frequently is the AC-20(3) policy reviewed and updated, and what triggers policy changes?
- •What training or awareness programs ensure personnel understand their responsibilities related to AC-20(3)?
Technical Implementation:
- •Describe the specific technical mechanisms or controls used to enforce AC-20(3) requirements.
- •What automated tools, systems, or technologies are deployed to implement AC-20(3)?
- •How is AC-20(3) integrated into your system architecture and overall security posture?
- •What configuration settings, parameters, or technical specifications enforce AC-20(3) requirements?
Evidence & Documentation:
- •What documentation demonstrates the complete implementation of AC-20(3)?
- •What audit logs, records, reports, or monitoring data validate AC-20(3) compliance?
- •Can you provide evidence of periodic reviews, assessments, or testing of AC-20(3) effectiveness?
- •What artifacts would you present during a FedRAMP assessment to demonstrate AC-20(3) compliance?
Ask AI
Configure your API key to use AI features.