Discussion: What are the next distributions or features to develop for linux-bench ?

[andypitcher]

Issue:

• Discussion: What are the next distributions or features to develop for linux-bench ? #102

[andypitcher]

@LaibaBareera can you follow up here if you know more about the roadmap, as @afdesk mentioned ?

[LaibaBareera]

Hi @andypitcher,
We don’t keep a fixed roadmap. We add distribution-specific CIS benchmarks on demand and cut a release when a profile is complete. Recent/active targets include Bottlerocket, Amazon Linux 2023, Google_Container_Optimized_OS and Amazon Linux 2.

How we prioritize

• Driven by customer/field requests and platform usage.
• Requires an upstream CIS benchmark and accessible test images.
• We may de-prioritize or retire profiles when a distro goes EOL or demand drops.

How we release

• Implement the selected distro/version’s CIS checks end-to-end.
• Validate on reference images.
• Publish a new release once complete (event-based, not time-based).

How we update

• Patch releases for fixes as they come in.
• Bump to newer CIS revisions when upstream updates (subject to demand/availability).
• We no longer ship the generic “distribution-independent” profile.

@afdesk, correct me if I am wrong.

[andypitcher]

Makes sense, thanks for providing these details.

Would it make sense to archive CIS Distribution Independent 1.1.0 and 2.0.0, and the related PR/issues ?

For the next OSes, wdyt of:

• CIS SUSE Linux Enterprise 12 Benchmark v3.2.0
• CIS Rocky Linux 10 Benchmark v1.0.0

[LaibaBareera]

@andypitcher Thanks!

On archiving DIL 1.1.0 / 2.0.0: I’d keep them for now—they still serve as a fallback for platforms where we don’t yet have a distro-specific CIS profile. We can mark them as legacy and close/retire related PRs/issues once coverage exists for those OSes.

On next OS targets: SLES 12 and Rocky Linux 10 aren’t currently driven by demand on our side, so they’re not in the near-term queue. We’re focused on AKS-optimized Azure Linux 2 and 3 next. We can revisit SLES/Rocky after that.

[andypitcher]

Understood, thanks for confirming.