{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-069-choose-notification-or-enforcement-when-creating-an-fsrm-file-screen/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-069-choose-notification-or-enforcement-when-creating-an-fsrm-file-screen/", "slug": "dse-20260908-069-choose-notification-or-enforcement-when-creating-an-fsrm-file-screen", "url": "https://update.dsesecurity.com/updates/dse-20260908-069-choose-notification-or-enforcement-when-creating-an-fsrm-file-screen/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-069-choose-notification-or-enforcement-when-creating-an-fsrm-file-screen.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-069-choose-notification-or-enforcement-when-creating-an-fsrm-file-screen/" }, "title": "Choose notification or enforcement when creating an FSRM file screen", "summary": "Should an FSRM file screen block matching files or only report them?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "continuity-recovery", "label": "Continuity & recovery", "alt": "Paired infrastructure paths converging on a stable recovered service.", "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "business-continuity", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-08T18:16:02+00:00", "modified_at": "2026-09-08T18:20:22+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 215, "potentially_affected": "Use this review when creating a screen for a defined file-service policy.", "dse_recommendation": "Prepare examples of files that should match and files that should remain unaffected.", "primary_source": { "name": "Create a File Screen", "url": "https://learn.microsoft.com/en-us/windows-server/storage/fsrm/create-file-screen", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

Microsoft distinguishes active file screening, which prevents saving files in blocked groups and can notify administrators, from passive screening, which sends configured notifications without blocking the save. A file screen applies to its selected folder and all subfolders. A template can retain a relationship with derived screens so later template changes can be applied to them. Microsoft documentation.

\n

Applicability

\n

Use this review when creating a screen for a defined file-service policy. Identify the folder tree, file groups, notification recipients, and data owner. Choose the behavior deliberately before configuring the screen.

\n

DSE recommendation

\n

Prepare examples of files that should match and files that should remain unaffected. Have the owner decide whether the first deployment should observe activity or prevent it. Review inherited template relationships alongside the folder scope. Tell support staff what users should experience and who will review the notifications, and preserve the original configuration before enabling enforcement.

\n

Verification

\n

Test matching and nonmatching files in the selected folder and a representative subfolder. Record whether saving was allowed and whether the expected notification arrived. Inspect a location outside the scope to confirm the intended boundary. Reconcile incorrect matches or missing notifications before broadening the screen or switching from passive observation to active blocking.

\n

Official references

\n

Microsoft Learn: Create a File Screen. Source reviewed September 8, 2026.

", "content_text": "Source facts\nMicrosoft distinguishes active file screening, which prevents saving files in blocked groups and can notify administrators, from passive screening, which sends configured notifications without blocking the save. A file screen applies to its selected folder and all subfolders. A template can retain a relationship with derived screens so later template changes can be applied to them. Microsoft documentation.\nApplicability\nUse this review when creating a screen for a defined file-service policy. Identify the folder tree, file groups, notification recipients, and data owner. Choose the behavior deliberately before configuring the screen.\nDSE recommendation\nPrepare examples of files that should match and files that should remain unaffected. Have the owner decide whether the first deployment should observe activity or prevent it. Review inherited template relationships alongside the folder scope. Tell support staff what users should experience and who will review the notifications, and preserve the original configuration before enabling enforcement.\nVerification\nTest matching and nonmatching files in the selected folder and a representative subfolder. Record whether saving was allowed and whether the expected notification arrived. Inspect a location outside the scope to confirm the intended boundary. Reconcile incorrect matches or missing notifications before broadening the screen or switching from passive observation to active blocking.\nOfficial references\nMicrosoft Learn: Create a File Screen. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft distinguishes active file screening, which prevents saving files in blocked groups and can notify administrators, from passive screening, which sends configured notifications without blocking the save. A file screen applies to its selected folder and all subfolders. A template can retain a relationship with derived screens so later template changes can be applied to them. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/storage/fsrm/create-file-screen).\n\n## Applicability\n\nUse this review when creating a screen for a defined file-service policy. Identify the folder tree, file groups, notification recipients, and data owner. Choose the behavior deliberately before configuring the screen.\n\n## DSE recommendation\n\nPrepare examples of files that should match and files that should remain unaffected. Have the owner decide whether the first deployment should observe activity or prevent it. Review inherited template relationships alongside the folder scope. Tell support staff what users should experience and who will review the notifications, and preserve the original configuration before enabling enforcement.\n\n## Verification\n\nTest matching and nonmatching files in the selected folder and a representative subfolder. Record whether saving was allowed and whether the expected notification arrived. Inspect a location outside the scope to confirm the intended boundary. Reconcile incorrect matches or missing notifications before broadening the screen or switching from passive observation to active blocking.\n\n## Official references\n\n[Microsoft Learn: Create a File Screen](https://learn.microsoft.com/en-us/windows-server/storage/fsrm/create-file-screen). Source reviewed September 8, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260908-069-choose-notification-or-enforcement-when-creating-an-fsrm-file-screen/", "url": "https://update.dsesecurity.com/updates/dse-20260908-069-choose-notification-or-enforcement-when-creating-an-fsrm-file-screen/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-069-choose-notification-or-enforcement-when-creating-an-fsrm-file-screen/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Choose notification or enforcement when creating an FSRM file screen", "item": "https://update.dsesecurity.com/updates/dse-20260908-069-choose-notification-or-enforcement-when-creating-an-fsrm-file-screen/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-069-choose-notification-or-enforcement-when-creating-an-fsrm-file-screen/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-069-choose-notification-or-enforcement-when-creating-an-fsrm-file-screen/", "url": "https://update.dsesecurity.com/updates/dse-20260908-069-choose-notification-or-enforcement-when-creating-an-fsrm-file-screen/", "headline": "Choose notification or enforcement when creating an FSRM file screen", "description": "Should an FSRM file screen block matching files or only report them?", "abstract": "Should an FSRM file screen block matching files or only report them?", "articleBody": "Source facts\nMicrosoft distinguishes active file screening, which prevents saving files in blocked groups and can notify administrators, from passive screening, which sends configured notifications without blocking the save. A file screen applies to its selected folder and all subfolders. A template can retain a relationship with derived screens so later template changes can be applied to them. Microsoft documentation.\nApplicability\nUse this review when creating a screen for a defined file-service policy. Identify the folder tree, file groups, notification recipients, and data owner. Choose the behavior deliberately before configuring the screen.\nDSE recommendation\nPrepare examples of files that should match and files that should remain unaffected. Have the owner decide whether the first deployment should observe activity or prevent it. Review inherited template relationships alongside the folder scope. Tell support staff what users should experience and who will review the notifications, and preserve the original configuration before enabling enforcement.\nVerification\nTest matching and nonmatching files in the selected folder and a representative subfolder. Record whether saving was allowed and whether the expected notification arrived. Inspect a location outside the scope to confirm the intended boundary. Reconcile incorrect matches or missing notifications before broadening the screen or switching from passive observation to active blocking.\nOfficial references\nMicrosoft Learn: Create a File Screen. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:16:02+00:00", "dateModified": "2026-09-08T18:20:22+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-069-choose-notification-or-enforcement-when-creating-an-fsrm-file-screen/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260908-069-choose-notification-or-enforcement-when-creating-an-fsrm-file-screen/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Choose notification or enforcement when creating an FSRM file screen" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 215, "timeRequired": "PT1M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Create a File Screen", "url": "https://learn.microsoft.com/en-us/windows-server/storage/fsrm/create-file-screen" } } ] } }