https://docs.sysward.com/docs/using-sysward/Recent content in Using SysWard onHugo -- gohugo.ioen-USThu, 09 Jul 2026 00:00:00 +0000https://docs.sysward.com/docs/using-sysward/dashboard/Tue, 13 Oct 2020 15:21:01 +0200https://docs.sysward.com/docs/using-sysward/dashboard/The dashboard gives you an at-a-glance view of your fleet’s patch and vulnerability status. It has three parts. Summary cards The cards across the top show the totals that matter most. Each one is also a shortcut — click the number to jump straight to the Agents list pre-filtered to those servers: Security Updates — servers with pending security patches Regular Updates — servers with pending non-security updates Dead Agents — agents that haven’t checked in within your organization’s dead-agent timeout (configurable on the Organization page) Job Failures — jobs that didn’t complete successfully Patches By Group This chart breaks pending security vs.https://docs.sysward.com/docs/using-sysward/agents/Tue, 13 Oct 2020 15:21:01 +0200https://docs.sysward.com/docs/using-sysward/agents/The agents list The Agents page lists every server reporting to SysWard. Filter to find a specific host, and see each one’s OS, hostname, group, update counts (security / regular / CVE), IP address, whether a reboot is required, CPU count, memory, agent version, and last check-in. Reassign a server’s group inline, or remove a host with the Delete action. Agent details Select a hostname to open its detail view, organized into tabs.https://docs.sysward.com/docs/using-sysward/groups/Tue, 13 Oct 2020 15:21:01 +0200https://docs.sysward.com/docs/using-sysward/groups/Groups let you organize your servers so you can view, patch, and report on related machines together (for example by environment, role, or team). The Groups page lists every group with the number of agents in it. Create a group with New Group and give it a name. Assign servers to it from the Agents list or the dashboard using the inline group dropdown, and remove a group with Delete.https://docs.sysward.com/docs/using-sysward/packages/Tue, 13 Oct 2020 15:21:01 +0200https://docs.sysward.com/docs/using-sysward/packages/The Packages page is a fleet-wide inventory of the packages installed across your servers — useful for verifying which hosts are running a vulnerable package. Each row shows: Name — the package Current — the version currently installed Candidate — the version available to upgrade to, if any Hosts — how many servers have the package installed Groups — the groups those servers belong to Select one or more packages and choose Upgrade to queue the upgrade across every host that has them.https://docs.sysward.com/docs/using-sysward/cves/Tue, 13 Oct 2020 15:21:01 +0200https://docs.sysward.com/docs/using-sysward/cves/The CVE Alerts page lists every known vulnerability affecting the packages installed across your infrastructure. Each row shows: Agent — the affected server Package and Version — the vulnerable package and its installed version CVE — the identifier, linked to its public advisory (opens in a new tab) Severity — Critical, High, Medium, or Low First Seen — when SysWard first detected it Use the Filter box to narrow the list by host, package, or CVE.https://docs.sysward.com/docs/using-sysward/remediation/Thu, 09 Jul 2026 00:00:00 +0000https://docs.sysward.com/docs/using-sysward/remediation/SysWard turns “these servers are vulnerable” into “these servers are patched.” Here’s the end-to-end workflow. 1. Find what’s vulnerable The CVEs page lists every vulnerability across your fleet; select a CVE to see every affected host. An individual server’s CVE tab shows just that host’s vulnerabilities. The Packages page shows which packages have a newer candidate version available. 2. Apply a fix Queue an upgrade from wherever you’re working: From a CVE — click Upgrade on a CVE row to patch the affected package on that host.https://docs.sysward.com/docs/using-sysward/scheduled_jobs/Tue, 13 Oct 2020 15:21:01 +0200https://docs.sysward.com/docs/using-sysward/scheduled_jobs/The Scheduled Jobs page lists every job across your infrastructure — the upgrades you queue from the CVEs, Packages, and Agents pages all land here. Each row shows: ID — the job identifier Agent — the target server Package — the package the job acts on Scheduled For — when the job is set to run Status — pending, running, completed, or failed Scheduled By — the user who queued it Use Cancel in the Actions column to stop a job that hasn’t run yet.https://docs.sysward.com/docs/using-sysward/history/Thu, 09 Jul 2026 00:00:00 +0000https://docs.sysward.com/docs/using-sysward/history/SysWard keeps an audit trail of what happened across your fleet — the jobs that ran, the events detected, and who initiated each one. History is available at three levels: Per agent — the History tab on an agent’s detail page. Per group — the history on a group’s overview. Fleet-wide — the history shown on the dashboard. Each entry shows: Type — the kind of event (for example a detected CVE, an upgrade, or a check-in) Description — what happened Date — when it happened User — who performed it Who performed an action The User column attributes each action: