MA-3(3)—Maintenance Tools | Prevent Unauthorized Removal
IL4 Mod
IL4 High
IL5
IL6
>Control Description
Prevent the removal of maintenance equipment containing organizational information by:
(a) Verifying that there is no organizational information contained on the equipment;
(b) Sanitizing or destroying the equipment;
(c) Retaining the equipment within the facility; or
(d) Obtaining an exemption from ⚙organization-defined personnel or roles explicitly authorizing removal of the equipment from the facility.
>DoD Impact Level Requirements
FedRAMP Parameter Values
MA-3 (3) (d) [the information owner]
>Discussion
Organizational information includes all information owned by organizations and any information provided to organizations for which the organizations serve as information stewards.
>Programmatic Queries
Beta
Related Services
AWS Systems Manager
AWS Config
AWS CloudTrail
CLI Commands
Create Config rule to prevent tool removal
aws configservice put-config-rule --config-rule file://prevent-tool-removal.jsonTag maintenance tools for resource control
aws ec2 create-tags --resources i-1234567890abcdef0 --tags Key=maintenance-tool,Value=protectedCreate IAM policy to prevent tool removal
aws iam put-user-policy --user-name ec2-user --policy-name prevent-tool-removal --policy-document file://prevent-removal-policy.jsonEnable CloudTrail logging for tool operations
aws cloudtrail create-trail --name maintenance-tool-trail --s3-bucket-name cloudtrail-bucket --is-multi-region-trail>Related Controls
>Assessment Interview Topics
Questions assessors commonly ask
Process & Governance:
- •What formal policies and procedures govern the implementation of MA-3(3) (Prevent Unauthorized Removal)?
- •Who are the designated roles responsible for implementing, maintaining, and monitoring MA-3(3)?
- •How frequently is the MA-3(3) policy reviewed and updated, and what triggers policy changes?
- •What governance structure ensures MA-3(3) requirements are consistently applied across all systems?
Technical Implementation:
- •Describe the specific technical mechanisms or controls used to enforce MA-3(3) requirements.
- •What automated tools, systems, or technologies are deployed to implement MA-3(3)?
- •How is MA-3(3) integrated into your system architecture and overall security posture?
- •What configuration settings, parameters, or technical specifications enforce MA-3(3) requirements?
Evidence & Documentation:
- •What documentation demonstrates the complete implementation of MA-3(3)?
- •What audit logs, records, reports, or monitoring data validate MA-3(3) compliance?
- •Can you provide evidence of periodic reviews, assessments, or testing of MA-3(3) effectiveness?
- •What artifacts would you present during a FedRAMP assessment to demonstrate MA-3(3) compliance?
Ask AI
Configure your API key to use AI features.