Skip to content
This repository has been archived by the owner on Jun 13, 2023. It is now read-only.

Latest commit

 

History

History
35 lines (26 loc) · 2.56 KB

File metadata and controls

35 lines (26 loc) · 2.56 KB

Office

Group Policy Objects for Office 2013 and Office 2016 are included in the SHB. It is recommended to use the most recent version of Office to leverage the latest security improvements and product enhancements.

  • Office 2016 Group Policy Objects and Group Policy Templates. Using the 64-bit version of Office 2016 is recommended.
  • Office 2013 Group Policy Objects and Group Policy Templates.

Group Policy templates

The Office template files can be downloaded from Microsoft. They are also included in the Group Policy Templates folder for each version of Office as a convenience.

Importing the Office Group Policy

Importing the Office domain Group Policy

Use the PowerShell Group Policy commands to import the Office Group Policy into a domain. Run the following command on a domain controller from a PowerShell prompt running as a domain administrator.

Invoke-ApplySecureHostBaseline -Path '.\Secure-Host-Baseline' -PolicyNames 'Office 2013','Office 2016'

Importing the Office local Group Policy

Use Microsoft's LGPO tool to apply the Office Group Policy to a standalone system. Run the following command from a command prompt running as a local administrator.

Invoke-ApplySecureHostBaseline -Path '.\Secure-Host-Baseline' -PolicyNames 'Office 2013','Office 2016' -ToolPath '.\LGPO\lgpo.exe'

Office Macros

Office Macros have proven themselves to be an increasingly popular attack vector. In Office 2016 a new group policy setting was added to block macros downloaded from the internet. The new setting was backported to Office 2013 as part of patch MS16-099. This Information Assurance Advisory was published to recommend blocking Office macros downloaded from the internet.

Downloads

Links