Is there going to be an update for RHEL9? DISA Stig is now on V2R2 which has undergo many changes

[WarpedEdge]

Question
There has been multiple changes to the DISA stig for RHEL9, but the last update is from April this year. Since then we are on V2R2 which since then has removed 12 Stigs going from 462 to 450 among with other things like removing dependencies. Is there a new release still being worked on?

Environment (please complete the following information):

• Ansible Version: Ansible Core 2.16.3
• Host Python Version: 3.12.5
• Ansible Server Python Version: 3.12.5
• Additional Details:

[uk-bolly]

hi @WarpedEdge

Great question.
V2R1 (July release) was a huge lift (every control ID changed and audit alignment) alongside client requirements and should be in public repositories early in the new year.
We are currently working on the new releases that came out a couple of weeks ago (these align with different NIST standards), these are released to those who are subscribed first. We try to release to the public approx 3months after that.
So all being well, we aim to and normally release to public approx 4 months after release.

I hope that makes sense.

many thanks

uk-bolly

[WarpedEdge]

uk-bolly, Thank you for the quick response. Hope to see it out soon early next year. Unfortunate that you all release 4 months after a release, due to a lot of these requirements being quarterly means that the public will always be behind to the point of waiting on the new release is an old release at the next quarter would then be available and required. I hope that if anything that release windows could be shortened in the future, not to be detrimental to your subscribers, but also to give more value to the public who utilizes mindpoint heavily in smaller orgs. Thank you again.

…

On Tue, Nov 5, 2024 at 8:46 AM uk-bolly ***@***.***> wrote: hi @WarpedEdge <https://github.com/WarpedEdge> Great question. V2R1 (July release) was a huge lift (every control ID changed and audit alignment) alongside client requirements and should be in public repositories early in the new year. We are currently working on the new releases that came out a couple of weeks ago (these align with different NIST standards), these are released to those who are subscribed first. We try to release to the public approx 3months after that. So all being well, we aim to and normally release to public approx 4 months after release. I hope that makes sense. many thanks uk-bolly — Reply to this email directly, view it on GitHub <#61 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVQGRMXJYNJKNUCSDWWB3SDZ7DD3NAVCNFSM6AAAAABRGRWB3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJXGIZDIOBVGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[uk-bolly]

hi @WarpedEdge

I understand your frustration, we do have a large number of repositories and branches that we maintain, the majority are open source, so we do try to get these out as soon as possible and sometimes it is under 4 months it all depends on the number of changes that take place in each release. Recently there has been significant changes to a large number of repositories and releases with many being completely rewritten and this all adds to the time.
However we have just released v2r1 to devel and hope to push to main in a couple of weeks. Once that i done we are looking to pull forward some of the other releases to try and get in alignment once again with what we are trying to deliver.

Kindest regards

uk-bolly