Skip to content

Conversation

DMedina6
Copy link
Contributor

@DMedina6 DMedina6 commented Oct 2, 2024

Update V1R3 to Windows_Server_2019_STIG_V3R1 profile controls definitions
v3r1-report.md

@karikarshivani
Copy link
Contributor

So far, I've reviewed 150ish (about half) of the controls and here are the unexpected changes I found:

Controls that overrode the main description with the skip statement and modified main impact

  • V-92963 -> SV-205732
  • V-93035 -> SV-205742
  • V-93037 -> SV-205743
  • V-93121 -> SV-205785
  • V-93123 -> SV-205786
  • V-93125 -> SV-205787
  • V-93127 -> SV-205788
  • V-93129 -> SV-205789
  • V-93131 -> SV-205790

Controls that only modified the main impact

  • V-92975 -> SV-205624
  • V-92977 -> SV-205710
  • V-92991 -> SV-205663
  • V-92995 -> SV-205665
  • V-92997 -> SV-205666
  • V-92999 -> SV-205667
  • V-93001 -> SV-205668
  • V-93003 -> SV-205669
  • V-93005 -> SV-205670
  • V-93133 -> SV-205791
  • V-93135 -> SV-205792
  • V-93137 -> SV-205793
  • V-93027 -> SV-205738
  • V-93039 -> SV-205744
  • V-93041 -> SV-205745
  • V-93043 -> SV-205746
  • V-93207 -> SV-205846
  • V-93211 -> SV-205877

Control that duplicated the older version?

  • V-93025 -> SV-205737

(Optional) Controls I'm curious about - they changed the check and/or fix text values to string literals %q(). Long term, it would be nice to standardize string updates - we can discuss further later

  • V-93019 -> SV-205734
  • V-93021 -> SV-205735
  • V-93023 -> SV-205736
  • V-93033 -> SV-205741

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants