# Hardening and auditing SLES 16: OpenSCAP, CIS context and SUSE Multi-Linux Manager

Source: https://forgeone.solutions/en/tech/sles-16-hardening-openscap-cis-mlm
Language: en
Published: 2026-10-06
Updated: 2026-11-20

Practical SLES 16 guide with OpenSCAP, ANSSI high lab evidence, CIS Level 2 positioning and SUSE Multi-Linux Manager channel readiness.

This lab article closes a practical gap in the SUSE series: it does not stop at installing SLES 16, but shows how a managed SLES 16 system behaves when OpenSCAP content, hardening profiles, remediation and SUSE Multi-Linux Manager lifecycle channels meet in practice.

The important finding is deliberately precise: CIS publishes a benchmark for SUSE Linux Enterprise 16, but the SUSE-provided scap-security-guide package in this lab exposes ANSSI, HIPAA, PCI-DSS and base profiles for SLE 16, not a ready-made CIS Level 2 profile. Therefore this article documents an ANSSI-BP-028 high run and explains how CIS Level 2 must be handled separately and honestly.

## Why CIS, OpenSCAP and Hardening Matter

CIS Benchmarks are vendor- and community-maintained security baselines. They translate common operating-system hardening questions into concrete checks: password policy, SSH behavior, sudo restrictions, file permissions, audit rules, kernel parameters and logging. In practice they are useful because security teams, auditors and operations teams can discuss the same baseline instead of comparing vague hardening opinions.

OpenSCAP is tooling for evaluating machine-readable SCAP content. The oscap command can scan a system, generate an HTML report and, depending on the profile, create remediation in Bash or Ansible form. That makes hardening repeatable: first measure, then change deliberately, then scan again and document exceptions.

SUSE Multi-Linux Manager adds the operational layer around that workflow. Packages, profiles, remediation runs and evidence do not live on an isolated test machine, but inside the same lifecycle, proxy and channel model that also supplies updates to production servers. That is why this article checks the manager and channel path before looking at the score.

### Concepts at a glance

| Term | Meaning | Why it matters |
| --- | --- | --- |
| CIS Benchmark | A published hardening baseline for a product or platform | Creates a shared technical and audit reference |
| CIS Level 1 | Usually a practical baseline with lower operational impact | Good starting point for broadly used systems |
| CIS Level 2 | Stricter baseline with more potential operational impact | Needs workload testing and documented exceptions |
| SCAP | Machine-readable security content and result format | Allows automated scans and comparable evidence |
| OpenSCAP / oscap | Scanner and reporting tooling for SCAP content | Turns profiles into repeatable checks and reports |
| Remediation | Generated or manual changes to satisfy failed rules | Must be reviewed before production rollout |

## Lab Setup

### Systems used

| Component | Role | Evidence |
| --- | --- | --- |
| mlm01.example.test | SUSE Multi-Linux Manager 5.2 | Manager UI, channel assignment and registered system view |
| mgrproxy01.example.test | MLM proxy between manager and client | Client repositories were served through the proxy URL |
| sles16-client01.example.test | SLES 16 managed client | OpenSCAP scan target and remediation target |

