Windows 10: Windows 11 Security Baselines - will the two new policies be included in the next Windows...

[Thomas Martin Grome] · Oct 6, 2021

Windows 11 Security Baselines - will the two new policies be included in the next Windows 10 baseline update?Namely:Script ScanningLimits print driver installation to AdministratorsThe latter I'm particularly interested in as I am under the impression that it is MSFTs solution to PrintNightmare

:)

Brink · Oct 6, 2021

Security baseline news for Microsoft Edge version 81

We have reviewed the new settings in version 81 of Microsoft Edge and determined that no new security settings are required. The settings recommended in the version 80 baseline will continue to be the security baseline for version 81! This means we will not be releasing our typical package.

Version 81 of Microsoft Edge adds 15 new computer- and user-based settings. There are now 285 enforceable Computer Configuration policy settings and 269 User Configuration policy settings. Using our streamlined approach, our baseline remains at 12 Group Policy settings. We have attached a spreadsheet with the new settings to make it easier for you to find them.

The version 80 package continues to be available as part of the Security Compliance Toolkit. Like all our baseline packages, this package includes:

Importable GPOs

A script to apply the GPOs to local policy

A script to import the GPOs into Active Directory Group Policy

A spreadsheet documenting all recommended settings in spreadsheet form (minus the version 81 setting that are attached to this blog)

Policy Analyzer rules

GP Reports

We always welcome feedback through the Baselines Discussion site.
Click to expand...

Source: https://techcommunity.microsoft.com/...1/ba-p/1303621

Latest Microsoft Edge released for Windows

Brink · Oct 6, 2021

Security baseline (DRAFT) release for Chromium-based Microsoft Edge 79

Microsoft is pleased to announce the draft release of the recommended security configuration baseline settings for the next version of Microsoft Edge based on Chromium, version 79. Please evaluate this proposed baseline and send us your feedback through the Baselines Discussion site.

The settings recommended in this baseline are identical to the ones we recommended in the version 78 draft. None of the settings introduced in the version 79 policies meet the bar for inclusion in the baseline for broad use. We are republishing the baseline package because the names of several of the recommended settings were changed (for example, references to “SSL” were replaced with “HTTPS” or “TLS”).

Like all our baseline packages, the downloadable draft baseline package (attached to this blog post) includes importable GPOs, a script to apply the GPOs to local policy, a script to import the GPOs into Active Directory Group Policy, and all the recommended settings in spreadsheet form, as Policy Analyzer rules, and as GP Reports. It also includes a spreadsheet showing the changes in the available GPO settings between versions 78 and 79.

Microsoft Edge is being rebuilt with the open-source Chromium project, and many of its security configuration options are inherited from that project. These Group Policy settings are entirely distinct from those for the original version of Microsoft Edge built into Windows 10: they are in different folders in the Group Policy editor and they reference different registry keys. The Group Policy settings that control the new version of Microsoft Edge are located under “Administrative Templates\Microsoft Edge,” while those that control the current version of Microsoft Edge remain located under “Administrative Templates\Windows Components\Microsoft Edge.” You can download the latest policy templates for the new version of Microsoft Edge from the Microsoft Edge Enterprise landing page. To learn more about managing the new version of Microsoft Edge, see Configure Microsoft Edge for Windows.

As with our current Windows and Office security baselines, our recommendations for Microsoft Edge configuration follow a streamlined and efficient approach to baseline definition when compared with the baselines we published before Windows 10. The foundation of that approach is essentially this:

The baselines are designed for well-managed, security-conscious organizations in which standard end users do not have administrative rights.

A baseline enforces a setting only if it mitigates a contemporary security threat and does not cause operational issues that are worse than the risks they mitigate.

A baseline enforces a default only if it is otherwise likely to be set to an insecure state by an authorized user:

If a non-administrator can set an insecure state, enforce the default.

If setting an insecure state requires administrative rights, enforce the default only if it is likely that a misinformed administrator will otherwise choose poorly.

