fix(ui): handle level 1 requirements for M365 CIS (#11921)

This commit is contained in:
Pedro Martín
2026-07-09 16:41:51 +02:00
committed by GitHub
parent 0b36d08b92
commit 01c004a7af
3 changed files with 7 additions and 3 deletions
@@ -0,0 +1 @@
CIS Level 1 and Level 2 compliance filters now match profiles prefixed with a license tier (e.g. "E3 Level 1"), so M365 CIS requirements are no longer hidden
+5 -2
View File
@@ -38,8 +38,11 @@ export const mapComplianceData = (
const attrs = metadataArray?.[0];
if (!attrs) continue;
// Apply profile filter
if (filter === "Level 1" && attrs.Profile !== "Level 1") {
// Apply profile filter.
// Most CIS benchmarks use "Level 1"/"Level 2" as the Profile, but some
// (e.g. M365) prefix it with the license tier: "E3 Level 1", "E5 Level 2".
// Match by suffix so the Level 1 filter works across all CIS variants.
if (filter === "Level 1" && !attrs.Profile?.endsWith("Level 1")) {
continue; // Skip Level 2 requirements when Level 1 is selected
}
+1 -1
View File
@@ -127,7 +127,7 @@ export interface ISO27001AttributesMetadata {
export interface CISAttributesMetadata {
Section: string;
SubSection: string | null;
Profile: string; // "Level 1" or "Level 2"
Profile: string; // "Level 1"/"Level 2" (M365 prefixes the tier: "E3 Level 1", "E5 Level 2")
AssessmentStatus: string; // "Manual" or "Automated"
Description: string;
RationaleStatement: string;