Design how to display a list of controls

[tuckerzp]

Description

We currently have a few different ways to view a list of controls:

Controls in a catalog without groups

https://viewer.oscalio.io/catalog?url=https://raw.githubusercontent.com/EasyDynamics/oscal-demo-content/tuckerzp/group-prose/catalogs/basic-test-catalog-no-groups.json

Controls in a catalog with groups

https://viewer.oscalio.io/catalog?url=https://raw.githubusercontent.com/EasyDynamics/oscal-demo-content/main/catalogs/NIST_SP-800-53_rev5_catalog.json

Controls listed in a profile

https://viewer.oscalio.io/profile?url=https://raw.githubusercontent.com/EasyDynamics/oscal-demo-content/main/profiles/NIST_SP-800-53_rev4_MODERATE-baseline_profile.json

Controls listed in a component definition

https://viewer.oscalio.io/component-definition?url=https://raw.githubusercontent.com/EasyDynamics/oscal-demo-content/main/component-definitions/example-component.json

Controls listed in an ssp

https://viewer.oscalio.io/system-security-plan?url=https://raw.githubusercontent.com/EasyDynamics/oscal-demo-content/main/system-security-plans/ssp-example.json

The way each of these lists is displayed and interacted with currently is very closely tied to the OSCAL document type they are contained within. This makes it difficult to use the list in a consistent way despite them being used to convey relatively similar data to the user.

Ideally we can formalize on one or two strategies that we can then use whenever we want to display a list of controls to a user.

Acceptance Criteria

• User interactions considered
• Low fidelity mock up created

Additional Notes

While not necessarily directly related to displaying a list of controls, it may be worth keeping in mind that we will eventually want to edit individual controls and edit controls displayed on the list.