{"id":1384,"date":"2026-11-16T14:30:00","date_gmt":"2026-11-16T14:30:00","guid":{"rendered":"https:\/\/cotocus.org\/blog\/?p=1384"},"modified":"2026-11-19T04:30:00","modified_gmt":"2026-11-19T04:30:00","slug":"linux-host-sysops-audit-checklist","status":"publish","type":"post","link":"https:\/\/cotocus.org\/blog\/linux-host-sysops-audit-checklist\/","title":{"rendered":"A Practical SysOps Audit Checklist for a Single Linux Host"},"content":{"rendered":"<p>This is an audit you can finish in an afternoon. Pick one Linux host, ideally a mid-importance one, and work down the list. Each item states what to check and what a bad answer looks like. By closing time you should hold a short, written, risk-ranked list of fixes. The structure follows the scope that the Ops Atlas assigns to SysOps in <a href=\"https:\/\/www.xopsschool.com\/sysops\/\">its reference page on the discipline<\/a>: services, privileges, remote access, logs, timers, packages, filesystems, time, the host firewall, backups and triage.<\/p>\n<h2>Before you start<\/h2>\n<ul>\n<li>Open a second session on the host and leave it open. If a check requires a reload, you want a way back in.<\/li>\n<li>Create a scratch file for findings. Record the command, the result and your verdict.<\/li>\n<li>Do not change anything during the first pass. Look, note, then fix in a second pass.<\/li>\n<\/ul>\n<h2>Section A: access and privilege<\/h2>\n<ul>\n<li>List accounts that can log in. Any shared or unnamed account is a finding.<\/li>\n<li>Run the dump of effective remote-login settings from the daemon&#8217;s test mode and compare it with what you think you configured. In this daemon the first value usually wins, so a stray early line can override a careful later one.<\/li>\n<li>Confirm that password login and direct administrator login are off, if your policy says so.<\/li>\n<li>Inspect the sudo rules directory. Files must be mode 0440, and any file with a dot in its name is skipped silently. Run the editor&#8217;s check mode, which also verifies ownership.<\/li>\n<li>Where the host is reached through a cloud session service, confirm that the default shared user has been replaced by per-person run-as settings.<\/li>\n<\/ul>\n<h2>Section B: scheduled work<\/h2>\n<ul>\n<li>List every cron entry and every active timer. Note who owns each one.<\/li>\n<li>Search cron lines for a bare percent sign; it will be treated as a newline.<\/li>\n<li>For each important job, find the last successful run. A job with no recorded success is a finding, even if it has no recorded failure.<\/li>\n<li>For timers, check for persistence, a randomised delay and a failure hook. Missing ones are improvements, not emergencies.<\/li>\n<\/ul>\n<h2>Section C: logs and time<\/h2>\n<ul>\n<li>Check the journal&#8217;s storage setting. If it is unset, the effective behaviour depends on whether a persistent directory exists.<\/li>\n<li>Check the size cap. By default the journal may take up to a tenth of the filesystem and leaves a larger share free.<\/li>\n<li>Review log rotation. Copy-and-truncate rotation can lose a very small slice of lines.<\/li>\n<li>Run the time service&#8217;s status. Is it synchronised? Is the offset small? What is the policy for large corrections?<\/li>\n<\/ul>\n<h2>Section D: packages and restarts<\/h2>\n<ul>\n<li>List pending updates and the oldest one outstanding.<\/li>\n<li>Check whether a restart is owed: the Red Hat family helper returns exit code one when it is, and Ubuntu leaves a marker file.<\/li>\n<li>Know your undo. dnf can reverse a transaction from its history; apt cannot, and you would pin an older version.<\/li>\n<li>Validate the mount table and test mounting everything before the next reboot.<\/li>\n<li>Look up the end-of-support date of the operating system release and write it down.<\/li>\n<\/ul>\n<h2>Section E: protection layers<\/h2>\n<ul>\n<li>Is the host firewall on, and does the rule set match the services the host should expose?<\/li>\n<li>Is SELinux or AppArmor in enforcing mode? Any host-wide permissive setting is a finding. Per-domain or per-profile exceptions are acceptable if they are documented.<\/li>\n<li>For firewall edits, confirm there is a procedure that reverts automatically unless you confirm the change.<\/li>\n<\/ul>\n<h2>Section F: capacity and limits<\/h2>\n<ul>\n<li>For each filesystem, compute days of runway from the growth rate, including the share reserved for the administrator. As a worked case, a 500 GiB volume with 410 GiB used and 9 GiB daily growth has about seven days, not ten.<\/li>\n<li>Check the open-file limit of the busiest services. The default soft limit is 1,024.<\/li>\n<li>If a process has been tuned so the kernel will never kill it, note it: the Atlas warns that this only shifts the kill elsewhere.<\/li>\n<\/ul>\n<h2>Section G: recovery<\/h2>\n<ul>\n<li>Find the last backup and the last test restore. No test means the backup is unproven.<\/li>\n<li>Confirm that snapshots are not being counted as backups.<\/li>\n<li>Check that you can reach the machine without its network, through a console path, and that any disk-encryption recovery keys are stored somewhere other than on the machine.<\/li>\n<\/ul>\n<h2>Section H: triage readiness<\/h2>\n<ul>\n<li>Is there a script, stored with the runbook, that prints load, memory, disk, network and top-process data in a fixed order? If not, write one.<\/li>\n<li>Is historical performance data being collected, so a bad hour can be compared with a good one?<\/li>\n<li>Do alerts fire on a few signals tied to user pain, rather than on dozens of raw counters?<\/li>\n<li>Would the on-call person know not to restart first? Add the sentence to the runbook if not.<\/li>\n<\/ul>\n<h2>Readings that trigger false alarms<\/h2>\n<p>An audit also needs a short list of things that look wrong and are not. A load figure higher than the number of processors may reflect tasks waiting on storage, not saturated processors. A small amount of free memory is normal because the system caches aggressively; judge by the available-memory figure. A disk showing full busy time on flash storage or a striped array may still have headroom. Write these false alarms next to the finding they could be mistaken for, so the next auditor does not spend an hour on them.<\/p>\n<h2>How to write up a finding<\/h2>\n<p>Keep each finding to four lines: what you saw, why it matters, the smallest safe fix and who owns it. Avoid language such as &#8220;should be improved&#8221;. Say &#8220;remove the shared login by the end of the month&#8221; and name the person. Findings written this way get closed; findings written as essays get filed.<\/p>\n<h2>Scoring and follow-up<\/h2>\n<p>Tally findings by section and rank them: access problems first, because they widen every other risk; unproven recovery second; drift and housekeeping after. The Atlas suggests a handful of measures for tracking progress over time: baseline conformance, monitoring coverage, scheduled-job success, disk runway, reboot debt, toil share and end-of-life exposure. Pick three and record them monthly.<\/p>\n<p>If your team also runs automated incident tooling, two related reads on this site cover the response side of the picture: how <a href=\"https:\/\/cotocus.org\/blog\/mastering-incident-management-with-aiops-for-faster-resolution\/\">smarter incident handling speeds up resolution<\/a> and a <a href=\"https:\/\/cotocus.org\/blog\/aiops-roadmap-a-practical-guide-for-devops-sre-and-operations-teams\/\">practical roadmap for operations teams adopting automation<\/a>. Use them to decide where host findings should feed alerts.<\/p>\n<p>Repeat the audit on a different host next week. By the fourth round you will have a feel for the typical failure patterns, and a standard template for the rest of the estate.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>One afternoon, one host, thirty checks. Work through access, scheduling, logs, updates, firewall, performance and recovery, and leave with a written list of fixes.<\/p>\n","protected":false},"author":4,"featured_media":1385,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[130],"tags":[],"class_list":["post-1384","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-it-operations"],"_links":{"self":[{"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/posts\/1384","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/comments?post=1384"}],"version-history":[{"count":1,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/posts\/1384\/revisions"}],"predecessor-version":[{"id":1501,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/posts\/1384\/revisions\/1501"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/media\/1385"}],"wp:attachment":[{"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/media?parent=1384"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/categories?post=1384"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/tags?post=1384"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}