User interface defenses – Microsoft Surface Hub 2 SmCamera User Manual
Page 295
The configuration file is signed using the Microsoft Production Root CA designed to
prevent restrictions from being removed or modified by a third party. All other
executables at this point are simply blocked at the operating system runtime level and
prevented from accessing processing power. This attack surface reduction provides the
following protections:
No legacy document modes
No legacy script engines
No Vector Markup Language
No Browser Helper Objects
No ActiveX controls
In addition to blocking unsigned or incorrectly signed code via UMCI, Surface Hub uses
Windows Application Control to block Windows components, such as the Command
Prompt, PowerShell, and Task Manager. These safeguards reflect a key design feature of
Surface Hub as a secure computing appliance. For more information, see the following:
While boot-time defenses and operating system lockdown safeguards deliver
foundational security, the user interface provides an additional layer designed to further
reduce risk. To prevent malicious code from reaching the device through drivers, Surface
Hub does not download advanced drivers for plug and play (PnP) devices. Devices that
leverage basic drivers, such as USB flash drives or certified Surface Hub peripherals
(speakers, microphones, cameras), work as expected, but advanced systems, such as
printers, will not.
User interface defenses also simplify the UI, further preventing the execution of
malicious software or code. The following Surface Hub UI elements layer the core
security provided by code signing:
File Explorer.
Surface Hub has a custom File Explorer that enables quick access to
Music, Videos, Documents, Pictures, and Downloads folders — without exposing
users to system or program files. Other locations on the local hard drive are not
available through File Explorer. In addition, many file types running, such as .exe
and .msi installation files, cannot run, providing another layer of safety against
potentially malicious executables.
User interface defenses