Cyber · Trackr The Free Compliance Library
⌘K
DoD Compliance · STIG

Microsoft Publisher 2016 Security Technical Implementation Guide

V2R1 · · · Released 05 Jan 2026 · 16 rules
Compare

Pick two releases to diff their requirements.

View

Open a previous version of this STIG.

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.
Digest of Updates vs. V1R3 · 27 Apr 2018 +16 −15

Comparison against the immediately-prior release (V1R3). Rule matching uses the Group Vuln ID. Content-change detection compares the rule’s description, check, and fix text after stripping inline markup — cosmetic-only edits aren’t flagged.

Added rules 16

  • V-238482 Medium Disabling of user name and password syntax from being used in URLs must be enforced.
  • V-238483 Medium Enabling IE Bind to Object functionality must be present.
  • V-238484 Medium Saved from URL mark to assure Internet zone processing must be enforced.
  • V-238485 Medium Navigation to URLs embedded in Office products must be blocked.
  • V-238486 Medium Scripted Window Security must be enforced.
  • V-238487 Medium Add-on Management functionality must be allowed.
  • V-238488 Medium Add-ins to Office applications must be signed by a Trusted Publisher.
  • V-238489 Medium Links that invoke instances of Internet Explorer from within an Office product must be blocked.
  • V-238490 Medium Trust Bar Notifications for unsigned application add-ins must be blocked.
  • V-238491 Medium File Downloads must be configured for proper restrictions.
  • V-238492 Medium Protection from zone elevation must be enforced.
  • V-238493 Medium ActiveX Installs must be configured for proper restriction.
  • V-238494 Medium Warning Bar settings for VBA macros must be configured.
  • V-238495 Medium Fatally corrupt files must be blocked from opening.
  • V-238496 Medium The Publisher Automation Security Level must be configured for high security.
  • V-279948 High The version of Publisher running on the system must be a supported version.

Removed rules 15

  • V-70729 Medium Disabling of user name and password syntax from being used in URLs must be enforced.
  • V-70731 Medium Enabling IE Bind to Object functionality must be present.
  • V-70733 Medium Saved from URL mark to assure Internet zone processing must be enforced.
  • V-70735 Medium Navigation to URLs embedded in Office products must be blocked.
  • V-70747 Medium Scripted Window Security must be enforced.
  • V-70749 Medium Add-on Management functionality must be allowed.
  • V-70751 Medium Add-ins to Office applications must be signed by a Trusted Publisher.
  • V-70753 Medium Links that invoke instances of Internet Explorer from within an Office product must be blocked.
  • V-70755 Medium Trust Bar Notifications for unsigned application add-ins must be blocked.
  • V-70757 Medium File Downloads must be configured for proper restrictions.
  • V-70759 Medium Protection from zone elevation must be enforced.
  • V-70761 Medium ActiveX Installs must be configured for proper restriction.
  • V-70763 Medium Warning Bar settings for VBA macros must be configured.
  • V-71673 Medium Fatally corrupt files must be blocked from opening.
  • V-71675 Medium The Publisher Automation Security Level must be configured for high security.
Sort by
b
Disabling of user name and password syntax from being used in URLs must be enforced.
SC-18 - Medium - CCI-001170 - V-238482 - SV-238482r961092_rule
RMF Control
SC-18
Severity
M
CCI
CCI-001170
Version
DTOO104
Vuln IDs
  • V-238482
  • V-70729
Rule IDs
  • SV-238482r961092_rule
  • SV-85353
