Sekit CSF · Vulnerability & Configuration · Process
RCF-0227Baseline compliance
Baseline compliance is consistently monitored and non-compliant systems are remediated within agreed timelines
Mapping at a glance
RCF-0227Baseline complianceVulnerability & Configuration · Process
RCF-0227 maps to 7 controls across the published frameworks. +2 more in the table below. Open in the full graph →
Maps to ISO/IEC 27001:2022
Curated mapping with the reasoning, not just the codes.
A.5.36Compliance with policies, rules and standards for information securitysupportsThis process control monitors baseline compliance continuously and brings non-compliant systems back within standard inside the agreed window, matching A.5.36's requirement to follow up on non-compliance.A.8.9Configuration managementsupportsMonitoring baseline compliance continuously and bringing non-compliant systems back within the standard inside an agreed window closes the loop A.8.9 requires.
Maps to NIST CSF 2.0
Curated mapping with the reasoning, not just the codes.
ID.RA-01Vulnerabilities identified and recordedPR.PS-01Configuration management appliedPR.PS-02Software maintained
Maps to Cyber Essentials
Curated mapping with the reasoning, not just the codes.
Evidence that proves this control
What an auditor, or Sekit's evidence engine, asks for.
Device hardening baseline
The secure-configuration standard applied to devices when handed out (default settings, disabled services) and how compliance is checked.
From the Sekit evidence catalog
This topic through the other lenses
All Vulnerability & Configuration controls
Ask Sekura: “What evidence proves RCF-0227?”
Also via MCP, free with account