MA-3(1)—Inspect Tools
MODERATE
HIGH
>Control Description
Inspect the maintenance tools used by maintenance personnel for improper or unauthorized modifications.
>Cross-Framework Mappings
>Programmatic Queries
Beta
Related Services
AWS Config
AWS Systems Manager
AWS Trusted Advisor
CLI Commands
Create Config rule to inspect maintenance tools
aws configservice put-config-rule --config-rule file://maintenance-tools-rule.jsonGet Config compliance for maintenance tool inspection
aws configservice describe-compliance-by-config-rule --compliance-types NON_COMPLIANTCreate inventory of maintenance tools
aws ssm create-inventory --instance-id i-1234567890abcdef0 --type-name AWS:Application --instance-association-output-location S3Location=s3://bucket/inventoryRun Trusted Advisor check for security tools
aws support describe-trusted-advisor-checks --language en>Supplemental Guidance
Maintenance tools can be directly brought into a facility by maintenance personnel or downloaded from a vendor's website. If, upon inspection of the maintenance tools, organizations determine that the tools have been modified in an improper manner or the tools contain malicious code, the incident is handled consistent with organizational policies and procedures for incident handling.
>Related Controls
>Assessment Interview Topics
Questions assessors commonly ask
Process & Governance:
- •What formal policies and procedures govern the implementation of MA-3(1) (Inspect Tools)?
- •Who are the designated roles responsible for implementing, maintaining, and monitoring MA-3(1)?
- •How frequently is the MA-3(1) policy reviewed and updated, and what triggers policy changes?
- •What governance structure ensures MA-3(1) requirements are consistently applied across all systems?
Technical Implementation:
- •Describe the specific technical mechanisms or controls used to enforce MA-3(1) requirements.
- •What automated tools, systems, or technologies are deployed to implement MA-3(1)?
- •How is MA-3(1) integrated into your system architecture and overall security posture?
- •What configuration settings, parameters, or technical specifications enforce MA-3(1) requirements?
Evidence & Documentation:
- •What documentation demonstrates the complete implementation of MA-3(1)?
- •What audit logs, records, reports, or monitoring data validate MA-3(1) compliance?
- •Can you provide evidence of periodic reviews, assessments, or testing of MA-3(1) effectiveness?
- •What artifacts would you present during a FedRAMP assessment to demonstrate MA-3(1) compliance?
Ask AI
Configure your API key to use AI features.