<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://cmmcwiki.org/index.php?action=history&amp;feed=atom&amp;title=LLMResponse_MA.L2-3.7.1.a</id>
	<title>LLMResponse MA.L2-3.7.1.a - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://cmmcwiki.org/index.php?action=history&amp;feed=atom&amp;title=LLMResponse_MA.L2-3.7.1.a"/>
	<link rel="alternate" type="text/html" href="https://cmmcwiki.org/index.php?title=LLMResponse_MA.L2-3.7.1.a&amp;action=history"/>
	<updated>2026-04-20T07:11:41Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.8</generator>
	<entry>
		<id>https://cmmcwiki.org/index.php?title=LLMResponse_MA.L2-3.7.1.a&amp;diff=1365&amp;oldid=prev</id>
		<title>David: Created page with &quot;I&#039;ll help you prioritize your assessment approaches and evidence types for the MA.L2-3.7.1 requirement. Based on the CMMC Level 2 Assessment Guide and the specifics of this security practice, here&#039;s my recommendation:  == Assessment Approaches Priority ==  1. **Examine** - This should be your first approach because system maintenance documentation provides foundational evidence of your maintenance program. Examining maintenance records, policies, and schedules will show...&quot;</title>
		<link rel="alternate" type="text/html" href="https://cmmcwiki.org/index.php?title=LLMResponse_MA.L2-3.7.1.a&amp;diff=1365&amp;oldid=prev"/>
		<updated>2025-04-02T02:52:20Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;I&amp;#039;ll help you prioritize your assessment approaches and evidence types for the MA.L2-3.7.1 requirement. Based on the CMMC Level 2 Assessment Guide and the specifics of this security practice, here&amp;#039;s my recommendation:  == Assessment Approaches Priority ==  1. **Examine** - This should be your first approach because system maintenance documentation provides foundational evidence of your maintenance program. Examining maintenance records, policies, and schedules will show...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;I&amp;#039;ll help you prioritize your assessment approaches and evidence types for the MA.L2-3.7.1 requirement. Based on the CMMC Level 2 Assessment Guide and the specifics of this security practice, here&amp;#039;s my recommendation:&lt;br /&gt;
&lt;br /&gt;
== Assessment Approaches Priority ==&lt;br /&gt;
&lt;br /&gt;
1. **Examine** - This should be your first approach because system maintenance documentation provides foundational evidence of your maintenance program. Examining maintenance records, policies, and schedules will show that maintenance is performed systematically.&lt;br /&gt;
&lt;br /&gt;
2. **Interview** - After reviewing documentation, interviewing personnel responsible for system maintenance can confirm that documented procedures are understood and actually followed.&lt;br /&gt;
&lt;br /&gt;
3. **Test** - While valuable, testing should come after examining documentation and interviewing personnel. Testing can validate that maintenance processes are functioning as intended.&lt;br /&gt;
&lt;br /&gt;
== Evidence Types Ranking for Assessment Objective [a] ==&lt;br /&gt;
&lt;br /&gt;
1. **Artifacts** - These provide the strongest evidence that system maintenance is actually performed. Examples include:&lt;br /&gt;
   - Maintenance logs and records&lt;br /&gt;
   - Patch management reports&lt;br /&gt;
   - Ticket/change management system records showing completed maintenance&lt;br /&gt;
   - System update logs&lt;br /&gt;
&lt;br /&gt;
2. **Documents** - These provide the framework for your maintenance program:&lt;br /&gt;
   - System maintenance policy&lt;br /&gt;
   - Maintenance procedures&lt;br /&gt;
   - Vendor maintenance specifications&lt;br /&gt;
   - Maintenance schedules&lt;br /&gt;
   - System security plan sections addressing maintenance&lt;br /&gt;
&lt;br /&gt;
3. **Screen Share** - This can demonstrate:&lt;br /&gt;
   - Live patch management system showing maintenance history&lt;br /&gt;
   - Configuration management systems showing updates&lt;br /&gt;
   - Ticket system showing maintenance workflow&lt;br /&gt;
&lt;br /&gt;
4. **Physical Review** - While useful for hardware maintenance, this is less critical for the overall assessment:&lt;br /&gt;
   - Physical observation of hardware being maintained&lt;br /&gt;
   - Equipment maintenance logs maintained near the equipment&lt;br /&gt;
   - Review of maintenance areas and tools&lt;br /&gt;
&lt;br /&gt;
For this particular assessment objective, the primary focus should be on collecting artifacts that prove maintenance is actually performed, supported by documents that show you have a structured program in place. Screen shares and physical reviews can supplement your primary evidence.&lt;br /&gt;
&lt;br /&gt;
Would you like more specific examples of artifacts or documents you should collect for this requirement?&lt;/div&gt;</summary>
		<author><name>David</name></author>
	</entry>
</feed>