The Uniform Resource Locator (URL) standard allows user authentication to be included in URL strings in the form http://username:password@example.com. A malicious user might use this URL syntax to create a hyperlink that appears to open a legitimate website but actually opens a deceptive (spoofed) website. For example, the URL http://www.wingtiptoys.com@example.com appears to open http://www.wingtiptoys.com but actually opens http://example.com. To protect users from such attacks, Internet Explorer usually blocks any URLs using this syntax. This functionality can be controlled separately for instances of Internet Explorer spawned by Office applications (for example, if a user clicks a link in an Office document or selects a menu option that loads a website). If user names and passwords in URLs are allowed, users could be diverted to dangerous Web pages, which could pose a security risk.
Checks: C-41693r654778_chk

Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2016 (Machine) -> Security Settings -> IE Security "Disable user name and password" is set to "Enabled" and 'mspub.exe' is checked. Procedure: Use the Windows Registry Editor to navigate to the following key: HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_HTTP_USERNAME_PASSWORD_DISABLE Criteria: If the value mspub.exe is REG_DWORD = 1, this is not a finding.

Fix: F-41652r654779_fix

Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2016 (Machine) -> Security Settings -> IE Security "Disable user name and password" to "Enabled" and place a check in the 'mspub.exe' check box.

b
Enabling IE Bind to Object functionality must be present.
SC-18 - Medium - CCI-001695 - V-238483 - SV-238483r960921_rule
RMF Control
SC-18
Severity
M
CCI
CCI-001695
Version
DTOO111
Vuln IDs
  • V-238483
  • V-70731
Rule IDs
  • SV-238483r960921_rule
  • SV-85355
Internet Explorer performs a number of safety checks before initializing an ActiveX control. It will not initialize a control if the kill bit for the control is set in the registry, or if the security settings for the zone in which the control is located do not allow it to be initialized. This functionality can be controlled separately for instances of Internet Explorer spawned by Office applications (for example, if a user clicks a link in an Office document or selects a menu option that loads a web page). A security risk could occur if potentially dangerous controls are allowed to load.
Checks: C-41694r654781_chk

Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2016 (Machine) -> Security Settings -> IE Security "Bind to Object" is set to "Enabled" and 'mspub.exe' is checked. Procedure: Use the Windows Registry Editor to navigate to the following key: HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_SAFE_BINDTOOBJECT Criteria: If the value mspub.exe is REG_DWORD = 1, this is not a finding.

Fix: F-41653r654782_fix

Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2016 (Machine) -> Security Settings -> IE Security "Bind to Object" to "Enabled" and place a check in the 'mspub.exe' check box.

b
Saved from URL mark to assure Internet zone processing must be enforced.
SC-18 - Medium - CCI-001170 - V-238484 - SV-238484r961092_rule
RMF Control
SC-18
Severity
M
CCI
CCI-001170
Version
DTOO117
Vuln IDs
  • V-238484
  • V-70733
Rule IDs
  • SV-238484r961092_rule
  • SV-85357
Typically, when Internet Explorer loads a web page from a Universal Naming Convention (UNC) share that contains a Mark of the Web (MOTW) comment, indicating the page was saved from a site on the Internet, Internet Explorer runs the page in the Internet security zone instead of the less restrictive Local Intranet security zone. This functionality can be controlled separately for instances of Internet Explorer spawned by Office applications (for example, if a user clicks a link in an Office document or selects a menu option that loads a web page). If Internet Explorer does not evaluate the page for a MOTW, potentially dangerous code could be allowed to run.
Checks: C-41695r654784_chk

Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2016 (Machine) -> Security Settings -> IE Security "Saved from URL" is set to "Enabled" and 'mspub.exe' is checked. Procedure: Use the Windows Registry Editor to navigate to the following key: HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_UNC_SAVEDFILECHECK Criteria: If the value mspub.exe is REG_DWORD = 1, this is not a finding.

Fix: F-41654r654785_fix

Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2016 (Machine) -> Security Settings -> IE Security "Saved from URL" to "Enabled" and place a check in the 'mspub.exe' check box.

b
Navigation to URLs embedded in Office products must be blocked.
SC-18 - Medium - CCI-001170 - V-238485 - SV-238485r961092_rule
RMF Control
SC-18
Severity
M
CCI
CCI-001170
Version
DTOO123
Vuln IDs
  • V-238485
  • V-70735
Rule IDs
  • SV-238485r961092_rule
  • SV-85359
To protect users from attacks, Internet Explorer usually does not attempt to load malformed URLs. This functionality can be controlled separately for instances of Internet Explorer spawned by Office applications (for example, if a user clicks a link in an Office document or selects a menu option that loads a web page). If Internet Explorer attempts to load a malformed URL, a security risk could occur.
Checks: C-41696r654787_chk

Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2016 (Machine) -> Security Settings -> IE Security "Navigate URL" is set to "Enabled" and 'mspub.exe' is checked. Procedure: Use the Windows Registry Editor to navigate to the following key: HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_VALIDATE_NAVIGATE_URL Criteria: If the value mspub.exe is REG_DWORD = 1, this is not a finding.

Fix: F-41655r654788_fix

Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2016 (Machine) -> Security Settings -> IE Security "Navigate URL" to "Enabled" and place a check in the 'mspub.exe' check box.

b
Scripted Window Security must be enforced.
SC-18 - Medium - CCI-001695 - V-238486 - SV-238486r960921_rule
RMF Control
SC-18
Severity
M
CCI
CCI-001695
Version
DTOO124
Vuln IDs
  • V-238486
  • V-70747
Rule IDs
  • SV-238486r960921_rule
  • SV-85371
Malicious websites often try to confuse or trick users into giving a site permission to perform an action allowing the site to take control of the users' computers in some manner. Disabling or not configuring this setting allows unknown websites to: -Create browser windows appearing to be from the local operating system. -Draw active windows displaying outside of the viewable areas of the screen capturing keyboard input. -Overlay parent windows with their own browser windows to hide important system information, choices or prompts.
Checks: C-41697r654790_chk

Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2016 (Machine) -> Security Settings -> IE Security "Scripted Window Security Restrictions" is set to "Enabled" and 'mspub.exe' is checked. Procedure: Use the Windows Registry Editor to navigate to the following key: HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_WINDOW_RESTRICTIONS Criteria: If the value mspub.exe is REG_DWORD = 1, this is not a finding.

Fix: F-41656r654791_fix

Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2016 (Machine) -> Security Settings -> IE Security "Scripted Window Security Restrictions" to "Enabled" and place a check in the 'mspub.exe' check box.

b
Add-on Management functionality must be allowed.
SC-18 - Medium - CCI-001662 - V-238487 - SV-238487r961086_rule
RMF Control
SC-18
Severity
M
CCI
CCI-001662
Version
DTOO126
Vuln IDs
  • V-238487
  • V-70749
Rule IDs
  • SV-238487r961086_rule
  • SV-85373
Internet Explorer add-ons are pieces of code, run in Internet Explorer, to provide additional functionality. Rogue add-ons may contain viruses or other malicious code. Disabling or not configuring this setting could allow malicious code or users to become active on user computers or the network. For example, a malicious user can monitor and then use keystrokes users type into Internet Explorer. Even legitimate add-ons may demand resources, compromising the performance of Internet Explorer, and the operating systems for user computers.
Checks: C-41698r654793_chk

Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2016 (Machine) -> Security Settings -> IE Security "Add-on Management" is set to "Enabled" and 'mspub.exe' is checked. Procedure: Use the Windows Registry Editor to navigate to the following key: HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ADDON_MANAGEMENT Criteria: If the value mspub.exe is REG_DWORD = 1, this is not a finding.

Fix: F-41657r654794_fix

Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2016 (Machine) -> Security Settings -> IE Security "Add-on Management" to "Enabled" and place a check in the 'mspub.exe' check box.

b
Add-ins to Office applications must be signed by a Trusted Publisher.
CM-5 - Medium - CCI-001749 - V-238488 - SV-238488r960954_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001749
Version
DTOO127
Vuln IDs
  • V-238488
  • V-70751
Rule IDs
  • SV-238488r960954_rule
  • SV-85375
This policy setting controls whether add-ins for this applications must be digitally signed by a trusted publisher. If you enable this policy setting, this application checks the digital signature for each add-in before loading it. If an add-in does not have a digital signature, or if the signature did not come from a trusted publisher, this application disables the add-in and notifies the user. Certificates must be added to the Trusted Publishers list if you require that all add-ins be signed by a trusted publisher. For detail on about obtaining and distributing certificates, see http://go.microsoft.com/fwlink/?LinkId=294922. Office 2016 stores certificates for trusted publishers in the Internet Explorer trusted publisher store. Earlier versions of Microsoft Office stored trusted publisher certificate information (specifically, the certificate thumbprint) in a special Office trusted publisher store. Office 2016 still reads trusted publisher certificate information from the Office trusted publisher store, but it does not write information to this store. Therefore, if you created a list of trusted publishers in a previous version of Office and you upgrade to Office 2016, your trusted publisher list will still be recognized. However, any trusted publisher certificates that you add to the list will be stored in the Internet Explorer trusted publisher store. For more information about trusted publishers, see the Office Resource Kit. If you disable or do not configure this policy setting, this application does not check the digital signature on application add-ins before opening them. If a dangerous add-in is loaded, it could harm users' computers or compromise data security.
Checks: C-41699r654796_chk

Verify the policy value for User Configuration -> Administrative Templates -> Microsoft Publisher 2016 -> Security -> Trust Center "Require that application add-ins are signed by Trusted Publisher" is set to "Enabled". Procedure: Use the Windows Registry Editor to navigate to the following key: HKCU\Software\Policies\Microsoft\Office\16.0\publisher\security Criteria: If the value RequireAddinSig is REG_DWORD = 1, this is not a finding.

Fix: F-41658r654797_fix

Set the policy value for User Configuration -> Administrative Templates -> Microsoft Publisher 2016 -> Security -> Trust Center "Require that application add-ins are signed by Trusted Publisher" to "Enabled".

b
Links that invoke instances of Internet Explorer from within an Office product must be blocked.
SC-18 - Medium - CCI-001662 - V-238489 - SV-238489r961086_rule
RMF Control
SC-18
Severity
M
CCI
CCI-001662
Version
DTOO129
Vuln IDs
  • V-238489
  • V-70753
Rule IDs
  • SV-238489r961086_rule
  • SV-85377
The Pop-up Blocker feature in Internet Explorer can be used to block most unwanted pop-up and pop-under windows from appearing. This functionality can be controlled separately for instances of Internet Explorer spawned by Office applications (for example, if a user clicks a link in an Office document or selects a menu option that loads a web page). If the Pop-up Blocker is disabled, disruptive and potentially dangerous pop-up windows could load and present a security risk.
Checks: C-41700r654799_chk

Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2016 (Machine) -> Security Settings -> IE Security "Block popups" is set to "Enabled" and 'mspub.exe' is checked. Procedure: Use the Windows Registry Editor to navigate to the following key: HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_WEBOC_POPUPMANAGEMENT Criteria: If the value mspub.exe is REG_DWORD = 1, this is not a finding.

Fix: F-41659r654800_fix

Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2016 (Machine) -> Security Settings -> IE Security "Block popups" to "Enabled" and place a check in the 'mspub.exe' check box.

b
Trust Bar Notifications for unsigned application add-ins must be blocked.
CM-5 - Medium - CCI-001749 - V-238490 - SV-238490r960954_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001749
Version
DTOO131
Vuln IDs
  • V-238490
  • V-70755
Rule IDs
  • SV-238490r960954_rule
  • SV-85379
This policy setting controls whether the specified Office application notifies users when unsigned application add-ins are loaded or silently disable such add-ins without notification. This policy setting only applies if you enable the "Require that application add-ins are signed by Trusted Publisher" policy setting, which prevents users from changing this policy setting. If you enable this policy setting, applications automatically disable unsigned add-ins without informing users. If you disable this policy setting, if this application is configured to require that all add-ins be signed by a trusted publisher, any unsigned add-ins the application loads will be disabled and the application will display the Trust Bar at the top of the active window. The Trust Bar contains a message that informs users about the unsigned add-in. If you do not configure this policy setting, the disable behavior applies, and in addition, users can configure this requirement themselves in the "Add-ins" category of the Trust Center for the application.
Checks: C-41701r654802_chk

Verify the policy value for User Configuration -> Administrative Templates -> Microsoft Publisher 2016 -> Security -> Trust Center "Disable Trust Bar Notification for unsigned application add-ins" is set to "Enabled". Procedure: Use the Windows Registry Editor to navigate to the following key: HKCU\Software\Policies\Microsoft\Office\16.0\publisher\security Criteria: If the value NoTBPromptUnsignedAddin is REG_DWORD = 1, this is not a finding.

Fix: F-41660r654803_fix

Set the policy value for User Configuration -> Administrative Templates -> Microsoft Publisher 2016 -> Security -> Trust Center "Disable Trust Bar Notification for unsigned application add-ins" to "Enabled".

b
File Downloads must be configured for proper restrictions.
SC-18 - Medium - CCI-001169 - V-238491 - SV-238491r961089_rule
RMF Control
SC-18
Severity
M
CCI
CCI-001169
Version
DTOO132
Vuln IDs
  • V-238491
  • V-70757
Rule IDs
  • SV-238491r961089_rule
  • SV-85381
Disabling this setting allows websites to present file download prompts via code without the user specifically initiating the download. User preferences may also allow the download to occur without prompting or interaction with the user. Even if Internet Explorer prompts the user to accept the download, some websites abuse this functionality. Malicious websites may continually prompt users to download a file or present confusing dialog boxes to trick users into downloading or running a file. If the download occurs and it contains malicious code, the code could become active on user computers or the network.
Checks: C-41702r654805_chk

Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2016 (Machine) -> Security Settings -> IE Security "Restrict File Download" is set to "Enabled" and 'mspub.exe' is checked. Procedure: Use the Windows Registry Editor to navigate to the following key: HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_RESTRICT_FILEDOWNLOAD Criteria: If the value of mspub.exe is REG_DWORD = 1, this is not a finding.

Fix: F-41661r654806_fix

Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2016 (Machine) -> Security Settings -> IE Security "Restrict File Download" to "Enabled" and place a check in the 'mspub.exe' check box.

b
Protection from zone elevation must be enforced.
SC-18 - Medium - CCI-001695 - V-238492 - SV-238492r960921_rule
RMF Control
SC-18
Severity
M
CCI
CCI-001695
Version
DTOO209
Vuln IDs
  • V-238492
  • V-70759
Rule IDs
  • SV-238492r960921_rule
  • SV-85383
Internet Explorer places restrictions on each web page users can use the browser to open. Web pages on a user's local computer have the fewest security restrictions and reside in the Local Machine zone, making this security zone a prime target for malicious users and code. Disabling or not configuring this setting could allow pages in the Internet zone to navigate to pages in the Local Machine zone to then run code to elevate privileges. This could allow malicious code or users to become active on user computers or the network.
Checks: C-41703r654808_chk

Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2016 (Machine) -> Security Settings -> IE Security "Protection From Zone Elevation" is set to "Enabled" and 'mspub.exe' is checked. Procedure: Use the Windows Registry Editor to navigate to the following key: HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ZONE_ELEVATION Criteria: If the value mspub.exe is REG_DWORD = 1, this is not a finding.

Fix: F-41662r654809_fix

Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2016 (Machine) -> Security Settings -> IE Security "Protection From Zone Elevation" to "Enabled" and place a check in the 'mspub.exe' check box.

b
ActiveX Installs must be configured for proper restriction.
SC-18 - Medium - CCI-002460 - V-238493 - SV-238493r961779_rule
RMF Control
SC-18
Severity
M
CCI
CCI-002460
Version
DTOO211
Vuln IDs
  • V-238493
  • V-70761
Rule IDs
  • SV-238493r961779_rule
  • SV-85385
Microsoft ActiveX controls allow unmanaged, unprotected code to run on the user computers. ActiveX controls do not run within a protected container in the browser like the other types of HTML or Microsoft Silverlight-based controls. Disabling or not configuring this setting does not block prompts for ActiveX control installations, and these prompts display to users. This could allow malicious code to become active on user computers or the network.
Checks: C-41704r654811_chk

Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2016 (Machine) -> Security Settings -> IE Security "Restrict ActiveX Install" is set to "Enabled" and 'mspub.exe' is checked. Procedure: Use the Windows Registry Editor to navigate to the following key: HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_RESTRICT_ACTIVEXINSTALL Criteria: If the value mspub.exe is REG_DWORD = 1, this is not a finding.

Fix: F-41663r654812_fix

Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2016 (Machine) -> Security Settings -> IE Security "Restrict ActiveX Install" to "Enabled" and place a check in the 'mspub.exe' check box.

b
Warning Bar settings for VBA macros must be configured.
CM-7 - Medium - CCI-000381 - V-238494 - SV-238494r960963_rule
RMF Control
CM-7
Severity
M
CCI
CCI-000381
Version
DTOO304
Vuln IDs
  • V-238494
  • V-70763
Rule IDs
  • SV-238494r960963_rule
  • SV-85387
This policy setting controls how the specified applications warn users when Visual Basic for Applications (VBA) macros are present. If you enable this policy setting, you can choose from four options for determining how the specified applications will warn the user about macros: - Disable all with notification: The application displays the Trust Bar for all macros, whether signed or unsigned. This option enforces the default configuration in Office. - Disable all except digitally signed macros: The application displays the Trust Bar for digitally signed macros, allowing users to enable them or leave them disabled. Any unsigned macros are disabled, and users are not notified. - Disable all without notification: The application disables all macros, whether signed or unsigned, and does not notify users. - Enable all macros (not recommended): All macros are enabled, whether signed or unsigned. This option can significantly reduce security by allowing dangerous code to run undetected. If you disable this policy setting, "Disable all with notification" will be the default setting. If you do not configure this policy setting, when users open files in the specified applications that contain VBA macros, the applications open the files with the macros disabled and display the Trust Bar with a warning that macros are present and have been disabled. Users can inspect and edit the files if appropriate, but cannot use any disabled functionality until they enable it by clicking "Enable Content" on the Trust Bar. If the user clicks "Enable Content", then the document is added as a trusted document. Important: If "Disable all except digitally signed macros" is selected, users will not be able to open unsigned Access databases. Also, note that Microsoft Office stores certificates for trusted publishers in the Internet Explorer trusted publisher store. Earlier versions of Microsoft Office stored trusted publisher certificate information (specifically, the certificate thumbprint) in a special Office trusted publisher store. Microsoft Office still reads trusted publisher certificate information from the Office trusted publisher store, but it does not write information to this store. Therefore, if you created a list of trusted publishers in a previous version of Microsoft Office and you upgrade to Office, your trusted publisher list will still be recognized. However, any trusted publisher certificates that you add to the list will be stored in the Internet Explorer trusted publisher store.
Checks: C-41705r654814_chk

Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Publisher 2016 >> Security >> Trust Center >> "VBA Macro Notification Settings" is set to "Enabled: Disable all with notification". The options "Enabled: Disable all except digitally signed macros" and "Enabled: Disable all without notification" are more restrictive and also acceptable values. Procedure: Use the Windows Registry Editor to navigate to the following key: HKCU\Software\Policies\Microsoft\Office\16.0\publisher\security Criteria: If the value VBAWarnings is REG_DWORD = 2, this is not a finding. Values of REG_DWORD = 3 or 4 are also acceptable values. If the registry key does not exist or the value is REG_DWORD = 1, then this is a finding.

Fix: F-41664r654815_fix

Set the policy value User Configuration >> Administrative Templates >> Microsoft Publisher 2016 >> Security >> Trust Center >> "VBA Macro Notification Settings" to "Enabled (Disabled all with notifications)".

b
Fatally corrupt files must be blocked from opening.
SC-18 - Medium - CCI-001662 - V-238495 - SV-238495r961086_rule
RMF Control
SC-18
Severity
M
CCI
CCI-001662
Version
DTOO322
Vuln IDs
  • V-238495
  • V-71673
Rule IDs
  • SV-238495r961086_rule
  • SV-86297
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.
Checks: C-41706r654817_chk

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.

Fix: F-41665r654818_fix

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

b
The Publisher Automation Security Level must be configured for high security.
SC-18 - Medium - CCI-001170 - V-238496 - SV-238496r961092_rule
RMF Control
SC-18
Severity
M
CCI
CCI-001170
Version
DTOO323
Vuln IDs
  • V-238496
  • V-71675
Rule IDs
  • SV-238496r961092_rule
  • SV-86299
This policy setting controls whether macros opened programmatically by another application can run in Publisher.If you enable this policy setting, you may choose an option for controlling macro behavior in Publisher when the application is opened programmatically:- Low (enabled): Macros can run in the programmatically opened application.- By UI (prompted): Macro functionality is determined by the setting in the "Macro Settings" section of the Trust Center.- High (disabled): All macros are disabled in the programmatically opened application.If you disable or do not configure this policy setting, Publisher will use the default Macro setting in Trust Center.
Checks: C-41707r654820_chk

Verify the policy value for User Configuration -> Administrative Templates -> Microsoft Publisher 2016 -> Security "Publisher Automation Security Level" is set to "Enabled and High (Disabled)" is selected. Procedure: Use the Windows Registry Editor to navigate to the following key: HKCU\Software\Policies\Microsoft\Office\Common\Security Criteria: If the value AutomationSecurityPublisher is REG_DWORD = 3, this is not a finding.

Fix: F-41666r654821_fix

Set the policy value for User Configuration -> Administrative Templates -> Microsoft Publisher 2016 -> Security "Publisher Automation Security Level" to "Enabled and High (Disabled)" is selected.

c
The version of Publisher running on the system must be a supported version.
SI-2 - High - CCI-002605 - V-279948 - SV-279948r1156593_rule
RMF Control
SI-2
Severity
H
CCI
CCI-002605
Version
DTO-Pub999
Vuln IDs
  • V-279948
Rule IDs
  • SV-279948r1156593_rule
Security flaws with software applications are discovered daily. Vendors are constantly updating and patching their products to address newly discovered security vulnerabilities. Organizations (including any contractor to the organization) are required to promptly install security-relevant software updates (e.g., patches, service packs, and hot fixes). Flaws discovered during security assessments, continuous monitoring, incident response activities, or information system error handling must also be addressed expeditiously. Organization-defined time periods for updating security-relevant software may vary based on a variety of factors including, for example, the security category of the information system or the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw). This requirement will apply to software patch management solutions that are used to install patches across the enclave and also to applications themselves that are not part of that patch management solution. For example, many browsers today provide the capability to install their own patch software. Patch criticality, as well as system criticality will vary. Therefore, the tactical situations regarding the patch management process will also vary. This means that the time period used must be a configurable parameter. Time frames for application of security-relevant software updates may be dependent upon the Information Assurance Vulnerability Management (IAVM) process. The application will be configured to check for and install security-relevant software updates within an identified time period from the availability of the update. The specific time period will be defined by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs).
Checks: C-84509r1156591_chk

Publisher 2016 is no longer supported by the vendor. If the system is running Publisher 2016, this is a finding.

Fix: F-84414r1156592_fix

Upgrade to a supported version.