Microsoft Encourages Windows 10 Based 'Highly Secure' PCs With These New Standards

Microsoft Encourages Windows 10 Based 'Highly Secure' PCs With These New Standards”

The company today released updates for Windows 10 Creators Update (build 1703), Windows 10 November Update (build 1511) and Windows 10 Anniversary Update (build 1609). Apparently these two occurrences are not unrelated, as there are plenty of reports of folks suffering the stylus blues after installing Microsoft's latest upgrade for its desktop OS.

It is apparent that there is a bug in the Windows 10 Fall Creators Update where pinch to zoom no longer works, and where the system will not recognize the Surface Pen. "Windows enterprise security features light up when you meet or exceed these standards and your device is able to provide a highly secure experience".

The firmware section is further divided into six more categories, focusing on code integrity and update mechanism, among others.

Processors must support Input-Output Memory Management Unit (IOMMU) device virtualization and all I/O devices need to be protected by IOMMU/SMMU.

System must have virtual machine extensions with second level address translation.

Systems must have a TPM 2.0 module that is in compliance with the Trustworthy Computing Group (TCG) specifications.

Also, note that enabling this feature, you'll be giving Windows 10 permission to periodically record the physical location of your device as well.

It may seem like a somewhat daunting list, and in some respects it is.

Microsoft demands that systems implement cryptographically verified platform boot. However, it does not mean that only expensive systems will meet the the requirements.

System's firmware must implement Secure MOR revision 2. Perhaps Microsoft also needs to consider a certification program along with a "Secure Windows 10 device" badge to allow OEMs to differentiate from competitors based on this certification and give them a good reason to adopt these requirements in the first place.

Type Troubleshooting in the search box, click Troubleshooting.

Сomo este

Más reciente