Quick Start

Use a Linux host group for source, library, enrollment, baseline, assessment, and remediation. Windows differs in source type, package upload, and reboot detection.

Prerequisites

• Your account can manage sources, the library, targets, and baselines.
• You have a reachable Linux host, entered manually or already enrolled in Node Management.
• The host can reach the selected repository. Built-in public sources require public repository access.
• Install and reboot change the host. Try a non-critical host first.

Confirm a patch source

1. Open Settings → Patch Sources.
2. Use a built-in public YUM, DNF, or APT source, or add a custom source. A custom source belongs to the current organization.
3. Test connectivity before saving. Saved sources can be tested one by one or in a batch.
4. Disable a source you do not want synchronized.

Import patches

1. Open Patch Library and choose Linux or Windows.
2. Preview sync candidates, select the patches to import, and adjust severity if needed.
3. You can also create a patch manually. A Windows package upload requires a file.
4. A patch referenced by a baseline or currently being remediated cannot be deleted.

Enroll targets

1. Open Targets.
2. For manual entry, fill the Windows or Linux connection and test it before saving.
3. When importing from Node Management, select at least one node.
4. Changing connection details runs connectivity detection again.
5. Confirm operating system, architecture, source, and connectivity. A host without a baseline is not yet a risk.

Create a baseline and assess

1. Open Baselines and create a baseline for the operating system.
2. Add library patches as requirements. The same patch is not added twice.
3. Bind hosts. A host has only one baseline. A new binding replaces the old one.
4. Requirement or binding changes invalidate the old assessment.
5. Assess from the baseline, or open Home and start an immediate assessment for the visible enrolled hosts. A baseline with no requirements or no hosts cannot be assessed.
6. Only hosts bound to a baseline produce a compliance result. Unbound hosts can be visited by an assessment task, but they do not refresh risk.

Remediate one risk

1. Open Risk Governance → Pending Risks. Switch among patch, host, and baseline views.
2. Confirm the item is a missing requirement from a current assessment. Unknown items are not listed.
3. Remediate now or in an execution window. The host must be bound to a baseline that contains the selected patch. A host cannot enter two immediate tasks at once.
4. For hosts waiting to reboot, create a separate reboot window. A reboot requires a window.
5. Open Risk Governance → Execution Records for progress, host stage, and logs.
6. Cancel only a host operation that has not been dispatched, and enter a reason. A dispatched operation is not interrupted.
7. Retry a failed, unknown, or unsatisfied host by selecting that target. After an install or reboot timeout, read the read-only check before installing again.

Optional scheduled assessment

1. Open Settings → Scan Settings.
2. Enable the schedule: hourly with at least one hour between runs, daily, or weekly. The schedule uses your time zone.
3. Optional: notify when non-compliant or failed hosts are found.
4. Turning the schedule off does not block a manual assessment from Home or a baseline.

Verify

• Home shows enrolled hosts, coverage of baseline-bound hosts, compliance, pending risk, and exceptions. The compliance rate counts only hosts with a definite result.
• Baseline detail can show the matrix by host or by patch, including failure reason and assessment time.
• After install and recheck, the host leaves pending risk or becomes satisfied.
• Export the loaded page of risks, or the aggregated items you selected. The workbook has a summary and details. The Export all button exports the loaded page, not every risk in the system. Execution records can also be exported within your permissions.