Skip to content

Instantly share code, notes, and snippets.

@predominant

predominant/inspec-scaffolding-v2.md

Created July 16, 2020 01:09
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save predominant/c9c27b1364de8daa236ca4a0fcccf433 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save predominant/c9c27b1364de8daa236ca4a0fcccf433 to your computer and use it in GitHub Desktop.
Download ZIP

Revisions

  1. predominant created this gist Jul 16, 2020.
    30 changes: 30 additions & 0 deletions inspec-scaffolding-v2.md
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,30 @@
    # Scaffolding vNext

    ## Motivation

    The current scaffolding works really well.

    Improvements and rearchitecting the current scaffolding would allow for greater flexibility, visibility and customization in profile use and reporting.

    ## Goals

    * Every profile is a Habitat artifact
    * Every profile/artifact can be run stand-alone as a once-off run, or as a service with all the benefits of package subscription and automatic updating that Habitat provides
    * Every profile employed in a scan is reported separately (specified individually on the `inspec exec` command line)
    * Leverage Habitat for profile dependencies

    ## Nice to have

    * Maintain the list of profiles to be run in a single location
    * Minimal (if any) changes required to existing Inspec profiles

    ## Notes

    ### Graham

    * We need to retain the ability to modify profiles (eg: Setting custom scores)
    * we need to ensure waivers are intelligently managed either in-artifact, or injectable some time later (during run, with configuration?)

    ### Matt

    * Potentially use inputs to define scores/custom values, with defaults in the profile itself.