Sekit CSF · Vulnerability & Configuration · Policy
RCF-0226Baseline compliance
The company formally measures compliance of all systems against approved security configuration baselines
Mapping at a glance
RCF-0226Baseline complianceVulnerability & Configuration · Policy
RCF-0226 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.1Policies for information securitysupportsAmong A.5.1's topic-specific policies, Sekit's Baseline compliance policy commits to measuring what share of systems meet approved baselines and reporting that figure to management.A.8.9Configuration managementsupportsCommitting to measure what share of systems meet approved baselines and report that to management operationalizes A.8.9's configuration standard into a tracked metric.
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-0226?”
Also via MCP, free with account