From Microsoft Access 2013 STIG
Part of DTOO304 - VBA Macro Warning settings
VSTO projects require access to the Visual Basic for Applications project system in Excel, PowerPoint, and Word, even though the projects do not use Visual Basic for Applications. Design-time support of controls in both Visual Basic and C# projects depends on the Visual Basic for Applications project system in Word and Excel. By default, Excel, Word, and PowerPoint do not allow automation clients to have programmatic access to VBA projects. Users can enable this by selecting the Trust access to the VBA project object model in the Macro Settings section of the Trust Center. However, doing so allows macros in any documents the user opens to access the core Visual Basic objects, methods, and properties, which represents a potential security hazard.
Verify the policy value for User Configuration -> Administrative Templates -> Microsoft Access 2013 -> Application Settings -> Security -> Trust Center -> "VBA macro Notification Settings" is set to "Enabled: Disable all with notification". Procedure: Use the Windows Registry Editor to navigate to the following key: HKCU\software\policies\Microsoft\office\15.0\access\security Criteria: If the value vbawarnings is REG_DWORD = 2, this is not a finding.
Set policy value for User Configuration -> Administrative Templates -> Microsoft Access 2013 -> Application Settings -> Security -> Trust Center -> "VBA macro Notification Settings" must be set to "Enabled: Disable all with notification".
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