MA-3(2)—Maintenance Tools | Inspect Media

IL4 Mod

IL4 High

IL5

IL6

>Control Description

Check media containing diagnostic and test programs for malicious code before the media are used in the system.

>DoD Impact Level Requirements

No specific parameter values or requirements for this impact level.

>Discussion

If, upon inspection of media containing maintenance, diagnostic, and test programs, organizations determine that the media contains malicious code, the incident is handled consistent with organizational incident handling policies and procedures.

>Programmatic Queries

Beta

Related Services

AWS EC2

AWS Systems Manager

AWS EBS

CLI Commands

Create EBS snapshot for media inspection

aws ec2 create-snapshot --volume-id vol-1234567890abcdef0 --description 'Media inspection snapshot'

List volumes for media inspection

aws ec2 describe-volumes --filters Name=status,Values=in-use --query 'Volumes[].VolumeId' --output text

Create Systems Manager document for media scan

aws ssm create-document --content file://media-inspection.json --name media-inspect-doc --document-type Command

Run media inspection on instances

aws ssm send-command --document-name 'media-inspect-doc' --instance-ids 'i-1234567890abcdef0' --output-s3-bucket-name s3://inspection-results

Open AWS Console Documentation

>Related Controls

SI-3

>Assessment Interview Topics

Questions assessors commonly ask

Process & Governance:

•What formal policies and procedures govern the implementation of MA-3(2) (Inspect Media)?
•Who are the designated roles responsible for implementing, maintaining, and monitoring MA-3(2)?
•How frequently is the MA-3(2) policy reviewed and updated, and what triggers policy changes?
•What governance structure ensures MA-3(2) requirements are consistently applied across all systems?

Technical Implementation:

•Describe the specific technical mechanisms or controls used to enforce MA-3(2) requirements.
•What automated tools, systems, or technologies are deployed to implement MA-3(2)?
•How is MA-3(2) integrated into your system architecture and overall security posture?
•What configuration settings, parameters, or technical specifications enforce MA-3(2) requirements?

Evidence & Documentation:

•What documentation demonstrates the complete implementation of MA-3(2)?
•What audit logs, records, reports, or monitoring data validate MA-3(2) compliance?
•Can you provide evidence of periodic reviews, assessments, or testing of MA-3(2) effectiveness?
•What artifacts would you present during a FedRAMP assessment to demonstrate MA-3(2) compliance?

Ask AI

Configure your API key to use AI features.