/en/tags/compliance/Recent content in Compliance on Mi&Bee BlogHugo -- gohugo.ioen蓝宝石的傻话Thu, 21 May 2026 00:00:00 +0000/en/posts/telemetry/security-collector-exporter-from-compliance-to-runtime/Thu, 21 May 2026 00:00:00 +0000/en/posts/telemetry/security-collector-exporter-from-compliance-to-runtime/<h2 id="the-origin-compliance-check-hassles">The Origin: Compliance Check Hassles</h2> <p>Anyone in operations knows there&rsquo;s no escaping one hurdle for domestic servers: <strong>Cybersecurity Level Protection</strong> (GB/T 22239-2019, commonly known as &ldquo;Level Protection 2.0&rdquo;). Whether you&rsquo;re Level 3 or Level 2, auditors come asking about these things:</p> <ul> <li>Is SSH root login disabled? Are password policies compliant?</li> <li>Is the firewall on? Is SELinux enforcing?</li> <li>Are there expired accounts? What&rsquo;s the password validity period?</li> <li>Which ports are open? Are there high-risk services running?</li> <li>Are audit logs enabled? How long are they retained?</li> </ul> <p>There are plenty of compliance check tools on the market—search GitHub and you&rsquo;ll find a bunch: <code>Golin</code>, <code>EvaluationTools</code>, <code>Linux-Security-Compliance-Check</code>, etc. But they all share one limitation: <strong>Run once, get a report, done</strong>. You check compliance today, and someone changes <code>sshd_config</code> tomorrow, turns off the firewall, installs a backdoor service—you&rsquo;d never know.</p>