Skip to content

OSCAL Reporting data

No due date 0% complete

Lula as a tool in the critical path towards authorization will become more apparent as we enable fully end-to-end workflows for distributed data -> system implementation.

As such reporting on data that provides concise insights to various personas will both be important as well as required when tooling wants to retrieve insights for visualization purposes.

Lula as a tool in the critical path towards authorization will become more apparent as we enable fully end-to-end workflows for distributed data -> system implementation.

As such reporting on data that provides concise insights to various personas will both be important as well as required when tooling wants to retrieve insights for visualization purposes.

Objectives

  • Support for retrieving and ingesting a catalog
  • Support for retrieving and ingesting a profile (if applicable)
  • Support for applying profile against catalog (if applicable)
  • Support for Calculating % controls satisfied / not-satisfied / not evaluated in the CLI
  • Support for creating a visual representation (static file) for the above findings

Evidence of Value

Do we know how many controls it covers? I am interested in tracking so we can see how much real time validation we are building up to over time

Loading