RFC: update to use the 4.x/5.x data features

[aaronlippold]

• [ ] defaults to text based impacts: none,low,medium,high,critical
• [ ] uses desc 'sub-section, 'textfor:check,fix,justification,vulnerability discussion`, etc[]
• [ ] puts attributes in the inspec.yml file and uses the shared attributes model
• [ ] has the ability to remember what attributes have been created already for easy reuse
• [ ] uses the supports: <platform> in the inspec.yml
• [ ] adds both a single line profile title and a long desc with in the inspec.yml
• [ ] correctly populates all the values in the inspec.yml template

[aaronlippold]

I actually want a couple things out of that PR for both Heimdall and Heimdall-Lite and Vulcan and the _tools.

( please create an issues on each project for this - and create a PR or PRs to cover the 6 elements )

• [ ] That we update the parsing to allow for either a tag fix and check or a desc, fix and check.
• [ ] That we allow for allow for three new types: desc, justification, caveat, discussion a. That caveat and or justification are appended to the 'Finding Details' b. We actually search for /*caveat*/ and /*justification*/ - such that myorg-/_caveat is discovered. b. that discussion or /*discussion*/ be appended to the bottom of the general description - such that vulnerability_discussion would be discovered.
• [ ] That we support both text based impacts and numeric based impacts a. that our default is the text based impact b. that we 'display' the text based impact but put the numeric in if it was used high (0.7)
• [ ] That we update inspec_tools and heimdall_tools to use the new sub-sections and text based impacts
• [ ] That CAT I / CAT II / CAT III be replaced by High / Medium / Low
• [ ] That our tools do not create code that uses " where ' are the correct style

[rbclark]

Is there an InSpec profile created somewhere that already uses all these elements that I can use for reference to make sure the output generated by Vulcan looks correct?

[aaronlippold]

Windows 10 on the mitre GitHub.

On Wed, Mar 25, 2020, 8:37 AM Robert Clark notifications@github.com wrote:

Is there an InSpec profile created somewhere that already uses all these elements that I can use for reference to make sure the output generated by Vulcan looks correct?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/mitre/vulcan/issues/39#issuecomment-603815348, or unsubscribe https://github.com/notifications/unsubscribe-auth/AALK42HG4UNMXF2BI6S6EF3RJH3IXANCNFSM4GFWKJFQ .

[github-actions[bot]]

Stale issue message

[Bialogs]

I think this is more applicable for inspec_tools

[aaronlippold]

just want to make sure we use our style guide when we generate profiles

---

Aaron Lippold

@.***

260-255-4779

twitter/aim/yahoo,etc. 'aaronlippold'

On Tue, Sep 28, 2021 at 1:31 PM Kyle @.***> wrote:

Closed #39 https://github.com/mitre/vulcan/issues/39.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/mitre/vulcan/issues/39#event-5375516068, or unsubscribe https://github.com/notifications/unsubscribe-auth/AALK42HM266WINGHEPJCGBTUEH3XPANCNFSM4GFWKJFQ .