|
| 1 | +Running CMMC Level 1 (17 practices) - Open Source |
| 2 | + |
| 3 | +⚠️ IMPORTANT DISCLAIMER: |
| 4 | +═══════════════════════════════════════════════════════════ |
| 5 | +This scanner tests technical controls that can be automated. |
| 6 | + |
| 7 | +CMMC Level 1 requires 17 practices. Many controls require |
| 8 | +organizational documentation and policies that cannot be |
| 9 | +verified through automated scanning. |
| 10 | + |
| 11 | +A high automated check score does NOT mean you are CMMC |
| 12 | +compliant. This is a technical assessment tool, not a |
| 13 | +compliance certification. |
| 14 | + |
| 15 | +You still need to document policies, training, incident |
| 16 | +response procedures, and other organizational controls. |
| 17 | +═══════════════════════════════════════════════════════════ |
| 18 | + |
| 19 | + |
| 20 | +CMMC Level 1 scan complete: 17 controls tested |
| 21 | + |
| 22 | +🔓 UNLOCK CMMC LEVEL 2: |
| 23 | + • 110 additional Level 2 practices for CUI |
| 24 | + • Required for DoD contractors handling CUI |
| 25 | + • Complete evidence collection guides |
| 26 | + • November 10, 2025 deadline compliance |
| 27 | + |
| 28 | +Visit https://auditkit.io/pro for full CMMC Level 2 |
| 29 | + |
| 30 | +Automated Check Score: 57.1% (4/7 passed) |
| 31 | + |
| 32 | +⚠️ IMPORTANT: Only 7 of 17 total controls are automated. |
| 33 | + 10 controls require manual documentation and evidence. |
| 34 | + Use 'auditkit evidence' to track what you need to collect. |
| 35 | + |
| 36 | +AuditKit CMMC Compliance Scan Results |
| 37 | +===================================== |
| 38 | +AWS Account: 1234567890 |
| 39 | +Framework: CMMC |
| 40 | +Scan Time: 2025-10-11 18:52:15 |
| 41 | + |
| 42 | +Compliance Score: [31m57.1%[0m |
| 43 | +Controls Passed: 4/17 |
| 44 | + |
| 45 | +Other Issues: |
| 46 | +================ |
| 47 | +[FAIL] AC.L1-3.1.2 - Security Control |
| 48 | + Issue: No custom IAM policies - relying on AWS managed policies only |
| 49 | + Fix: Create custom IAM policies to restrict access appropriately |
| 50 | + |
| 51 | +[FAIL] IA.L1-3.5.2 - Security Control |
| 52 | + Issue: Only 0/2 users have MFA enabled |
| 53 | + Fix: Enable MFA for all IAM users |
| 54 | + |
| 55 | +[FAIL] SC.L1-3.13.1 - Security Control |
| 56 | + Issue: 1 security groups allow unrestricted access: sg-0ab56571076bcff37 |
| 57 | + Fix: Restrict security group rules to specific IP ranges |
| 58 | + |
| 59 | +Manual Documentation Required: |
| 60 | +================================= |
| 61 | +[INFO] MP.L1-3.8.3 - Security Control |
| 62 | + Guidance: MANUAL: Document media sanitization procedures for EBS volumes and S3 objects |
| 63 | + Evidence: Documentation → Screenshot showing media sanitization procedures | AWS Console → S3 → Lifecycle rules |
| 64 | + |
| 65 | +[INFO] PE.L1-3.10.1 - Security Control |
| 66 | + Guidance: MANUAL: AWS data centers have physical controls (inherited control) |
| 67 | + Evidence: AWS Artifact → Screenshot SOC 2 report showing physical controls |
| 68 | + |
| 69 | +[INFO] PE.L1-3.10.3 - Security Control |
| 70 | + Guidance: MANUAL: AWS data centers escort visitors (inherited control) |
| 71 | + Evidence: AWS Artifact → Screenshot showing visitor management procedures |
| 72 | + |
| 73 | +[INFO] PE.L1-3.10.4 - Security Control |
| 74 | + Guidance: MANUAL: AWS maintains physical access logs (inherited control) |
| 75 | + Evidence: AWS Artifact → Screenshot showing physical access logging |
| 76 | + |
| 77 | +[INFO] PE.L1-3.10.5 - Security Control |
| 78 | + Guidance: MANUAL: AWS controls physical access devices (inherited control) |
| 79 | + Evidence: AWS Artifact → Screenshot showing physical access device management |
| 80 | + |
| 81 | +[INFO] PS.L1-3.9.1 - Security Control |
| 82 | + Guidance: MANUAL: Document personnel screening procedures for CUI access |
| 83 | + Evidence: HR Documentation → Screenshot showing personnel screening procedures and background check records |
| 84 | + |
| 85 | +[INFO] PS.L1-3.9.2 - Security Control |
| 86 | + Guidance: MANUAL: Document authorization process for CUI access |
| 87 | + Evidence: Documentation → Screenshot showing CUI access authorization procedures and approval records |
| 88 | + |
| 89 | +[INFO] SI.L1-3.14.1 - Security Control |
| 90 | + Guidance: MANUAL: Document flaw identification and remediation processes |
| 91 | + Evidence: AWS Console → Systems Manager → Patch Manager → Screenshot compliance dashboard |
| 92 | + |
| 93 | +[INFO] SI.L1-3.14.2 - Security Control |
| 94 | + Guidance: MANUAL: Document malicious code protection mechanisms |
| 95 | + Evidence: AWS Console → GuardDuty → Screenshot showing malware detection enabled |
| 96 | + |
| 97 | +[INFO] SI.L1-3.14.4 - Security Control |
| 98 | + Guidance: MANUAL: Document malicious code protection update procedures |
| 99 | + Evidence: AWS Console → GuardDuty → Settings → Screenshot showing automatic updates enabled |
| 100 | + |
| 101 | +[32mPassed Controls:[0m |
| 102 | +=================== |
| 103 | + - AC.L1-3.1.1 - Security Control |
| 104 | + - IA.L1-3.5.1 - Security Control |
| 105 | + - SC.L1-3.13.16 - Security Control |
| 106 | + - SC.L1-3.13.11 - Security Control |
| 107 | + |
| 108 | +Priority Action Items: |
| 109 | +========================= |
| 110 | + 1. Enable continuous compliance monitoring |
| 111 | + 2. Document your security policies and procedures |
| 112 | + 3. Set up automated alerting for security events |
| 113 | + 4. Schedule quarterly access reviews |
| 114 | + |
| 115 | +For detailed CMMC report with full evidence checklist: |
| 116 | + auditkit scan -provider aws -framework cmmc -format pdf -output report.pdf |
| 117 | + |
| 118 | +To track evidence collection progress: |
| 119 | + auditkit evidence -provider aws |
| 120 | + |
0 commit comments