# Choose notification or enforcement when creating an FSRM file screen

> Should an FSRM file screen block matching files or only report them?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-069-choose-notification-or-enforcement-when-creating-an-fsrm-file-screen/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:16:02+00:00
- Modified: 2026-09-08T18:20:22+00:00
- Last reviewed by DSE: 2026-09-08
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 1 minutes

## What you need to know

Should an FSRM file screen block matching files or only report them?

## 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.

## Article

## Source facts

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](https://learn.microsoft.com/en-us/windows-server/storage/fsrm/create-file-screen).

## Applicability

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.

## DSE recommendation

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.

## Verification

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.

## Official references

[Microsoft Learn: Create a File Screen](https://learn.microsoft.com/en-us/windows-server/storage/fsrm/create-file-screen). Source reviewed September 8, 2026.

## Primary reference

- Name: Create a File Screen
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/windows-server/storage/fsrm/create-file-screen
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Choose notification or enforcement when creating an FSRM file screen,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-069-choose-notification-or-enforcement-when-creating-an-fsrm-file-screen/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.