live wire
▸AI · vLLM Recipes maps Muse Spark Open to single-node Blackwell and AMD deployment (Oct. 16)vLLM▸PLATFORM · Clang 23 bytecode interpreter cuts allocations and expands constant-expression supportRed Hat Developer▸PLATFORM · RHEL becomes first-party on OCI; OpenShift subscriptions reach Oracle MarketplaceRed Hat▸AI · vLLM-Omni merges native MOSS-Image serving with parallelism and offloadvLLM▸AI · vLLM adds System One endpoint for Decision 3.0 multimodal routing models (Oct. 15)vLLM▸SECURITY · Red Hat rates OpenShift AI 3.4.5 update Critical; advisory lists hundreds of CVEsRed Hat Product Security▸SECURITY · Red Hat’s first Security Signals report shifts focus from CVE counts to risk paths (Oct. 15)Red Hat▸PLATFORM · IBM adds non-destructive FlexVolume-to-CSI migration tool for OpenShift object storageIBM Cloud▸vLLM tests agent-built Kimi K3 decode path at up to 1.9× speedup; PR remains openvLLM▸AI · LeaderWorkerSet 1.0 changes rollout defaults for disaggregated AI workloadsKubernetes SIGs▸SECURITY · Red Hat flags active exploitation of kernel flaw affecting OpenShift CoreOS; no fix listedRed Hat Product Security▸AI · Red Hat sets Dec. 9 showcase for AI 3.6 agent governance and model servicesRed Hat▸vLLM 0.32.0 drops Python 3.10, restricts CORS defaults and adds security fixesvLLM▸SECURITY · Red Hat tracks Moderate Hono auth bypass across OpenShift AI, Dev Spaces and AnsibleRed Hat Product Security▸AI · vLLM Recipes maps Muse Spark Open to single-node Blackwell and AMD deployment (Oct. 16)vLLM▸PLATFORM · Clang 23 bytecode interpreter cuts allocations and expands constant-expression supportRed Hat Developer▸PLATFORM · RHEL becomes first-party on OCI; OpenShift subscriptions reach Oracle MarketplaceRed Hat▸AI · vLLM-Omni merges native MOSS-Image serving with parallelism and offloadvLLM▸AI · vLLM adds System One endpoint for Decision 3.0 multimodal routing models (Oct. 15)vLLM▸SECURITY · Red Hat rates OpenShift AI 3.4.5 update Critical; advisory lists hundreds of CVEsRed Hat Product Security▸SECURITY · Red Hat’s first Security Signals report shifts focus from CVE counts to risk paths (Oct. 15)Red Hat▸PLATFORM · IBM adds non-destructive FlexVolume-to-CSI migration tool for OpenShift object storageIBM Cloud▸vLLM tests agent-built Kimi K3 decode path at up to 1.9× speedup; PR remains openvLLM▸AI · LeaderWorkerSet 1.0 changes rollout defaults for disaggregated AI workloadsKubernetes SIGs▸SECURITY · Red Hat flags active exploitation of kernel flaw affecting OpenShift CoreOS; no fix listedRed Hat Product Security▸AI · Red Hat sets Dec. 9 showcase for AI 3.6 agent governance and model servicesRed Hat▸vLLM 0.32.0 drops Python 3.10, restricts CORS defaults and adds security fixesvLLM▸SECURITY · Red Hat tracks Moderate Hono auth bypass across OpenShift AI, Dev Spaces and AnsibleRed Hat Product Security
upstreambeat.ai
newsSECURITY

RHEL 10 gains automated scanning and remediation for DISA STIG V1R2

SCAP Security Guide 0.1.82 aligns the RHEL 10 profile with the official benchmark and makes it usable across OpenSCAP, Satellite and Red Hat Lightspeed.

RHEL 10 STIG automation versus manual remediation.
Side by side: what changed
By The News Desk· Sep 26, 2026the quick take — two AI hosts go live when you do

Red Hat has released an automated compliance profile for Red Hat Enterprise Linux 10 that follows the official Defense Information Systems Agency Security Technical Implementation Guide, replacing the earlier vendor profile with content aligned to RHEL 10 DISA STIG Benchmark V1R2.

The profile ships in scap-security-guide 0.1.82. Red Hat’s release notes say the update brings the RHEL 10 profile into line with the official benchmark; the same release also updates the RHEL 8 and RHEL 9 DISA profiles to V2R8 and V2R9, respectively.

What administrators can automate

According to Red Hat’s announcement, administrators can use the stig or stig_gui profile to evaluate and remediate RHEL 10 systems through OpenSCAP’s oscap command, Red Hat Satellite or Red Hat Lightspeed. Red Hat also points to an official RHEL 10 STIG Ansible role for applying the controls.

The same content can be used earlier in the system lifecycle. Red Hat says organizations can apply STIG hardening through Kickstart, RHEL image builder and RHEL image mode rather than treating compliance as a post-install cleanup task. For platform teams, that creates a path to put the benchmark into repeatable image pipelines and provisioning workflows.

Version 0.1.82 also improves RHEL 10 remediation scripts so that newly created files and directories receive explicit owners and permissions, and adds rationale to the rule requiring the SSSD package, according to the SCAP Security Guide notes.

Automation is not certification

The new profile automates technical checks and remediations; it does not certify a deployed environment. Red Hat explicitly says administrators and security officers still need to review findings in the context of their operational environment to establish compliance.

That distinction matters for teams pursuing an Authority to Operate. The profile can make assessment, remediation and evidence collection more repeatable, but organizations remain responsible for interpreting results, documenting exceptions and satisfying controls that cannot be reduced to host configuration.

Filed by The News Desk. Corrections: desk@upstreambeat.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.