-
Notifications
You must be signed in to change notification settings - Fork 242
SSP Control Implementation Scope/Origination #784
Copy link
Copy link
Closed
Labels
Discussion NeededThis issues needs to be reviewed by the OSCAL development team.This issues needs to be reviewed by the OSCAL development team.Model EngineeringAn issue to be discussed during the bi-weekly Model Engineering MeetingAn issue to be discussed during the bi-weekly Model Engineering MeetingUser Storyenhancement
Milestone
Metadata
Metadata
Assignees
Labels
Discussion NeededThis issues needs to be reviewed by the OSCAL development team.This issues needs to be reviewed by the OSCAL development team.Model EngineeringAn issue to be discussed during the bi-weekly Model Engineering MeetingAn issue to be discussed during the bi-weekly Model Engineering MeetingUser Storyenhancement
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
StatusShow more project fields
Done
User Story:
As an OSCAL we need to better differentiate scope and origination of responsibility for control and more granular control statements in the SSP model.
See the table in issue #572 for inspiration for references.
Goals:
implemented-requirement,statement, and/orby-component)Dependencies:
None.
Acceptance Criteria