Microsoft Publisher 2016 Security Technical Implementation Guide

The Microsoft Publisher 2016 Security Technical Implementation Guide (V2 R1) has 16 STIG checks. New to STIG checklists? Read What is a STIG checklist?, CKL vs CKLB, and STIG vs SCAP benchmark.

Find STIG checks

16STIG checks

Search filters this STIG's checks locally. Separate terms must all match (use quotes for an exact phrase). A search you ran on the Search page carries over here.

Severity

Version

V2 · R1

CurrentPublished Mon Jan 05 2026

Fatally corrupt files must be blocked from opening.

Microsoft Publisher 2016 Security Technical Implementation Guide

Assessment Title

Rule Text

Fatally corrupt files must be blocked from opening.

Description

Discussion Text

When disabled, fatally corrupt files are prevented from opening. When enabled, the user is warned but may choose to open the file.By default, fatally corrupt files are prevented from opening.

New to STIG checklists? Read What is a STIG checklist? and CKL vs CKLB.

Objective

V-238495

Rule

SV-238495r961086_rule

Severity

medium

Rule Version

DTOO322

Documentable

false

IA Controls

NIST SP 800-53

Rev 5

Assessment Procedure

Check Text

Verify the policy value for User Configuration -> Administrative Templates -> Microsoft Publisher 2016 -> Security "Prompt to allow fatally corrupt files to open instead of blocking them" is set to "Disabled".

Procedure: Use the Windows Registry Editor to navigate to the following key: 


HKCU\Software\Policies\Microsoft\Office\16.0\publisher

Criteria: If the value PromptForBadFiles is REG_DWORD = 0, this is not a finding.

Implementation Procedure

Fix Text

Set the policy value for User Configuration -> Administrative Templates -> Microsoft Publisher 2016 -> Security "Prompt to allow fatally corrupt files to open instead of blocking them" to "Disabled".

STIG check 14 of 16 in the Microsoft Publisher 2016 STIG checklist

← Previous · V-238494Warning Bar settings for VBA macros must be configured.Next · V-238496 →The Publisher Automation Security Level must be configured for high security.