Skip to content

Security Compliance

SlimRMM includes a comprehensive CIS benchmark-based security compliance monitoring system to help ensure your endpoints meet industry security standards.

Overview

The compliance module continuously monitors your managed systems against the CIS Benchmarks, providing:

  • Real-time compliance scoring
  • Policy-based monitoring
  • Exception/waiver management
  • Historical trend analysis
  • Remediation guidance

CIS Benchmark Levels

Level 1 (Basic)

Recommended security settings that can be implemented without significant impact on system functionality:

  • Basic firewall configuration
  • Standard password policies
  • Common user account restrictions
  • Basic audit logging

Level 2 (Defense in Depth)

Advanced security settings for environments requiring enhanced security:

  • Strict firewall rules
  • Advanced encryption requirements
  • Comprehensive audit policies
  • Additional access restrictions

Check Categories

SlimRMM includes 30+ built-in checks across these categories:

CategoryDescriptionExample Checks
FirewallFirewall status and configurationFirewall enabled, profiles active
EncryptionDisk encryption statusBitLocker (Windows), FileVault (macOS), LUKS (Linux)
User AccountsAccount security settingsGuest account disabled, admin account restrictions
Password PolicyPassword requirementsComplexity, length, age, history
Remote AccessRemote access configurationSSH hardening, RDP restrictions
Audit LoggingSystem audit configurationAudit policy enabled, log retention
AntivirusMalware protection statusWindows Defender status, real-time protection
System UpdatesUpdate configurationAuto-updates enabled, pending updates

Scoring Algorithm

Compliance scores are calculated using a weighted severity system:

SeverityWeightDescription
Critical10Issues requiring immediate attention
High5Significant security concerns
Medium3Moderate security improvements
Low1Minor security enhancements

Score Calculation:

Score = (Passed Weight / Total Weight) * 100

Risk Level Assignment:

  • Critical: Any critical check failed
  • High: More than 2 high-severity checks failed
  • Medium: 1-2 high-severity or 5+ medium-severity checks failed
  • Low: All critical/high checks passed, few medium/low failures

Policies

Creating a Policy

Policies define which checks to run and against which agents:

json
{
  "name": "Windows Workstations - CIS Level 1",
  "cis_level": "level_1",
  "target_os": "windows",
  "schedule_type": "continuous",
  "check_interval_minutes": 60,
  "passing_score_threshold": 80
}

Policy Options

OptionDescription
cis_levellevel_1 or level_2
target_oswindows, darwin, linux, or all
schedule_typecontinuous, scheduled, or manual
check_interval_minutesHow often to run checks (default: 60)
passing_score_thresholdMinimum score to be considered compliant (default: 80)

Exceptions

For cases where a check cannot be satisfied due to business requirements, you can create exceptions:

  • Reason: Document why the exception is needed
  • Expiry: Optional expiration date
  • Scope: Per-agent or global

Excepted checks are marked as "Exempted" and excluded from scoring.

API Endpoints

Policies

MethodEndpointDescription
GET/api/v1/compliance/policiesList all policies
POST/api/v1/compliance/policiesCreate a policy
GET/api/v1/compliance/policies/{id}Get policy details
PUT/api/v1/compliance/policies/{id}Update a policy
DELETE/api/v1/compliance/policies/{id}Delete a policy

Checks

MethodEndpointDescription
GET/api/v1/compliance/checksList all checks
POST/api/v1/compliance/checks/seedImport built-in CIS checks

Results & Scores

MethodEndpointDescription
GET/api/v1/compliance/results/agent/{uuid}Get agent check results
GET/api/v1/compliance/score/agent/{uuid}Get agent compliance score
GET/api/v1/compliance/history/agent/{uuid}Get agent score history

Statistics

MethodEndpointDescription
GET/api/v1/compliance/statsOverall compliance statistics
GET/api/v1/compliance/trendCompliance trend data
GET/api/v1/compliance/stats/top-failingMost common failing checks

Dashboard

The compliance dashboard provides:

  • Overview Stats: Total agents, compliant percentage, average score
  • Risk Distribution: Chart showing agents by risk level
  • Category Breakdown: Compliance by check category
  • Top Failing Checks: Most common compliance issues
  • Non-Compliant Agents: List of agents needing attention
  • 30-Day Trend: Historical compliance scores

Agent View

Each agent's detail page includes a Compliance tab showing:

  • Current compliance score
  • Pass/fail status per check
  • Remediation guidance for failed checks
  • Score history graph
  • Exception management

Remediation

SlimRMM provides detailed remediation guidance for each failed check, including:

  • Description of the security issue
  • Impact of the misconfiguration
  • Steps to manually remediate
  • Command (where applicable) for reference

No Auto-Remediation

SlimRMM intentionally does not automatically remediate compliance issues. All changes must be reviewed and applied by an administrator to prevent unintended system modifications.

Best Practices

  1. Start with Level 1: Begin with CIS Level 1 checks before advancing to Level 2
  2. Review Exceptions: Regularly review and expire outdated exceptions
  3. Monitor Trends: Use the 30-day trend to track improvement
  4. Prioritize Critical: Address critical and high-severity issues first
  5. Document Exceptions: Always provide clear reasons for exceptions

Released under the MIT License.