(For further explanation, see the “Why aren’t we enforcing more defaults?” section in this blog post.)

Version 79 of the Chromium-based version of Microsoft Edge has 217 enforceable Computer Configuration policy settings and another 201 User Configuration policy settings. Following our streamlined approach, our recommended baseline configures a grand total of twelve Group Policy settings. You can find full documentation in the download package’s Documentation subdirectory.
Click to expand...

Source: https://techcommunity.microsoft.com/...e/ba-p/1066051

Brink · Oct 6, 2021

Security baseline (DRAFT) for Chromium based Microsoft Edge version 78

Microsoft is pleased to announce the draft release of the recommended security configuration baseline settings for the next version of Microsoft Edge based on Chromium, version 78. Please evaluate this proposed baseline and send us your feedback through the Baselines Discussion site.

Like all our baseline packages, the downloadable draft baseline package (attached to this blog post) includes importable GPOs, a script to apply the GPOs to local policy, a script to import the GPOs into Active Directory Group Policy, and all the recommended settings in spreadsheet form, as Policy Analyzer rules, and as GP Reports.

Microsoft Edge is being rebuilt with the open-source Chromium project, and many of its security configuration options are inherited from that project. These Group Policy settings are entirely distinct from those for the original version of Microsoft Edge built into Windows 10: they are in different folders in the Group Policy editor and they reference different registry keys. The Group Policy settings that control the new version of Microsoft Edge are located under “Administrative Templates\Microsoft Edge,” while those that control the current version of Microsoft Edge remain located under “Administrative Templates\Windows Components\Microsoft Edge.” You can download the latest policy templates for the new version of Microsoft Edge from the Microsoft Edge Enterprise landing page. To learn more about managing the new version of Microsoft Edge, see Configure Microsoft Edge for Windows.

As with our current Windows and Office security baselines, our recommendations for Microsoft Edge configuration follow a streamlined and efficient approach to baseline definition when compared with the baselines we published before Windows 10. The foundation of that approach is essentially this:

The baselines are designed for well-managed, security-conscious organizations in which standard end users do not have administrative rights.

A baseline enforces a setting only if it mitigates a contemporary security threat and does not cause operational issues that are worse than the risks they mitigate.

A baseline enforces a default only if it is otherwise likely to be set to an insecure state by an authorized user:

If a non-administrator can set an insecure state, enforce the default.

If setting an insecure state requires administrative rights, enforce the default only if it is likely that a misinformed administrator will otherwise choose poorly.

(For further explanation, see the “Why aren’t we enforcing more defaults?” section in this blog post.)

Version 78 of the Chromium-based version of Microsoft Edge has 205 enforceable Computer Configuration policy settings and another 190 User Configuration policy settings. Following our streamlined approach, our recommended baseline configures a grand total of twelve Group Policy settings. You can find full documentation in the download package’s Documentation subdirectory.
Click to expand...

Source: https://techcommunity.microsoft.com/...ge/ba-p/949991

Tweet

— Twitter API (@user) View on Twitter
Click to expand...

Windows 10: Windows 11 Security Baselines - will the two new policies be included in the next Windows...

Windows 11 Security Baselines - will the two new policies be included in the next Windows...

Windows 11 Security Baselines - will the two new policies be included in the next Windows...

Windows 11 Security Baselines - will the two new policies be included in the next Windows...

Windows 11 Security Baselines - will the two new policies be included in the next Windows... - Similar Threads - Security Baselines policies

23h2 security baseline. Whats new from 2021 baseline?

23h2 security baseline. Whats new from 2021 baseline?

Moving to new baseline

Revert Security Baselines

Revert Security Baselines

Building/ Creating Secure Host Baseline Image for Windows 11

Building/ Creating Secure Host Baseline Image for Windows 11

Microsoft Security Baseline policies conflict

Microsoft Security Baseline policies conflict