sands-mvcc/cmmc

This repository is a static CMMC audit-preparation dashboard: the entire application appears to be a set of linked HTML pages, with no visible backend, database, or build system in the repo snapshot.

1) Entry and navigation layer

index.html is the likely landing page, with dashboard.html and agenda.html acting as the main navigation hubs. The app is organized as a brochure-style site where users move between pages via hyperlinks rather than through an API-driven workflow.

2) Primary purpose: CMMC pre-audit preparation

The README states the project is for CMMC Audit Dashboard and PreAudit preparation. The page set reflects that goal: it collects assessment artifacts, control references, readiness material, and reporting views in one place.

3) Core assessment artifact subsystem

Several pages correspond to standard CMMC/NIST-style evidence and assessment outputs:

• SSP.html, SAR.html, POAM.html, VSR.html

• IRP.html, CMP.html, ALMR.html, ACM.html

• asset.html, maintenance.html, applicability.html

These likely form the operational heart of the dashboard, where audit evidence and compliance status are reviewed.

4) Tool-oriented pages for each artifact

The repository includes parallel “tool” pages such as SSP_tool.html, SAR_tool.html, POAM_tool.html, VSR_tool.html, IRP_tool.html, CMP_tool.html, ALMR_tool.html, ACM_tool.html, Asset_tool.html, Maintenance_tool.html.

This suggests each artifact has an associated working page or guided helper, likely used to create, review, or manage that artifact in a structured way.

5) Scenario/organization-specific content

Pages prefixed with Acme_ such as Acme_ACM.html, Acme_Asset_Inventory.html, and Acme_Maintenance.html imply example or client-specific instances of the same compliance content. This indicates the dashboard supports templated content or sample organizational data.

6) Reference and standards subsystem

Pages like cui.html, dfars.html, nist171.html, apt.html, accesscontroll1.html, and matrix_energy.html appear to provide compliance references, policy context, or control mappings. These pages likely support the evidence pages by explaining requirements and applicability.

7) Readiness and review subsystem

readiness.html, capabilities.html, evidence.html, reports.html, roles.html, and process.html look like higher-level oversight views. These are the pages a manager or assessor would use to understand readiness posture, responsibilities, evidence completeness, and reporting status.

8) Training, exercises, and narrative content

The many assignment*.html, casestudy*.html, casestudies.html, and casestudy.html pages suggest a training or instructional layer. These likely support walkthroughs, scenario-based learning, or audit-prep exercises rather than live operational data.

9) Domain-specific inventory and operational support

The asset and maintenance pages indicate the dashboard is not only about documents but also about operational control areas tied to CMMC evidence: asset inventory, lifecycle maintenance, and configuration-related activities.

10) Likely data flow in the site

A typical flow is: landing/dashboard → reference or readiness pages → specific control/artifact pages → tool pages for completion → reports/evidence views. The pages appear to be connected through manual navigation and embedded links, with the browser acting as the only runtime.

11) Architectural boundary

This repo is best diagrammed as a single static front-end content system rather than a multi-tier application. The meaningful boundaries are between:

• navigation/dashboard pages,

• compliance artifact pages,

• standards/reference content,

• training/case-study content,

• and report/readiness views.

12) Implementation implications

Because the repository is HTML-only in the tree, any dynamic behavior is likely minimal or embedded directly in the pages. The architecture is therefore centered on content organization and cross-page navigation, not services, persistence, or server-side orchestration.