Just used SAF CLI v1.6.0 to generate an InSpec profile from the SLES15 STIG (see here for the initial commit).
CI/CD failed at the vendor step because the inspec.yml produced by saf generate inspec_profile was malformed:
/Users/wdower/.rbenv/versions/3.3.0/lib/ruby/3.3.0/rubygems/requirement.rb:107:in `parse': Illformed requirement ["\"~>6.0\"\n"] (Gem::Requirement::BadRequirementError)
Using CINC Auditor at 7.1.7 and Ruby at 3.3.0.
Fixing it is trivial -- edit inspec.yml
inspec_version: |
"~>6.0"
to
but the fact remains that using SAF CLI to generate a profile should result in a profile that passes the check command (there will of course still be loads of warnings about tests not being populated with code, but that's expected).
As a side note, the copyright_email should be updated from saf@groups.mitre.org to just saf@mitre.org.
Just used SAF CLI v1.6.0 to generate an InSpec profile from the SLES15 STIG (see here for the initial commit).
CI/CD failed at the vendor step because the
inspec.ymlproduced bysaf generate inspec_profilewas malformed:/Users/wdower/.rbenv/versions/3.3.0/lib/ruby/3.3.0/rubygems/requirement.rb:107:in `parse': Illformed requirement ["\"~>6.0\"\n"] (Gem::Requirement::BadRequirementError)Using CINC Auditor at 7.1.7 and Ruby at 3.3.0.
Fixing it is trivial -- edit
inspec.ymlto
but the fact remains that using SAF CLI to generate a profile should result in a profile that passes the
checkcommand (there will of course still be loads of warnings about tests not being populated with code, but that's expected).As a side note, the
copyright_emailshould be updated from saf@groups.mitre.org to just saf@mitre.org.