[![SLES 16 client in SUSE Multi-Linux Manager](https://forgeone.solutions/media/02-mlm-sles16-client-filtered.png)](https://forgeone.solutions/media/02-mlm-sles16-client-filtered.png)

The SLES 16 client was reachable through the proxy, registered in SUSE Multi-Linux Manager and assigned to a production lifecycle channel. That is intentionally close to a customer rollout: the compliance workflow must work through the same package and proxy path that normal operations use.

## Channel Readiness Before Hardening

The first check was not an OpenSCAP scan. It was package availability on the managed client. A hardening guide is not useful if the client cannot install the scanner and the security guide from its assigned lifecycle channel.

```bash
zypper refresh
zypper se -s openscap scap-security-guide
rpm -q openscap openscap-utils libopenscap33 scap-security-guide
```

In the lab, the production channel assigned to the client did not expose all OpenSCAP packages even though the manager already had them in other synchronized SLES 16 channels. This is a realistic lifecycle-management issue: cloned channels can be too narrow or stale. Fix the channel content before scheduling scans at scale.

### Package readiness

| Package | Purpose | Finding |
| --- | --- | --- |
| openscap-utils | Provides oscap CLI tooling | Required for local scan and report generation |
| scap-security-guide | Provides SLE 16 datastream content | Required for supported profiles |
| libopenscap33 | Runtime library | Dependency of OpenSCAP tools |
| libexslt0 / libxmlsec1-openssl1 | XML and signature support | Dependency gap surfaced during package installation |

## Available SLES 16 Profiles

```bash
oscap info /usr/share/xml/scap/ssg/content/ssg-sle16-ds.xml
```

### Profile result

| Profile | Status in this lab | Operational interpretation |
| --- | --- | --- |
| ANSSI-BP-028 minimal/intermediary/enhanced/high | Available | Usable for automated SLE 16 OpenSCAP evidence |
| HIPAA | Available | Useful for healthcare-aligned baseline checks |
| PCI-DSS 4.0.1 | Available | Useful where cardholder-data environments are relevant |
| CIS Level 1 / Level 2 | Not exposed by the installed SSG datastream | Use CIS benchmark/CIS-CAT/Build Kit or a validated tailored profile instead |

## Baseline Scan

```bash
mkdir -p /root/openscap-evidence/sles16-hardening-20261006
oscap xccdf eval \
  --profile xccdf_org.ssgproject.content_profile_anssi_bp28_high \
  --results /root/openscap-evidence/sles16-hardening-20261006/anssi-high-results.xml \
  --report /root/openscap-evidence/sles16-hardening-20261006/anssi-high-report.html \
  /usr/share/xml/scap/ssg/content/ssg-sle16-ds.xml
```

[![OpenSCAP baseline report before remediation](https://forgeone.solutions/media/06-openscap-baseline-scoring.png)](https://forgeone.solutions/media/06-openscap-baseline-scoring.png)

### Baseline result

| Result | Count | Meaning |
| --- | --- | --- |
| PASS | 156 | Controls already fulfilled by the installed system |
| FAIL | 216 | Rules requiring remediation or design decisions |
| NOT APPLICABLE | 24 | Rules not applicable to this target |
| NOT CHECKED | 1 | Rule not evaluated automatically |

## Controlled Remediation

Before applying remediation, the VM was snapshotted. This is not optional for high-hardening profiles. Partitioning, sudo, audit, PAM, SSH and kernel settings can affect access and operations immediately.

```bash
virsh snapshot-create-as \
  --domain sles16-client01 \
  --name before-openscap-anssi-high-20261006 \
  --description "Before SLES16 OpenSCAP ANSSI high remediation evidence run" \
  --disk-only --atomic --no-metadata

oscap xccdf generate fix --fix-type bash \
  --profile xccdf_org.ssgproject.content_profile_anssi_bp28_high \
  --output anssi-high-remediation.sh \
  anssi-high-results.xml

oscap xccdf generate fix --fix-type ansible \
  --profile xccdf_org.ssgproject.content_profile_anssi_bp28_high \
  --output anssi-high-remediation.yml \
  anssi-high-results.xml
```

The remediation script completed, but the log also showed realistic limits: some packages could not be reinstalled from the assigned repositories, one SSSD PAM remediation was missing, and sudo was hardened with requiretty, noexec, use\_pty and umask. That is exactly why remediation belongs into a tested maintenance workflow instead of a blind one-liner.

[![OpenSCAP report after remediation](https://forgeone.solutions/media/07-openscap-post-remediation-scoring.png)](https://forgeone.solutions/media/07-openscap-post-remediation-scoring.png)

### Before and after

| Metric | Before remediation | After remediation |
| --- | --- | --- |
| PASS | 156 | 261 |
| FAIL | 216 | 101 |
| ERROR | 0 | 10 |
| Score | not used as release gate | 79.57 percent in the generated report |

## What This Means for CIS Level 2

Do not rename an ANSSI high scan to CIS Level 2. If a customer requires CIS Level 2 for SLES 16, the correct path is to obtain the CIS SLE 16 benchmark content, run it with CIS-CAT Pro or a validated tailored SCAP workflow, document local exceptions and keep the evidence tied to the actual benchmark version.

### Technical acceptance

| Check | Result | Comment |
| --- | --- | --- |
| Client managed by MLM | PASS | sles16-client01.example.test visible and current in MLM |
| Proxy path used | PASS | Client repositories were served through mgrproxy01.example.test |
| OpenSCAP package readiness | PASS WITH FINDING | Packages existed on the manager, but lifecycle channel content needed attention |
| SLE 16 SSG profile discovery | PASS | ANSSI, HIPAA, PCI-DSS and base profiles listed |
| CIS Level 2 automation | NOT CLAIMED | CIS benchmark exists, but no CIS profile was present in the installed SUSE SSG datastream |
| Remediation | PASS WITH CONDITIONS | Improved results, but repository and sudo/noexec effects require operational review |

## Operational Checklist

For production, treat this as a controlled change: verify channel contents, snapshot or backup first, run a baseline scan, review the generated remediation, apply in a maintenance window, re-scan, document exceptions and only then define whether the system is compliant enough for the intended workload.

## Hero image

[![OpenSCAP report after remediation](https://forgeone.solutions/media/07-openscap-post-remediation-scoring.png)](https://forgeone.solutions/media/07-openscap-post-remediation-scoring.png)

## Author

Mathias Rumbold

## Category

- [Enterprise Linux](https://forgeone.solutions/en/tech/sles-16-hardening-openscap-cis-mlm?category=enterprise-linux)

## Tags

- [SUSE](https://forgeone.solutions/en/tech/sles-16-hardening-openscap-cis-mlm?tags=suse)
- [SLES 16](https://forgeone.solutions/en/tech/sles-16-hardening-openscap-cis-mlm?tags=sles-16)
- [CIS Benchmark](https://forgeone.solutions/en/tech/sles-16-hardening-openscap-cis-mlm?tags=cis-benchmark)
- [Hardening](https://forgeone.solutions/en/tech/sles-16-hardening-openscap-cis-mlm?tags=hardening)
- [SUSE Multi-Linux Manager](https://forgeone.solutions/en/tech/sles-16-hardening-openscap-cis-mlm?tags=suse-multi-linux-manager)

## SUSE Enterprise Linux & Multi-Linux Manager Schritt für Schritt

Die Serie verbindet SLES 16 Grundlagen mit dem produktiven Aufbau von SUSE Multi-Linux Manager 5.2. Bestehende URLs bleiben unverändert.

1. [Install SLES 16 for production: from ISO to manageable Linux server](https://forgeone.solutions/en/tech/install-sles-16)
2. [SLES 16 and Enterprise Linux: How Different Is Day-to-Day Administration?](https://forgeone.solutions/en/tech/sles-16-enterprise-linux-rhel-rocky-almalinux-comparison)
3. [Hardening and auditing SLES 16: OpenSCAP, CIS context and SUSE Multi-Linux Manager (current part)](https://forgeone.solutions/en/tech/sles-16-hardening-openscap-cis-mlm)
4. [Install SUSE Multi-Linux Manager 5.2 for production: SL Micro, storage and first channel sync](https://forgeone.solutions/en/tech/install-suse-multi-linux-manager-5-2-sl-micro)
5. [SUSE Multi-Linux Manager 5.2: onboard first Linux clients for production](https://forgeone.solutions/en/tech/suse-multi-linux-manager-5-2-onboard-linux-clients)
6. [SUSE Multi-Linux Manager 5.2: build production patch and lifecycle management](https://forgeone.solutions/en/tech/suse-multi-linux-manager-5-2-patch-lifecycle-management)
7. [SUSE Multi-Linux Manager 5.2: manage mixed Linux estates in production](https://forgeone.solutions/en/tech/suse-multi-linux-manager-5-2-manage-mixed-linux)
8. [SUSE Multi-Linux Manager 5.2: use OpenSCAP, compliance and audit in production](https://forgeone.solutions/en/tech/suse-multi-linux-manager-5-2-openscap-compliance-audit)
9. [SUSE Multi-Linux Manager 5.2: build proxies for sites and distributed Linux estates](https://forgeone.solutions/en/tech/suse-multi-linux-manager-5-2-build-proxies-for-sites)
10. [SUSE Multi-Linux Manager 5.2: integrate SSO with Keycloak, SAML and MFA](https://forgeone.solutions/en/tech/suse-multi-linux-manager-5-2-integrate-sso-keycloak-saml-mfa)
11. [SUSE Multi-Linux Manager 5.2: use Ansible next to Salt in production](https://forgeone.solutions/en/tech/suse-multi-linux-manager-5-2-ansible-next-to-salt)
12. [SUSE Multi-Linux Manager 5.2: build reporting, inventory and subscription audit](https://forgeone.solutions/en/tech/suse-multi-linux-manager-5-2-reporting-inventory-subscription-audit)
13. [Operate and harden SUSE Multi-Linux Manager 5.2 in production](https://forgeone.solutions/en/tech/operate-harden-suse-multi-linux-manager-5-2-production)

## Further content

- [SUSE Linux Enterprise Server](https://forgeone.solutions/en/products/suse-linux-enterprise-server)
