azurenoops / azurenoops/spin_agent

[WM-BW-9] Control inheritance sub-page blank — no workflow to document Common Control Provider inheritance

Open
#677 1 comment 0 reactions 1 assignee Claimed by @jrspinella View on GitHub
agent:war-machine broken-workflow-ATO/RMF bug priority:medium
Dominant language
C#
Stars
3
Forks
1
Avg merge
18h 9m
Merged PRs (30d)
43

Description

## WM-BW-9 — Control Inheritance Sub-page Blank; SP 800-37 Task I-2 Not Supported

**Category:** Broken ATO/RMF Workflow | **Priority:** Medium
**Regulation:** SP 800-37 Task I-2

### Observation
The control inheritance sub-page renders blank. There is no workflow to document or formally accept Common Control Provider (CCP) inheritance. SP 800-37 Task I-2 requires inherited controls be formally identified and accepted.

### Evidence
- Issue #634 — control inheritance sub-page renders blank (one of 11 blank sub-pages)

### Impact
Systems cannot formally document which controls are inherited from CCPs. SSP exports will be incomplete and do not satisfy SP 800-37 Task I-2 requirements.

### Acceptance Criteria
- [ ] Control inheritance sub-page renders content
- [ ] Workflow to identify controls as inherited from a named CCP
- [ ] Formal acceptance action with responsible party and timestamp
- [ ] Inherited controls reflected correctly in SSP export

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.