research
CommandStart or resume an academic research project — idea through literature, methodology, writing, feedback, and publishing
Deep dive guidance on CMMC v2.0 domains and practices
> /plugin marketplace add GRCEngClub/claude-grc-engineering
description: Deep dive guidance on CMMC v2.0 domains and practices
> **Review required:** This material is an unverified working aid, not an authoritative assessment or legal determination. Verify every control, objective, scope, assessment type, scoring and contractual claim against current official sources and obtain qualified CMMC and contracting review before use. If a source or contract is unavailable, mark the conclusion unverified; do not infer compliance.
Provides detailed implementation guidance for CMMC v2.0 domains and their associated practices.
See the [DoD CMMC Model Overview v2.13](https://dodcio.defense.gov/Portals/0/Documents/CMMC/ModelOverviewv2.pdf) for Levels 1–3 and [32 CFR 170.14](https://www.ecfr.gov/current/title-32/section-170.14) for regulatory requirements. Level 1 identifiers map to NIST assessment objectives as specified in [32 CFR 170.15(c)(1)(ii)](https://www.ecfr.gov/current/title-32/section-170.15).
Controls who can access systems and data based on approved authorizations.
**Key practices**:
Maintains audit logs to detect and respond to cyber incidents.
**Key practices**:
Ensures personnel are trained in cybersecurity.
**Key practices**:
Establishes and maintains baseline configurations.
**Key practices**:
Verifies identities of users and devices.
**Key practices**:
Detects and responds to cybersecurity incidents.
**Key practices**:
Manages system maintenance and repair.
**Key practices**:
Protects digital and non-digital media.
**Key practices**:
Screens and monitors personnel.
**Key practices**:
Limits physical access to systems and facilities.
**Key practices**:
Manages organizational risk to operations and assets.
**Key practices**:
Develops and implements activities to assess security effectiveness.
**Key practices**:
Monitors and controls communications at system boundaries.
**Key practices**:
Identifies and manages information system flaws.
**Key practices**:
1. **Domain Overview**: Purpose and objectives 2. **Practice List**: All practices in domain by level 3. **Implementation Guidance**: How to satisfy each practice 4. **Common Gaps**: Typical deficiencies found 5. **Evidence Requirements**: What C3PAOs look for 6. **NIST Mapping**: Correlation to NIST 800-171
# Get guidance for Access Control domain /cmmc:domain-guidance AC # See Level 2 practices for Incident Response /cmmc:domain-guidance IR 2 # Review Audit and Accountability requirements /cmmc:domain-guidance AU
Open-source GRC Engineering resource for Claude. claude-grc-engineering turns technical evidence from cloud, SaaS, code, and security tools into framework-aligned findings, gap reports, remediation guidance, evidence packages, and OSCAL workflows.
Start or resume an academic research project — idea through literature, methodology, writing, feedback, and publishing
Query AWS for compliance-relevant configuration across IAM, S3, CloudTrail, EBS, and emit findings conforming to the v1 contract.
Install the frdocx-to-froscal-ssp Python pipeline and verify its dependencies. Idempotent.
Retrieve a single AWS Secrets Manager secret value to stdout or a 0600-permission file. Opt-in retrieval mode — never writes to…
Run testssl.sh against one or more HTTPS endpoints and emit v1 Findings mapped to SOC 2, NIST 800-53, PCI DSS 4.0.1, ISO 27001,…
Audit a file, directory, or whole repo for insecure default configuration: fallback secrets, default credentials, fail-open…
Check text against AGT prompt-injection, context-poisoning, and MCP threat detectors.
Show which external bug-bounty tools are installed on this machine and print install hints for the missing ones. Curated from…