{
  "slug": "security-projects",
  "topic": "Security projects",
  "status": "published",
  "order": 63,
  "capability": "leadership/projects",
  "title": "Security projects: how do you get a control to everyone, and into IT projects before go-live?",
  "short": "Set a coverage target such as 98% and dated exceptions before the pilot, run report-only for at least a week, and check IT projects at kickoff and before go-live.",
  "answer": "Before your next security rollout starts, write down its scope, a coverage target such as 98% of in-scope accounts enforced, and an end date for every exception, then run it in report-only or audit mode, a pilot and two or three rings. In the company's other IT projects, ask the security questions at kickoff and sign off before go-live, and scale the effort by protection need so only high-need projects wait for a full review.",
  "audience": "Heads of security, IT leads who own security, and project managers in small and mid-size companies",
  "version": "1.0",
  "lastReviewed": "2026-11-05",
  "reviewEveryDays": 30,
  "blocks": [
    {
      "type": "ranked",
      "id": "first",
      "title": "If you only do five things",
      "navTitle": "Five things",
      "items": [
        {
          "title": "Define done in numbers before you start.",
          "text": "Count the scope from the inventory and set a target, such as 98% of in-scope devices in block mode by 31 March, with an exception cap. Count enforced, not deployed."
        },
        {
          "title": "Watch before you enforce.",
          "text": "Keep a new Conditional Access policy in report-only mode for at least a week[^caplan]; it logs but blocks no one[^careport]. Audit ASR rules first, except the standard protection rules[^asrtest]."
        },
        {
          "title": "Roll out in rings sized for your help desk.",
          "text": "Pilot with IT and a champion per business unit, then a representative ring, then everyone, in waves within support capacity[^mfaplan]."
        },
        {
          "title": "Give every exception an end date.",
          "text": "Exclusion lists start short and grow[^caexcl]. Give each member of a policy's exclusion group a reason, an owner and an end date."
        },
        {
          "title": "Ask security at kickoff, not at go-live.",
          "text": "The BSI requires involving the ISB early in larger projects and new IT systems[^isms1]; Grundschutz++ requires a rule for when[^std3001]."
        }
      ]
    },
    {
      "type": "steps",
      "id": "rollout",
      "title": "Roll out a security change in this order",
      "navTitle": "Rollout",
      "items": [
        {
          "title": "Who and what is in scope?",
          "text": "Count from the inventory, not the new tool; Defender's device discovery (Plan 2) finds devices not yet onboarded[^discovery]. The security program sheet decides what goes first."
        },
        {
          "title": "What would break?",
          "text": "Run report-only or audit mode for one to four weeks and review the results with app owners. For segmentation, allow and log first, as the network segmentation sheet describes."
        },
        {
          "title": "Who pilots it?",
          "text": "IT and a champion per business unit[^asrtest], with a channel for problems. What they hit becomes the user message and the help desk script."
        },
        {
          "title": "When does the next ring start?",
          "text": "After a week with no open blocking tickets. Reuse your Windows update rings if you have them."
        },
        {
          "title": "When is it done?",
          "text": "When the tail is closed by name, the old path is gone, such as SMS codes, and an owner gets a monthly coverage report."
        }
      ]
    },
    {
      "type": "list",
      "id": "people",
      "title": "Users, help desk and rollback",
      "navTitle": "Help desk and rollback",
      "items": [
        "**Tell users what changes, when, and how to get help**[^caplan], a week before their ring and on the day.",
        "**Brief the help desk before each ring:** the script, known errors and what to collect, including the correlation ID from **More details**[^caplan].",
        "**Write the rollback first:** the trigger and the switch. Disable the CA policy or exclude a group[^caplan]. Exclude the app from ASR or return the rule to audit[^asrtest]. Pausing Intune deployments stops only later rings; revert the policy[^intune].",
        "**Exclude Mac, iOS and Android from report-only compliance policies,** or their users may get certificate prompts[^careport]. Test them in an enforced pilot.",
        "**In Germany, ask the works council early** about EDR, DLP and logging; it co-determines systems designed to monitor behavior or performance[^betrvg]."
      ]
    },
    {
      "type": "list",
      "id": "exceptions",
      "title": "Exceptions that end",
      "navTitle": "Exceptions",
      "items": [
        "**Exclude groups, not people.** One assigned Entra group per policy shows who is excluded[^caexcl]; break-glass accounts go in every one[^caplan].",
        "**Record why, what instead and until when:** a reason, a compensating control, an owner and an end date per member. Approval levels are in the risk register sheet.",
        "**Let reviews remove people.** Entra access reviews can ask members weekly and remove those who don't answer (Entra ID P2 or ID Governance)[^caexcl].",
        "**Cap them.** Our rule: at most 2% of the scope at go-live; any still open at the done date is renewed one level up, as in the risk register sheet. Report the count and the oldest monthly."
      ]
    },
    {
      "type": "list",
      "id": "adoption",
      "title": "Measure adoption against the inventory",
      "navTitle": "Adoption",
      "items": [
        "**Coverage is enforced over in scope,** counted weekly from the inventory by ring and business unit, with the tail named.",
        "**MFA and passkeys.** Entra's **Authentication methods** > **Activity** lists who is MFA or passwordless capable and counts single-factor sign-ins[^authact].",
        "**Conditional Access.** The gap analyzer workbook lists sign-ins no policy applied to (P1 and Log Analytics)[^gap].",
        "**EDR and ASR.** Compare onboarded with discovered devices[^discovery]; the ASR report needs Plan 2 or Defender for Business, else forward event 1122[^asrtest]."
      ]
    },
    {
      "type": "list",
      "id": "mistakes",
      "title": "Mistakes that cost the most",
      "navTitle": "Mistakes",
      "items": [
        "**Stopping at 80%.** The tail holds the old devices, service accounts and executives. Give it its own phase and owners.",
        "**Exceptions that become permanent.** Exclusions without an end date outlive their reason. Let them expire unless someone renews them.",
        "**No owner after go-live.** Conditional Access policies have no owner field, so Microsoft suggests putting it in the name and keeping a register[^caplan].",
        "**Piloting only in IT.** IT and lab devices usually lack a representative mix of apps and drivers[^rings]."
      ]
    },
    {
      "type": "list",
      "id": "gates",
      "title": "Security gates in IT and business projects",
      "navTitle": "Project gates",
      "items": [
        "**At kickoff, ask six questions:** what data, who signs in and how, internet-facing or not, which supplier, who gets admin rights, when it goes live.",
        "**Rate the processes the system serves: normal or high.** Grundschutz++ sets these two; on its catalog, high need adds a risk analysis[^std3001].",
        "**Write requirements into the plan.** Normal: SSO with MFA, exportable logs, named admins, backups, patch deadlines. High: add a design review. Software you build: see the secure development sheet.",
        "**Pentest at go-live** if the system faces the internet, has high need, is custom-built or changes sign-in; ENISA advises testing at set-up[^enisatig]. Otherwise scan and check settings. See the penetration testing sheet.",
        "**Sign off.** Security confirms each requirement or lists open items with owners and dates; management approves the risk of unmet ones, which Grundschutz++ rules out for MUSS requirements[^std3001]."
      ]
    },
    {
      "type": "list",
      "id": "tenders",
      "title": "Security in tenders and contracts",
      "navTitle": "Tenders",
      "items": [
        "**Use the six NIS2 purchasing points:** security requirements, updates for the whole lifetime or replacement after support ends, component information, security functions and secure configuration, assurance, and how you validate it[^enisatig]. They bind digital providers; in Germany, BSIG § 30(2) no. 5 requires security in acquisition of all NIS2 entities[^bsig30].",
        "**Ask when support ends.** From 11 December 2027, the CRA requires makers of new products to state the month and year at purchase[^craguide].",
        "**Require free, prompt fixes,** tested and delivered as soon as an issue is known, as ENISA advises[^enisatig].",
        "**Tie acceptance to evidence.** Make acceptance and the final payment depend on SSO and MFA working, logs flowing and critical pentest findings fixed. Add the third-party risk sheet's clauses."
      ]
    },
    {
      "type": "list",
      "id": "bottleneck",
      "title": "Don't become the bottleneck",
      "navTitle": "Bottleneck",
      "items": [
        "**Publish when security joins.** Grundschutz++ doesn't need the ISB active in every security-relevant project[^std3001]. Join the high-need ones.",
        "**Promise a turnaround,** such as the operating model sheet's 5 working days. If you miss it, normal-need projects go ahead and log open items.",
        "**Pre-approve patterns:** a SaaS requirement set, a contract annex, a reference design.",
        "**Put a champion in the PMO** to ask the kickoff questions and call you in for high-need projects."
      ]
    },
    {
      "type": "list",
      "id": "skip",
      "title": "What you can skip",
      "items": [
        "**A risk analysis for every project.** With the Grundschutz++ catalog, normal need requires none unless a requirement stays unmet[^std3001].",
        "**A pentest at every go-live.** A standard SaaS app behind SSO needs a check of your tenant's configuration.",
        "**Auditing the standard ASR rules.** Microsoft says they can typically go to block or warn without testing[^asrtest].",
        "**Months in report-only.** Our limit: a week to a month of real sign-ins. Enforce, then fix the tail."
      ]
    },
    {
      "type": "list",
      "id": "changed",
      "title": "What changed in 2026",
      "navTitle": "What changed",
      "span": "full",
      "items": [
        "**Intune stages policy rollouts.** Deployment plans, in preview since September 2026[^intunenew], push Windows policies and apps ring by ring and can be paused[^intune].",
        "**Grundschutz++ wants a project rule.** BSI-Standard 300-1 (20 October 2026) requires a security role in relevant projects and a rule for when[^std3001].",
        "**CRA support periods got clearer.** The Commission's draft CRA guidance of 27 July 2026 says the five-year minimum isn't a default[^craguide]."
      ]
    },
    {
      "type": "columns",
      "id": "by-size",
      "title": "What this looks like at your size",
      "navTitle": "By team size",
      "span": "full",
      "columns": [
        {
          "title": "Small team, no security staff",
          "items": [
            "The IT lead or provider runs rollouts; a managing director approves exceptions.",
            "Pilot with two or three users, then everyone.",
            "Check IT purchases against the six NIS2 points."
          ]
        },
        {
          "title": "Growing, with IT or security staff",
          "items": [
            "Write one page per rollout: scope, target, rings, rollback, exceptions, owner.",
            "Report coverage at the program's monthly meeting.",
            "Ask the kickoff questions in every IT project."
          ]
        },
        {
          "title": "Enterprise or regulated",
          "items": [
            "Ring by region or site, and hold mission-critical devices until last[^rings].",
            "Make security sign-off a gate in the project method.",
            "Put a security annex in every IT tender template."
          ]
        }
      ]
    }
  ],
  "changes": [
    {
      "date": "2026-11-05",
      "version": "1.0",
      "text": "Published after a copy edit and a source-by-source fact check, which made the rollback steps real rollbacks, added break-glass exclusions and Defender license needs, aligned exceptions with the risk register and scoped the Grundschutz++ and CRA claims to what the sources say."
    },
    {
      "date": "2026-11-05",
      "version": "0.1",
      "text": "First draft, based on Microsoft Learn rollout guides, BSI ISMS.1 and 300-1, ENISA's NIS2 guidance and the CRA guidance."
    }
  ],
  "sources": [
    {
      "id": "caplan",
      "title": "Plan a Conditional Access deployment",
      "publisher": "Microsoft Learn",
      "date": "1 Jun 2026",
      "url": "https://learn.microsoft.com/en-us/entra/identity/conditional-access/plan-conditional-access"
    },
    {
      "id": "careport",
      "title": "Conditional Access policy insights",
      "publisher": "Microsoft Learn",
      "date": "1 Jun 2026",
      "url": "https://learn.microsoft.com/en-us/entra/identity/conditional-access/concept-conditional-access-report-only"
    },
    {
      "id": "asrtest",
      "title": "Test your ASR rules deployment",
      "publisher": "Microsoft Learn",
      "date": "2 Jul 2026",
      "url": "https://learn.microsoft.com/en-us/defender-endpoint/attack-surface-reduction-rules-deployment-test"
    },
    {
      "id": "rings",
      "title": "Create a deployment plan (Windows)",
      "publisher": "Microsoft Learn",
      "date": "31 Dec 2017",
      "url": "https://learn.microsoft.com/en-us/windows/deployment/update/create-deployment-plan"
    },
    {
      "id": "mfaplan",
      "title": "Deployment considerations for Entra MFA",
      "publisher": "Microsoft Learn",
      "date": "2 Nov 2025",
      "url": "https://learn.microsoft.com/en-us/entra/identity/authentication/howto-mfa-getstarted"
    },
    {
      "id": "intune",
      "title": "Create and manage an Intune deployment",
      "publisher": "Microsoft Learn",
      "date": "26 Aug 2026",
      "url": "https://learn.microsoft.com/en-us/intune/device-management/deployments/create-deployment"
    },
    {
      "id": "intunenew",
      "title": "What's new in Microsoft Intune",
      "publisher": "Microsoft Learn",
      "date": "2 Nov 2026",
      "url": "https://learn.microsoft.com/en-us/intune/whats-new/"
    },
    {
      "id": "discovery",
      "title": "Defender device discovery overview",
      "publisher": "Microsoft Learn",
      "date": "8 May 2025",
      "url": "https://learn.microsoft.com/en-us/defender-endpoint/device-discovery"
    },
    {
      "id": "authact",
      "title": "Authentication Methods Activity",
      "publisher": "Microsoft Learn",
      "date": "22 Oct 2025",
      "url": "https://learn.microsoft.com/en-us/entra/identity/authentication/howto-authentication-methods-activity"
    },
    {
      "id": "gap",
      "title": "Conditional Access gap analyzer workbook",
      "publisher": "Microsoft Learn",
      "date": "4 Nov 2024",
      "url": "https://learn.microsoft.com/en-us/entra/identity/monitoring-health/workbook-conditional-access-gap-analyzer"
    },
    {
      "id": "caexcl",
      "title": "Manage users excluded from CA policies",
      "publisher": "Microsoft Learn",
      "date": "18 Jun 2025",
      "url": "https://learn.microsoft.com/en-us/entra/id-governance/conditional-access-exclusion"
    },
    {
      "id": "betrvg",
      "title": "BetrVG, § 87",
      "publisher": "Gesetze im Internet",
      "date": "checked 5 Nov 2026",
      "url": "https://www.gesetze-im-internet.de/betrvg/__87.html"
    },
    {
      "id": "isms1",
      "title": "ISMS.1 Sicherheitsmanagement",
      "publisher": "BSI",
      "date": "Edition 2023",
      "url": "https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/Grundschutz/IT-GS-Kompendium_Einzel_PDFs_2023/01_ISMS_Sicherheitsmanagement/ISMS_1_Sicherheitsmanagement_Edition_2023.pdf?__blob=publicationFile&v=3"
    },
    {
      "id": "std3001",
      "title": "BSI-Standard 300-1 (Grundschutz++)",
      "publisher": "BSI",
      "date": "20 Oct 2026",
      "url": "https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/Grundschutz/BSI_Standards/standard_300-1.pdf?__blob=publicationFile&v=3"
    },
    {
      "id": "enisatig",
      "title": "NIS2 implementation guidance",
      "publisher": "ENISA",
      "date": "26 Jun 2025",
      "url": "https://www.enisa.europa.eu/sites/default/files/2025-06/ENISA_Technical_implementation_guidance_on_cybersecurity_risk_management_measures_version_1.0.pdf"
    },
    {
      "id": "craguide",
      "title": "CRA guidance, C(2026) 5252",
      "publisher": "European Commission",
      "date": "27 Jul 2026",
      "url": "https://digital-strategy.ec.europa.eu/en/library/commission-publishes-new-guidance-support-timely-cyber-resilience-act-implementation"
    },
    {
      "id": "bsig30",
      "title": "BSIG, § 30",
      "publisher": "Gesetze im Internet",
      "date": "checked 5 Nov 2026",
      "url": "https://www.gesetze-im-internet.de/bsig_2025/__30.html"
    }
  ]
}