inspect-control

To get requirement stats from a compliance control file, analyze the file to compute totals by status such as mapped, unmapped, manual, and not applicable, presenting a concise triage overview.

The best way to triage unmapped requirements across frameworks like ANSSI or HIPAA is to analyze the control file to list unmapped and partially mapped items, guiding prioritization and resource planning.

Control file inspection works by falling back to filesystem-based YAML parsing to compute totals and unmapped requirements when MCP tooling is unavailable, ensuring resilient triage reporting.

Yes, you can check cross-framework mapping status for SRG/GPOS policies by analyzing the control file to report mapping status and cross-framework context for triage before mapping.

No, inspect-control does not require external dependencies to compute control statistics, as it implements load-and-validate logic that falls back to YAML parsing when MCP tooling is unavailable.

You need to run a triage report on a control file during initial mapping sessions across policies, using the computed requirement stats and mapping status to guide prioritization and resource planning.