search

finos / common-cloud-controls

FINOS Common Cloud Controls
https://www.finos.org/common-cloud-controls-project
Other
34 stars 39 forks source link

Define the tooling that should be used by the group / open source community? #44

Closed mcleo-d closed 7 months ago

mcleo-d commented 1 year ago

Due date : 15th December 2023

This GitHub issues represents part of the roadmap defined by the OSCAL working group on https://github.com/finos/common-cloud-controls/issues/13

### Tasks
- [ ] Define the tooling that should be used by the group / open source community?
- [ ] Should OSCAL be written by hand?
- [ ] How are the services described as OSCAL?
- [ ] Are there any editorial tools that enable automation of OSCAL?
- [ ] How should contributions be validated and accepted?
- [ ] Maybe other collaboration and editing solutions are better for the team?
robmoffat commented 10 months ago

@iMichaela having an OSCAL tool to help with formatting would be useful in the long run. Simple examples can be easily written by hand, but this becomes problematic after a certain size.

@eddie-knight have we made clear the project's vision for OSCAL?

@iMichaela without tooling people are likely to become lost.

@eddie-knight It might be good to extract this from the white paper so that it's easy to read + absorb.

@iMichaela (the white paper) doesn't give a clear example of how the controls work yet. Once you have the controls in a catalog, each component can show how they implement those controls.

Various tools for styling / displaying OSCAL in a human-friendly way.

robmoffat commented 10 months ago

https://github.com/oscal-club/awesome-oscal

robmoffat commented 10 months ago

See also: https://oscal-compass.github.io/compliance-trestle/

robmoffat commented 10 months ago

Related:

crawfordchanel commented 7 months ago

Closing: Mapped with issue #45