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.

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

Add config file support for control omission #351

Open
5 tasks
Tracked by #161
adhilto opened this issue Aug 15, 2024 · 0 comments · May be fixed by #431
Open
5 tasks
Tracked by #161

Add config file support for control omission #351

adhilto opened this issue Aug 15, 2024 · 0 comments · May be fixed by #431
Assignees
Milestone

Comments

@adhilto
Copy link
Collaborator

adhilto commented Aug 15, 2024

💡 Summary

Allow users to indicate which controls should be omitted from the ScubaGoggles report and specify the rationale for doing so.

Motivation and context

Feature recently added to ScubaGear. See:

Implementation notes

Related epic: #161.

PR for this feature on ScubaGear: cisagov/ScubaGear#1200.

Example config file on ScubaGear: https://github.com/cisagov/ScubaGear/blob/main/PowerShell/ScubaGear/Sample-Config-Files/omit_policies.yaml.

Acceptance criteria

  • Controls can be omitted via the config file
  • Config file allows you to indicate the rationale
  • Config file allows you to indicate an "expiration date," the date after which the control should no longer be omitted
  • The Reporter has been updated to properly display the omitted policies
  • Feature has been documented in the Readme files
@adhilto adhilto mentioned this issue Aug 15, 2024
9 tasks
@adhilto adhilto modified the milestones: Driftwood, Coast Sep 12, 2024
@adhilto adhilto self-assigned this Sep 23, 2024
@adhilto adhilto linked a pull request Sep 24, 2024 that will close this issue
14 tasks
@adhilto adhilto linked a pull request Sep 24, 2024 that will close this issue
14 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant