The Publisher Automation Security Level must be configured for high security.

From Microsoft Publisher 2010 STIG

Part of DTOO323 - Publisher Automation Security Level

Associated with: CCI-001170

SV-34093r1_rule The Publisher Automation Security Level must be configured for high security.

Vulnerability discussion

When a separate application is used to launch Publisher 2010 programmatically, any macros can run in the programmatically-opened application without being blocked. Disabling or not configuring this setting could allow a malicious user to use automation to run malicious code in Publisher 2010.

Check content

The policy value for User Configuration -> Administrative Templates -> Microsoft Publisher 2010 -> Security “Publisher Automation Security Level” must be 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 text

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

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.

Powered by sagemincer