AC-17(9)—Disconnect Or Disable Access
>Control Description
Provide the capability to disconnect or disable remote access to the system within ⚙organization-defined time period.
>Cross-Framework Mappings
>Supplemental Guidance
The speed of system disconnect or disablement varies based on the criticality of missions or business functions and the need to eliminate immediate or future remote access to systems.
>Assessment Interview Topics
Questions assessors commonly ask
Process & Governance:
- •What formal policies and procedures govern the implementation of AC-17(9) (Disconnect Or Disable Access)?
- •Who are the designated roles responsible for implementing, maintaining, and monitoring AC-17(9)?
- •How frequently is the AC-17(9) policy reviewed and updated, and what triggers policy changes?
- •What training or awareness programs ensure personnel understand their responsibilities related to AC-17(9)?
Technical Implementation:
- •Describe the specific technical mechanisms or controls used to enforce AC-17(9) requirements.
- •What automated tools, systems, or technologies are deployed to implement AC-17(9)?
- •How is AC-17(9) integrated into your system architecture and overall security posture?
- •What configuration settings, parameters, or technical specifications enforce AC-17(9) requirements?
Evidence & Documentation:
- •What documentation demonstrates the complete implementation of AC-17(9)?
- •What audit logs, records, reports, or monitoring data validate AC-17(9) compliance?
- •Can you provide evidence of periodic reviews, assessments, or testing of AC-17(9) effectiveness?
- •What artifacts would you present during a FedRAMP assessment to demonstrate AC-17(9) compliance?
Ask AI
Configure your API key to use AI features.