Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Reporting of number of controls met by component definitions #223

Open
6 tasks
brandtkeller opened this issue Jan 19, 2024 · 2 comments · May be fixed by #599
Open
6 tasks

Reporting of number of controls met by component definitions #223

brandtkeller opened this issue Jan 19, 2024 · 2 comments · May be fixed by #599
Assignees
@CloudBeard
Labels
enhancement New feature or request
Milestone
OSCAL Reporting data

Comments

@brandtkeller
Copy link
Member

brandtkeller commented Jan 19, 2024 •
edited
Loading

Is your feature request related to a problem? Please describe.

Ability to report on the number of controls present in a component definition - filtered by control-implementation source and framework.

Describe the solution you'd like

  • Given a component definition is present
  • When lula report is executed
  • Then a report logged to stdout to capture number of controls based on the above filter

Additional context

This would pave the way for future reporting on percentage of controls (when Lula can properly process both catalogs and profiles).

Expected Deliverable

  • Report Command added
  • Ability to ingest component-definition files (error otherwise)
  • Aggregate number of controls by control-implementation source and framework
  • Log report to stdout
  • Tests
  • Docs
@brandtkeller brandtkeller added the enhancement New feature or request label Jan 19, 2024
@brandtkeller brandtkeller mentioned this issue Feb 7, 2024
Open
@brandtkeller brandtkeller added the triage Awaiting triage from the team label Mar 29, 2024
@CloudBeard CloudBeard mentioned this issue Apr 16, 2024
Closed
4 tasks
@CloudBeard CloudBeard self-assigned this Apr 16, 2024
@brandtkeller brandtkeller added this to the OSCAL Reporting data milestone Apr 26, 2024
@brandtkeller
Copy link
Member Author

brandtkeller commented May 31, 2024 •
edited
Loading 

flowchart TD
    A[Report] -->|default/specified OSCAL files| B(Build Report)
    B --> C{Check for existence of models & Collect/identify Catalog}
    C -->|Components Exist| D[Component Report]
    C -->|SSP Exists| E[System Report]
    C -->|Assessment Results Exist| F[Assessment Report]
Loading

@brandtkeller brandtkeller removed the triage Awaiting triage from the team label May 31, 2024
@brandtkeller brandtkeller self-assigned this May 31, 2024
@CloudBeard
Copy link
Collaborator

That makes perfect sense ^

@brandtkeller brandtkeller changed the title Catalog Implementation derived from Component-Definitions Reporting of percentage of controls met by component definitions May 31, 2024
@brandtkeller brandtkeller mentioned this issue May 31, 2024
Closed
5 tasks
@CloudBeard CloudBeard linked a pull request Aug 14, 2024 that will close this issue
Draft
6 tasks
@brandtkeller brandtkeller removed their assignment Aug 15, 2024
@brandtkeller brandtkeller changed the title Reporting of percentage of controls met by component definitions Reporting of number of controls met by component definitions Aug 16, 2024
@brandtkeller brandtkeller linked a pull request Sep 4, 2024 that will close this issue
feat: initial lula report #599
Draft
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@CloudBeard CloudBeard

Labels
enhancement New feature or request
Projects
Lula and Friends
Status: 🏗 In Progress
Milestone
OSCAL Reporting data
2 participants
@brandtkeller @CloudBeard