mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
Merge branch 'master' into wip-css-update
This commit is contained in:
Justin Hall
GitHub
commit
2a3fdc4e91
@ -2,46 +2,13 @@
|
||||
"build_entry_point": "",
|
||||
"docsets_to_publish": [
|
||||
{
|
||||
"docset_name": "bcs-VSTS",
|
||||
"build_source_folder": "bcs",
|
||||
"build_output_subfolder": "bcs-VSTS",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": false,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "education-VSTS",
|
||||
"docset_name": "education",
|
||||
"build_source_folder": "education",
|
||||
"build_output_subfolder": "education-VSTS",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
},
|
||||
{
|
||||
"docset_name": "eula-vsts",
|
||||
"build_source_folder": "windows/eulas",
|
||||
"build_output_subfolder": "eula-vsts",
|
||||
"build_output_subfolder": "education",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": false,
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
@ -51,44 +18,12 @@
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "gdpr",
|
||||
"build_source_folder": "gdpr",
|
||||
"build_output_subfolder": "gdpr",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": false,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "internet-explorer-VSTS",
|
||||
"build_source_folder": "browsers/internet-explorer",
|
||||
"build_output_subfolder": "internet-explorer-VSTS",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
},
|
||||
{
|
||||
"docset_name": "itpro-hololens-VSTS",
|
||||
"docset_name": "hololens",
|
||||
"build_source_folder": "devices/hololens",
|
||||
"build_output_subfolder": "itpro-hololens-VSTS",
|
||||
"build_output_subfolder": "hololens",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -96,35 +31,32 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "keep-secure-VSTS",
|
||||
"docset_name": "internet-explorer",
|
||||
"build_source_folder": "browsers/internet-explorer",
|
||||
"build_output_subfolder": "internet-explorer",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "keep-secure",
|
||||
"build_source_folder": "windows/keep-secure",
|
||||
"build_output_subfolder": "keep-secure-VSTS",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
},
|
||||
{
|
||||
"docset_name": "known-issues",
|
||||
"build_source_folder": "windows/known-issues",
|
||||
"build_output_subfolder": "known-issues",
|
||||
"build_output_subfolder": "keep-secure",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": false,
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
@ -134,11 +66,12 @@
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "mdop-VSTS",
|
||||
"docset_name": "mdop",
|
||||
"build_source_folder": "mdop",
|
||||
"build_output_subfolder": "mdop-VSTS",
|
||||
"build_output_subfolder": "mdop",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -146,31 +79,12 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "microsoft-edge-VSTS",
|
||||
"docset_name": "microsoft-edge",
|
||||
"build_source_folder": "browsers/edge",
|
||||
"build_output_subfolder": "microsoft-edge-VSTS",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
},
|
||||
{
|
||||
"docset_name": "privacy",
|
||||
"build_source_folder": "windows/privacy",
|
||||
"build_output_subfolder": "privacy",
|
||||
"build_output_subfolder": "microsoft-edge",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
@ -184,9 +98,9 @@
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "security",
|
||||
"build_source_folder": "windows/security",
|
||||
"build_output_subfolder": "security",
|
||||
"docset_name": "release-information",
|
||||
"build_source_folder": "windows/release-information",
|
||||
"build_output_subfolder": "release-information",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
@ -194,18 +108,18 @@
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content",
|
||||
"LandingData": "Content"
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "smb-VSTS",
|
||||
"docset_name": "smb",
|
||||
"build_source_folder": "smb",
|
||||
"build_output_subfolder": "smb-VSTS",
|
||||
"build_output_subfolder": "smb",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -213,16 +127,15 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "store-for-business-VSTS",
|
||||
"docset_name": "store-for-business",
|
||||
"build_source_folder": "store-for-business",
|
||||
"build_output_subfolder": "store-for-business-VSTS",
|
||||
"build_output_subfolder": "store-for-business",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -230,33 +143,15 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "surface-hub-VSTS",
|
||||
"build_source_folder": "devices/surface-hub",
|
||||
"build_output_subfolder": "surface-hub-VSTS",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
},
|
||||
{
|
||||
"docset_name": "surface-VSTS",
|
||||
"docset_name": "surface",
|
||||
"build_source_folder": "devices/surface",
|
||||
"build_output_subfolder": "surface-VSTS",
|
||||
"build_output_subfolder": "surface",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -264,16 +159,31 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "win-access-protection-VSTS",
|
||||
"docset_name": "surface-hub",
|
||||
"build_source_folder": "devices/surface-hub",
|
||||
"build_output_subfolder": "surface-hub",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "win-access-protection",
|
||||
"build_source_folder": "windows/access-protection",
|
||||
"build_output_subfolder": "win-access-protection-VSTS",
|
||||
"build_output_subfolder": "win-access-protection",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -281,16 +191,15 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "win-app-management-VSTS",
|
||||
"docset_name": "win-app-management",
|
||||
"build_source_folder": "windows/application-management",
|
||||
"build_output_subfolder": "win-app-management-VSTS",
|
||||
"build_output_subfolder": "win-app-management",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -298,16 +207,15 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "win-client-management-VSTS",
|
||||
"docset_name": "win-client-management",
|
||||
"build_source_folder": "windows/client-management",
|
||||
"build_output_subfolder": "win-client-management-VSTS",
|
||||
"build_output_subfolder": "win-client-management",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -315,16 +223,15 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "win-configuration-VSTS",
|
||||
"docset_name": "win-configuration",
|
||||
"build_source_folder": "windows/configuration",
|
||||
"build_output_subfolder": "win-configuration-VSTS",
|
||||
"build_output_subfolder": "win-configuration",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -332,16 +239,15 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "win-development-VSTS",
|
||||
"docset_name": "win-deployment",
|
||||
"build_source_folder": "windows/deployment",
|
||||
"build_output_subfolder": "win-development-VSTS",
|
||||
"build_output_subfolder": "win-deployment",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -349,16 +255,15 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "win-device-security-VSTS",
|
||||
"docset_name": "win-device-security",
|
||||
"build_source_folder": "windows/device-security",
|
||||
"build_output_subfolder": "win-device-security-VSTS",
|
||||
"build_output_subfolder": "win-device-security",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -366,16 +271,15 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "windows-configure-VSTS",
|
||||
"docset_name": "windows-configure",
|
||||
"build_source_folder": "windows/configure",
|
||||
"build_output_subfolder": "windows-configure-VSTS",
|
||||
"build_output_subfolder": "windows-configure",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -383,16 +287,15 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "windows-deploy-VSTS",
|
||||
"docset_name": "windows-deploy",
|
||||
"build_source_folder": "windows/deploy",
|
||||
"build_output_subfolder": "windows-deploy-VSTS",
|
||||
"build_output_subfolder": "windows-deploy",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -400,16 +303,15 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "windows-hub-VSTS",
|
||||
"docset_name": "windows-hub",
|
||||
"build_source_folder": "windows/hub",
|
||||
"build_output_subfolder": "windows-hub-VSTS",
|
||||
"build_output_subfolder": "windows-hub",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -417,16 +319,31 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "windows-manage-VSTS",
|
||||
"docset_name": "windows-known-issues",
|
||||
"build_source_folder": "windows/known-issues",
|
||||
"build_output_subfolder": "windows-known-issues",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "windows-manage",
|
||||
"build_source_folder": "windows/manage",
|
||||
"build_output_subfolder": "windows-manage-VSTS",
|
||||
"build_output_subfolder": "windows-manage",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -434,16 +351,15 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "windows-plan-VSTS",
|
||||
"docset_name": "windows-plan",
|
||||
"build_source_folder": "windows/plan",
|
||||
"build_output_subfolder": "windows-plan-VSTS",
|
||||
"build_output_subfolder": "windows-plan",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -451,16 +367,47 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "windows-update-VSTS",
|
||||
"docset_name": "windows-privacy",
|
||||
"build_source_folder": "windows/privacy",
|
||||
"build_output_subfolder": "windows-privacy",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "windows-security",
|
||||
"build_source_folder": "windows/security",
|
||||
"build_output_subfolder": "windows-security",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
"ManagedReference": "Content",
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "windows-update",
|
||||
"build_source_folder": "windows/update",
|
||||
"build_output_subfolder": "windows-update-VSTS",
|
||||
"build_output_subfolder": "windows-update",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -468,16 +415,15 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "win-threat-protection-VSTS",
|
||||
"docset_name": "win-threat-protection",
|
||||
"build_source_folder": "windows/threat-protection",
|
||||
"build_output_subfolder": "win-threat-protection-VSTS",
|
||||
"build_output_subfolder": "win-threat-protection",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -485,16 +431,15 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
},
|
||||
{
|
||||
"docset_name": "win-whats-new-VSTS",
|
||||
"docset_name": "win-whats-new",
|
||||
"build_source_folder": "windows/whats-new",
|
||||
"build_output_subfolder": "win-whats-new-VSTS",
|
||||
"build_output_subfolder": "win-whats-new",
|
||||
"locale": "en-us",
|
||||
"monikers": [],
|
||||
"moniker_ranges": [],
|
||||
"open_to_public_contributors": true,
|
||||
"type_mapping": {
|
||||
"Conceptual": "Content",
|
||||
@ -502,9 +447,7 @@
|
||||
"RestApi": "Content"
|
||||
},
|
||||
"build_entry_point": "docs",
|
||||
"template_folder": "_themes",
|
||||
"moniker_groups": [],
|
||||
"version": 0
|
||||
"template_folder": "_themes"
|
||||
}
|
||||
],
|
||||
"notification_subscribers": [
|
||||
@ -544,10 +487,6 @@
|
||||
"master": [
|
||||
"Publish",
|
||||
"Pdf"
|
||||
],
|
||||
"atp-api-danm": [
|
||||
"Publish",
|
||||
"Pdf"
|
||||
]
|
||||
},
|
||||
"need_generate_pdf_url_template": true,
|
||||
|
||||
@ -6,21 +6,6 @@
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/security/threat-protection/windows-security-baselines.md",
|
||||
"redirect_url": "/windows/security/threat-protection/windows-security-configuration-framework/windows-security-baselines",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/security/threat-protection/security-compliance-toolkit-10.md",
|
||||
"redirect_url": "/windows/security/threat-protection/windows-security-configuration-framework/security-compliance-toolkit-10",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/security/threat-protection/get-support-for-security-baselines.md",
|
||||
"redirect_url": "/windows/security/threat-protection/windows-security-configuration-framework/get-support-for-security-baselines",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/collect-cab-files-exploit-guard-submission.md",
|
||||
"redirect_url": "/windows/security/threat-protection/windows-defender-exploit-guard/troubleshoot-np",
|
||||
"redirect_document_id": true
|
||||
|
||||
@ -24,7 +24,8 @@
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "Win.microsoft-edge"
|
||||
"depot_name": "Win.microsoft-edge",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
@ -34,4 +35,4 @@
|
||||
"dest": "browsers/edge",
|
||||
"markdownEngineName": "dfm"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
@ -26,10 +26,10 @@ For more information on how Internet Explorer and Microsoft Edge work together t
|
||||
[Enterprise Mode](https://docs.microsoft.com/internet-explorer/ie11-deploy-guide/enterprise-mode-overview-for-ie11) helps you run many legacy web applications with better backward compatibility. You can configure both Microsoft Edge and Internet Explorer to use the same Enterprise Mode Site List, switching seamlessly between browsers to support both modern and legacy web apps.
|
||||
|
||||
## How do I customize Microsoft Edge and related settings for my organization?
|
||||
You can use Group Policy or Microsoft Intune to manage settings related to Microsoft Edge, such as security settings, folder redirection, and preferences. See [Group Policy and Mobile Device Management (MDM) settings for Microsoft Edge](/group-policies/index.md) for a list of policies currently available for Microsoft Edge and configuration information. Note that the preview release of Chromium-based Microsoft Edge might not include management policies or other enterprise functionality; our focus during the preview is modern browser fundamentals.
|
||||
You can use Group Policy or Microsoft Intune to manage settings related to Microsoft Edge, such as security settings, folder redirection, and preferences. See [Group Policy and Mobile Device Management (MDM) settings for Microsoft Edge](https://docs.microsoft.com/microsoft-edge/deploy/group-policies/) for a list of policies currently available for Microsoft Edge and configuration information. Note that the preview release of Chromium-based Microsoft Edge might not include management policies or other enterprise functionality; our focus during the preview is modern browser fundamentals.
|
||||
|
||||
## Is Adobe Flash supported in Microsoft Edge?
|
||||
Adobe Flash is currently supported as a built-in feature of Microsoft Edge on PCs running Windows 10. In July 2017, Adobe announced that Flash support will end after 2020. With this change to Adobe support, we’ve started to phase Flash out of Microsoft Edge by adding the [Configure the Adobe Flash Click-to-Run setting group policy](/available-policies.md#configure-the-adobe-flash-click-to-run-setting) - this lets you control which websites can run Adobe Flash content.
|
||||
Adobe Flash is currently supported as a built-in feature of Microsoft Edge on PCs running Windows 10. In July 2017, Adobe announced that Flash support will end after 2020. With this change to Adobe support, we’ve started to phase Flash out of Microsoft Edge by adding the [Configure the Adobe Flash Click-to-Run setting group policy](https://docs.microsoft.com/microsoft-edge/deploy/available-policies#configure-the-adobe-flash-click-to-run-setting) - this lets you control which websites can run Adobe Flash content.
|
||||
|
||||
To learn more about Microsoft’s plan for phasing Flash out of Microsoft Edge and Internet Explorer, see [The End of an Era — Next Steps for Adobe Flash](https://blogs.windows.com/msedgedev/2017/07/25/flash-on-windows-timeline/#3Bcc3QjRw0l7XsZ4.97) (blog article).
|
||||
|
||||
|
||||
@ -27,7 +27,8 @@
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "Win.internet-explorer"
|
||||
"depot_name": "Win.internet-explorer",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
@ -37,4 +38,4 @@
|
||||
"dest": "edges/internet-explorer",
|
||||
"markdownEngineName": "dfm"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
@ -12,6 +12,6 @@
|
||||
## [Configure HoloLens using a provisioning package](hololens-provisioning.md)
|
||||
## [Install apps on HoloLens](hololens-install-apps.md)
|
||||
## [Enable Bitlocker device encryption for HoloLens](hololens-encryption.md)
|
||||
## [Restart, reset, or recover HoloLens 2](hololens-recovery.md)
|
||||
## [Restore HoloLens 2 using Advanced Recovery Companion](hololens-recovery.md)
|
||||
## [How HoloLens stores data for spaces](hololens-spaces.md)
|
||||
## [Change history for Microsoft HoloLens documentation](change-history-hololens.md)
|
||||
@ -19,7 +19,7 @@ This topic lists new and updated topics in the [Microsoft HoloLens documentation
|
||||
|
||||
New or changed topic | Description
|
||||
--- | ---
|
||||
[Restart, reset, or recover HoloLens 2](hololens-recovery.md) | New
|
||||
[Restore HoloLens 2 using Advanced Recovery Companion](hololens-recovery.md) | New
|
||||
|
||||
## November 2018
|
||||
|
||||
|
||||
@ -40,7 +40,8 @@
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "Win.itpro-hololens"
|
||||
"depot_name": "Win.itpro-hololens",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Restart, reset, or recover HoloLens 2
|
||||
title: Restore HoloLens 2 using Advanced Recovery Companion
|
||||
description: How to use Advanced Recovery Companion to flash an image to HoloLens 2.
|
||||
ms.prod: hololens
|
||||
ms.sitesec: library
|
||||
@ -9,7 +9,7 @@ ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
# Restart, reset, or recover HoloLens 2
|
||||
# Restore HoloLens 2 using Advanced Recovery Companion
|
||||
|
||||
>[!TIP]
|
||||
>If you're having issues with HoloLens (the first device released), see [Restart, reset, or recover HoloLens](https://support.microsoft.com/help/13452/hololens-restart-reset-or-recover-hololens). Advanced Recovery Companion is only supported for HoloLens 2.
|
||||
|
||||
@ -41,6 +41,7 @@
|
||||
### [Miracast on existing wireless network or LAN](miracast-over-infrastructure.md)
|
||||
### [Enable 802.1x wired authentication](enable-8021x-wired-authentication.md)
|
||||
### [Using a room control system](use-room-control-system-with-surface-hub.md)
|
||||
### [Implement Quality of Service on Surface Hub](surface-hub-qos.md)
|
||||
### [Using the Surface Hub Recovery Tool](surface-hub-recovery-tool.md)
|
||||
### [Surface Hub SSD replacement](surface-hub-ssd-replacement.md)
|
||||
## [PowerShell for Surface Hub](appendix-a-powershell-scripts-for-surface-hub.md)
|
||||
|
||||
@ -22,6 +22,7 @@ New or changed topic | Description
|
||||
[Technical information for 55” Microsoft Surface Hub](surface-hub-technical-55.md) | New; previously available for download and on [Surface Hub Tech Spec](https://support.microsoft.com/help/4483539/surface-hub-tech-spec)
|
||||
[Technical information for 84” Microsoft Surface Hub ](surface-hub-technical-84.md) | New; previously available for download and on [Surface Hub Tech Spec](https://support.microsoft.com/help/4483539/surface-hub-tech-spec)
|
||||
[Surface Hub SSD replacement](surface-hub-ssd-replacement.md) | New; previously available for download only
|
||||
[Implement Quality of Service on Surface Hub](surface-hub-qos.md) | New
|
||||
|
||||
## July 2018
|
||||
|
||||
|
||||
@ -29,7 +29,8 @@
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "Win.surface-hub"
|
||||
"depot_name": "Win.surface-hub",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
@ -39,4 +40,4 @@
|
||||
"dest": "devices/surface-hub",
|
||||
"markdownEngineName": "dfm"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
BIN
devices/surface-hub/images/qos-create.png
Normal file
BIN
devices/surface-hub/images/qos-create.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 14 KiB |
BIN
devices/surface-hub/images/qos-setting.png
Normal file
BIN
devices/surface-hub/images/qos-setting.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 34 KiB |
51
devices/surface-hub/surface-hub-qos.md
Normal file
51
devices/surface-hub/surface-hub-qos.md
Normal file
@ -0,0 +1,51 @@
|
||||
---
|
||||
title: Implement Quality of Service on Surface Hub
|
||||
description: Learn how to configure QoS on Surface Hub.
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
author: jdeckerms
|
||||
ms.author: jdecker
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
# Implement Quality of Service (QoS) on Surface Hub
|
||||
|
||||
Quality of Service (QoS) is a combination of network technologies that allows the administrators to optimize the experience of real time audio/video and application sharing communications.
|
||||
|
||||
Configuring [QoS for Skype for Business](https://docs.microsoft.com/windows/client-management/mdm/networkqospolicy-csp) on the Surface Hub can be done using your [mobile device management (MDM) provider](manage-settings-with-mdm-for-surface-hub.md) or through a [provisioning package](provisioning-packages-for-surface-hub.md).
|
||||
|
||||
|
||||
This procedure explains how to configure QoS for Surface Hub using Microsoft Intune.
|
||||
|
||||
1. In Intune, [create a custom policy](https://docs.microsoft.com/intune/custom-settings-configure).
|
||||
|
||||
|
||||
|
||||
2. In **Custom OMA-URI Settings**, select **Add**. For each setting that you add, you will enter a name, description (optional), data type, OMA-URI, and value.
|
||||
|
||||
|
||||
|
||||
3. Add the following custom OMA-URI settings:
|
||||
|
||||
Name | Data type | OMA-URI<br>./Device/Vendor/MSFT/NetworkQoSPolicy | Value
|
||||
--- | --- | --- | ---
|
||||
Audio Source Port | String | /HubAudio/SourcePortMatchCondition | Get the values from your Skype administrator
|
||||
Audio DSCP | Integer | /HubAudio/DSCPAction | 46
|
||||
Video Source Port | String | /HubVideo/SourcePortMatchCondition | Get the values from your Skype administrator
|
||||
Video DSCP | Integer | /HubVideo/DSCPAction | 34
|
||||
Audio Process Name | String | /HubAudio/AppPathNameMatchCondition | Microsoft.PPISkype.Windows.exe
|
||||
Video Process Name | String | /HubVideo/AppPathNameMatchCondition | Microsoft.PPISkype.Windows.exe
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Each **OMA-URI** path begins with `./Device/Vendor/MSFT/NetworkQoSPolicy`. The full path for the audio source port setting, for example, will be `./Device/Vendor/MSFT/NetworkQoSPolicy/HubAudio/SourcePortMatchCondition`.
|
||||
|
||||
|
||||
|
||||
|
||||
4. When the policy has been created, [deploy it to the Surface Hub.](manage-settings-with-mdm-for-surface-hub.md#manage-surface-hub-settings-with-mdm)
|
||||
|
||||
|
||||
>[!WARNING]
|
||||
>Currently, you cannot configure the setting **IPProtocolMatchCondition** in the [NetworkQoSPolicy CSP](https://docs.microsoft.com/windows/client-management/mdm/networkqospolicy-csp). If this setting is configured, the policy will fail to apply.
|
||||
|
||||
@ -26,7 +26,8 @@
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "Win.surface"
|
||||
"depot_name": "Win.surface",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
@ -36,4 +37,4 @@
|
||||
"dest": "devices/surface",
|
||||
"markdownEngineName": "dfm"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
@ -26,7 +26,8 @@
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "Win.education"
|
||||
"depot_name": "Win.education",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
|
||||
@ -27,7 +27,8 @@
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "Win.mdop"
|
||||
"depot_name": "Win.mdop",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
@ -37,4 +38,4 @@
|
||||
"dest": "mdop",
|
||||
"markdownEngineName": "dfm"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
@ -36,7 +36,8 @@
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "TechNet.smb"
|
||||
"depot_name": "TechNet.smb",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
@ -45,4 +46,4 @@
|
||||
"dest": "smb",
|
||||
"markdownEngineName": "dfm"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
@ -43,7 +43,8 @@
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "MSDN.store-for-business"
|
||||
"depot_name": "MSDN.store-for-business",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
@ -52,4 +53,4 @@
|
||||
"dest": "store-for-business",
|
||||
"markdownEngineName": "dfm"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
@ -38,7 +38,8 @@
|
||||
"ms.author": "justinha",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "MSDN.win-access-protection"
|
||||
"depot_name": "MSDN.win-access-protection",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
@ -46,4 +47,4 @@
|
||||
"template": [],
|
||||
"dest": "win-access-protection"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
@ -41,7 +41,8 @@
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "MSDN.win-app-management"
|
||||
"depot_name": "MSDN.win-app-management",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
@ -50,4 +51,4 @@
|
||||
"dest": "win-app-management",
|
||||
"markdownEngineName": "dfm"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
@ -40,7 +40,8 @@
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "MSDN.win-client-management"
|
||||
"depot_name": "MSDN.win-client-management",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
@ -49,4 +50,4 @@
|
||||
"dest": "win-client-management",
|
||||
"markdownEngineName": "dfm"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
@ -20,7 +20,7 @@ This topic lists new and updated topics in the [Configure Windows 10](index.md)
|
||||
|
||||
New or changed topic | Description
|
||||
--- | ---
|
||||
[Prepare a device for kiosk configuration](kiosk-prepare.md) | Added new recommendations for policies to manage updates.
|
||||
[Use Shell Launcher to create a Windows 10 kiosk](kiosk-shelllauncher.md) | Added information for Shell Launcher v2, coming in the next feature update to Windows 10.
|
||||
|
||||
## February 2019
|
||||
|
||||
|
||||
@ -41,7 +41,8 @@
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "MSDN.win-configuration"
|
||||
"depot_name": "MSDN.win-configuration",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
@ -50,4 +51,4 @@
|
||||
"dest": "win-configuration",
|
||||
"markdownEngineName": "dfm"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
BIN
windows/configuration/images/slv2-oma-uri.png
Normal file
BIN
windows/configuration/images/slv2-oma-uri.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 19 KiB |
@ -8,7 +8,6 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: jdeckerms
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 09/13/2018
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -30,7 +29,7 @@ Topic | Description
|
||||
[Policies enforced on kiosk devices](kiosk-policies.md) | Learn about the policies enforced on a device when you configure it as a kiosk.
|
||||
[Assigned access XML reference](kiosk-xml.md) | The XML and XSD for kiosk device configuration.
|
||||
[Use AppLocker to create a Windows 10 kiosk](lock-down-windows-10-applocker.md) | Learn how to use AppLocker to configure a kiosk device running Windows 10 Enterprise or Windows 10 Education, version 1703 and earlier, so that users can only run a few specific apps.
|
||||
[Use Shell Launcher to create a Windows 10 kiosk](kiosk-shelllauncher.md) | Using Shell Launcher, you can configure a kiosk device that runs a Windows desktop application as the user interface.
|
||||
[Use Shell Launcher to create a Windows 10 kiosk](kiosk-shelllauncher.md) | Using Shell Launcher, you can configure a kiosk device that runs a Windows application as the user interface.
|
||||
[Use MDM Bridge WMI Provider to create a Windows 10 kiosk](kiosk-mdm-bridge.md) | Environments that use Windows Management Instrumentation (WMI) can use the MDM Bridge WMI Provider to configure the MDM_AssignedAccess class.
|
||||
[Troubleshoot kiosk mode issues](kiosk-troubleshoot.md) | Tips for troubleshooting multi-app kiosk configuration.
|
||||
|
||||
|
||||
@ -12,6 +12,9 @@ ms.topic: article
|
||||
|
||||
# Configure kiosks and digital signs on Windows desktop editions
|
||||
|
||||
>[!WARNING]
|
||||
>Some information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
|
||||
|
||||
Some desktop devices in an enterprise serve a special purpose, such as a PC in the lobby that customers can use to view your product catalog or a PC displaying visual content as a digital sign. Windows 10 offers two different locked-down experiences for public or specialized use:
|
||||
|
||||
| | |
|
||||
@ -43,6 +46,7 @@ You can use this method | For this edition | For this kiosk account type
|
||||
[Assigned access cmdlets](kiosk-single-app.md#powershell) | Pro, Ent, Edu | Local standard user
|
||||
[The kiosk wizard in Windows Configuration Designer](kiosk-single-app.md#wizard) | Pro (version 1709), Ent, Edu | Local standard user, Active Directory, Azure AD
|
||||
[Microsoft Intune or other mobile device management (MDM)](kiosk-single-app.md#mdm) | Pro (version 1709), Ent, Edu | Local standard user, Azure AD
|
||||
[Shell Launcher](kiosk-shelllauncher.md) v2 | Ent, Edu | Local standard user, Active Directory, Azure AD
|
||||
|
||||
<span id="classic" />
|
||||
## Methods for a single-app kiosk running a Windows desktop application
|
||||
@ -50,8 +54,8 @@ You can use this method | For this edition | For this kiosk account type
|
||||
You can use this method | For this edition | For this kiosk account type
|
||||
--- | --- | ---
|
||||
[The kiosk wizard in Windows Configuration Designer](kiosk-single-app.md#wizard) | Ent, Edu | Local standard user, Active Directory, Azure AD
|
||||
[Shell Launcher](kiosk-shelllauncher.md) | Ent, Edu | Local standard user, Active Directory, Azure AD
|
||||
[Microsoft Intune or other mobile device management (MDM)](kiosk-single-app.md#mdm) | Pro (version 1709), Ent, Edu | Local standard user, Azure AD
|
||||
[Shell Launcher](kiosk-shelllauncher.md) v1 and v2 | Ent, Edu | Local standard user, Active Directory, Azure AD
|
||||
|
||||
<span id="desktop" />
|
||||
## Methods for a multi-app kiosk
|
||||
|
||||
@ -8,6 +8,7 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: jdeckerms
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 01/09/2019
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
@ -30,14 +31,12 @@ ms.topic: article
|
||||
|
||||
## Configuration recommendations
|
||||
|
||||
For a more secure kiosk experience, we recommend that you make the following configuration changes to the device before you configure it as a kiosk:
|
||||
For a more secure kiosk experience, we recommend that you make the following configuration changes to the device before you configure it as a kiosk:
|
||||
|
||||
Recommendation | How to
|
||||
--- | ---
|
||||
Hide update notifications<br>(New in Windows 10, version 1809) | Go to **Group Policy Editor** > **Computer Configuration** > **Administrative Templates\\Windows Components\\Windows Update\\Display options for update notifications**<br>-or-<br>Use the MDM setting **Update/UpdateNotificationLevel** from the [**Policy/Update** configuration service provider](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-updatenotificationlevel)<br>-or-<br>Add the following registry keys as type DWORD (32-bit) in the path of **HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate**:<br>**\SetUpdateNotificationLevel** with a value of `1`, and **\UpdateNotificationLevel** with a value of `1` to hide all notifications except restart warnings, or value of `2` to hide all notifications, including restart warnings.
|
||||
Enable and schedule automatic updates | Go to **Group Policy Editor** > **Computer Configuration** > **Administrative Templates\\Windows Components\\Windows Update\\Configure Automatic Updates**, and select `option 4 (Auto download and schedule the install)`<br>-or-<br>Use the MDM setting **Update/AllowAutoUpdate** from the [**Policy/Update** configuration service provider](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-allowautoupdate), and select `option 3 (Auto install and restart at a specified time)`<br><br>**Note:** Installations can take from between 30 minutes and 2 hours, depending on the device, so you should schedule updates to occur when a block of 3-4 hours is available.<br><br>To schedule the automatic update, configure **Schedule Install Day**, **Schedule Install Time**, and **Schedule Install Week**.
|
||||
Enable automatic restart at the scheduled time | Go to **Group Policy Editor** > **Computer Configuration** > **Administrative Templates\\Windows Components\\Windows Update\\Always automatically restart at the scheduled time**
|
||||
Replace "blue screen" with blank screen for OS errors | Add the following registry key as DWORD (32-bit) type with a value of `1`:</br></br>**HKLM\SYSTEM\CurrentControlSet\Control\CrashControl\DisplayDisabled**
|
||||
Hide update notifications<br>(New in Windows 10, version 1809) | Go to **Group Policy Editor** > **Computer Configuration** > **Administrative Templates\\Windows Components\\Windows Update\\Display options for update notifications**<br>-or-<br>Use the MDM setting **Update/UpdateNotificationLevel** from the [**Policy/Update** configuration service provider](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-updatenotificationlevel)<br>-or-<br>Add the following registry keys as DWORD (32-bit) type:</br>`HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\SetUpdateNotificationLevel` with a value of `1`, and `HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\UpdateNotificationLevel` with a value of `1` to hide all notifications except restart warnings, or value of `2` to hide all notifications, including restart warnings.
|
||||
Replace "blue screen" with blank screen for OS errors | Add the following registry key as DWORD (32-bit) type with a value of `1`:</br></br>`HKLM\SYSTEM\CurrentControlSet\Control\CrashControl\DisplayDisabled`
|
||||
Put device in **Tablet mode**. | If you want users to be able to use the touch (on screen) keyboard, go to **Settings** > **System** > **Tablet mode** and choose **On.** Do not turn on this setting if users will not interact with the kiosk, such as for a digital sign.
|
||||
Hide **Ease of access** feature on the sign-in screen. | See [how to disable the Ease of Access button in the registry.](https://docs.microsoft.com/windows-hardware/customize/enterprise/complementary-features-to-custom-logon#welcome-screen)
|
||||
Disable the hardware power button. | Go to **Power Options** > **Choose what the power button does**, change the setting to **Do nothing**, and then **Save changes**.
|
||||
@ -68,7 +67,7 @@ In addition to the settings in the table, you may want to set up **automatic log
|
||||
>[!NOTE]
|
||||
>If you are not familiar with Registry Editor, [learn how to modify the Windows registry](https://go.microsoft.com/fwlink/p/?LinkId=615002).
|
||||
|
||||
|
||||
|
||||
2. Go to
|
||||
|
||||
**HKEY\_LOCAL\_MACHINE\SOFTWARE\\Microsoft\WindowsNT\CurrentVersion\Winlogon**
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Use Shell Launcher to create a Windows 10 kiosk (Windows 10)
|
||||
description: A single-use device such as a digital sign is easy to set up in Windows 10 for desktop editions (Pro, Enterprise, and Education).
|
||||
description: Shell Launcher lets you change the default shell that launches when a user signs in to a device.
|
||||
ms.assetid: 428680AE-A05F-43ED-BD59-088024D1BFCC
|
||||
keywords: ["assigned access", "kiosk", "lockdown", "digital sign", "digital signage"]
|
||||
ms.prod: w10
|
||||
@ -8,7 +8,6 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: jdeckerms
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 10/01/2018
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
@ -16,26 +15,36 @@ ms.topic: article
|
||||
|
||||
|
||||
**Applies to**
|
||||
>App type: Windows desktop application
|
||||
>
|
||||
>OS edition: Windows 10 Ent, Edu
|
||||
>
|
||||
>Account type: Local standard user or administrator, Active Directory, Azure AD
|
||||
- Windows 10 Ent, Edu
|
||||
|
||||
>[!WARNING]
|
||||
>Some information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
|
||||
|
||||
Using Shell Launcher, you can configure a kiosk device that runs a Windows desktop application as the user interface. The application that you specify replaces the default shell (explorer.exe) that usually runs when a user logs on.
|
||||
Using Shell Launcher, you can configure a device that runs an application as the user interface, replacing the default shell (explorer.exe). In **Shell Launcher v1**, available in Windows 10, version 1809 and earlier, you can only specify a Windows desktop application as the replacement shell. In **Shell Launcher v2**, available in the next feature update to Windows 10, you can also specify a UWP app as the replacement shell.
|
||||
|
||||
>[!NOTE]
|
||||
>Using the Shell Launcher controls which application the user sees as the shell after sign-in. It does not prevent the user from accessing other desktop applications and system components.
|
||||
>Shell Launcher controls which application the user sees as the shell after sign-in. It does not prevent the user from accessing other desktop applications and system components.
|
||||
>
|
||||
>Methods of controlling access to other desktop applications and system components can be used in addition to using the Shell Launcher. These methods include, but are not limited to:
|
||||
>- [Group Policy](https://www.microsoft.com/download/details.aspx?id=25250) - example: Prevent access to registry editing tools
|
||||
>- [AppLocker](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-application-control/applocker/applocker-overview) - Application control policies
|
||||
>- [Mobile Device Management](https://docs.microsoft.com/windows/client-management/mdm) - Enterprise management of device security policies
|
||||
>
|
||||
>You can also configure a kiosk device that runs a Windows desktop application by using the [Provision kiosk devices wizard](kiosk-single-app.md#wizard).
|
||||
|
||||
|
||||
You can apply a custom shell through Shell Launcher [by using PowerShell](#configure-a-custom-shell-using-powershell). In Windows 10, version 1803 and later, you can also [use mobile device management (MDM)](#configure-a-custom-shell-in-mdm) to apply a custom shell through Shell Launcher.
|
||||
|
||||
|
||||
## Differences between Shell Launcher v1 and Shell Launcher v2
|
||||
|
||||
Shell Launcher v1 replaces `explorer.exe`, the default shell, with `eshell.exe` which can launch a Windows desktop application.
|
||||
|
||||
Shell Launcher v2 replaces `explorer.exe` with `customshellhost.exe`. This new executable file can launch a Windows desktop application or a UWP app.
|
||||
|
||||
In addition to allowing you to use a UWP app for your replacement shell, Shell Launcher v2 offers additional enhancements:
|
||||
- You can use a custom Windows desktop application that can then launch UWP apps, such as **Settings** and **Touch Keyboard**.
|
||||
- From a custom UWP shell, you can launch secondary views and run on multiple monitors.
|
||||
- The custom shell app runs in full screen, and and can run other apps in full screen on user’s demand.
|
||||
|
||||
For sample XML configurations for the different app combinations, see [Samples for Shell Launcher v2](https://github.com/Microsoft/Windows-iotcore-samples/tree/develop/Samples/ShellLauncherV2).
|
||||
|
||||
## Requirements
|
||||
|
||||
@ -44,16 +53,15 @@ Using Shell Launcher, you can configure a kiosk device that runs a Windows deskt
|
||||
>
|
||||
>- Shell Launcher doesn't support a custom shell with an application that launches a different process and exits. For example, you cannot specify **write.exe** in Shell Launcher. Shell Launcher launches a custom shell and monitors the process to identify when the custom shell exits. **Write.exe** creates a 32-bit wordpad.exe process and exits. Because Shell Launcher is not aware of the newly created wordpad.exe process, Shell Launcher will take action based on the exit code of **Write.exe**, such as restarting the custom shell.
|
||||
|
||||
- A domain or local user account.
|
||||
- A domain, Azure Active Directory, or local user account.
|
||||
|
||||
- A Windows desktop application that is installed for that account. The app can be your own company application or a common app like Internet Explorer.
|
||||
- A Windows application that is installed for that account. The app can be your own company application or a common app like Internet Explorer.
|
||||
|
||||
[See the technical reference for the shell launcher component.](https://go.microsoft.com/fwlink/p/?LinkId=618603)
|
||||
[See the technical reference for the shell launcher component.](https://docs.microsoft.com/windows-hardware/customize/enterprise/shell-launcher)
|
||||
|
||||
## Enable Shell Launcher feature
|
||||
|
||||
## Configure Shell Launcher
|
||||
|
||||
To set a Windows desktop application as the shell, you first turn on the Shell Launcher feature, and then you can set your custom shell as the default using PowerShell.
|
||||
To set a custom shell, you first turn on the Shell Launcher feature, and then you can set your custom shell as the default using PowerShell or MDM.
|
||||
|
||||
**To turn on Shell Launcher in Windows features**
|
||||
|
||||
@ -63,7 +71,7 @@ To set a Windows desktop application as the shell, you first turn on the Shell L
|
||||
|
||||
2. Select **Shell Launcher** and **OK**.
|
||||
|
||||
Alternatively, you can turn on Shell Launcher using Windows Configuration Designer in a provisioning package, using `SMISettings > ShellLauncher`, or the Deployment Image Servicing and Management (DISM.exe) tool.
|
||||
Alternatively, you can turn on Shell Launcher using Windows Configuration Designer in a provisioning package, using `SMISettings > ShellLauncher`, or you can use the Deployment Image Servicing and Management (DISM.exe) tool.
|
||||
|
||||
**To turn on Shell Launcher using DISM**
|
||||
|
||||
@ -74,9 +82,70 @@ Alternatively, you can turn on Shell Launcher using Windows Configuration Design
|
||||
Dism /online /Enable-Feature /all /FeatureName:Client-EmbeddedShellLauncher
|
||||
```
|
||||
|
||||
**To set your custom shell**
|
||||
|
||||
Modify the following PowerShell script as appropriate. The comments in the sample script explain the purpose of each section and tell you where you will want to change the script for your purposes. Save your script with the extension .ps1, open Windows PowerShell as administrator, and run the script on the kiosk device.
|
||||
## Configure a custom shell in MDM
|
||||
|
||||
You can use XML and a [custom OMA-URI setting](#custom-oma-uri-setting) to configure Shell Launcher in MDM.
|
||||
|
||||
### XML for Shell Launcher configuration
|
||||
|
||||
The following XML sample works for **Shell Launcher v1**:
|
||||
|
||||
```
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<ShellLauncherConfiguration xmlns="http://schemas.microsoft.com/ShellLauncher/2018/Configuration">
|
||||
<Profiles>
|
||||
<Profile ID="{24A7309204F3F-44CC-8375-53F13FE213F7}">
|
||||
<Shell Shell="%ProgramFiles%\Internet Explorer\iexplore.exe -k www.bing.com" />
|
||||
</Profile>
|
||||
</Profiles>
|
||||
<Configs>
|
||||
<!--local account-->
|
||||
<Account Name="ShellLauncherUser"/>
|
||||
<Profile ID="{24A7309204F3F-44CC-8375-53F13FE213F7}"/>
|
||||
</Configs>
|
||||
</ShellLauncherConfiguration>
|
||||
```
|
||||
|
||||
For **Shell Launcher v2**, you will use a different schema reference and a different app type for `Shell`, as shown in the following example.
|
||||
|
||||
```
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<ShellLauncherConfiguration xmlns="http://schemas.microsoft.com/ShellLauncher/2018/Configuration"
|
||||
xmlns:v2="http://schemas.microsoft.com/ShellLauncher/2019/Configuration">
|
||||
<Profiles>
|
||||
<DefaultProfile>
|
||||
<Shell Shell="ShellLauncherV2DemoUwp_5d7tap497jwe8!App" v2:AppType="UWP" v2:AllAppsFullScreen="true">
|
||||
<DefaultAction Action="RestartShell"/>
|
||||
</Shell>
|
||||
</DefaultProfile>
|
||||
</Profiles>
|
||||
<Configs/>
|
||||
</ShellLauncherConfiguration>
|
||||
```
|
||||
|
||||
>[!TIP]
|
||||
>In the XML for Shell Launcher v2, note the **AllAppsFullScreen** attribute. When set to **True**, Shell Launcher will run every app in full screen, or maximized for desktop apps. When this attribute is set to **False** or not set, only the custom shell app runs in full screen; other apps launched by the user will run in windowed mode.
|
||||
|
||||
[Get XML examples for different Shell Launcher v2 configurations.](https://github.com/Microsoft/Windows-iotcore-samples/tree/develop/Samples/ShellLauncherV2)
|
||||
|
||||
### Custom OMA-URI setting
|
||||
|
||||
In your MDM service, you can create a [custom OMA-URI setting](https://docs.microsoft.com/intune/custom-settings-windows-10) to configure Shell Launcher v1 or v2. (The [XML](#xml-for-shell-launcher-configuration) that you use for your setting will determine whether you apply Shell Launcher v1 or v2.)
|
||||
|
||||
The OMA-URI path is `./Device/Vendor/MSFT/AssignedAccess/ShellLauncher`.
|
||||
|
||||
For the value, you can select data type `String` and paste the desired configuration file content into the value box. If you wish to upload the xml instead of pasting the content, choose data type `String (XML file)` instead.
|
||||
|
||||
|
||||
|
||||
After you configure the profile containing the custom Shell Launcher setting, select **All Devices** or selected groups of devices to apply the profile to. Don't assign the profile to users or user groups.
|
||||
|
||||
## Configure a custom shell using PowerShell
|
||||
|
||||
For scripts for Shell Launcher v2, see [Shell Launcher v2 Bridge WMI sample scripts](https://github.com/Microsoft/Windows-iotcore-samples/blob/develop/Samples/ShellLauncherV2/SampleBridgeWmiScripts/README.md).
|
||||
|
||||
For Shell Launcher v1, modify the following PowerShell script as appropriate. The comments in the sample script explain the purpose of each section and tell you where you will want to change the script for your purposes. Save your script with the extension .ps1, open Windows PowerShell as administrator, and run the script on the kiosk device.
|
||||
|
||||
```
|
||||
# Check if shell launcher license is enabled
|
||||
|
||||
@ -42,8 +42,6 @@ Method | Description
|
||||
|
||||
>[!TIP]
|
||||
>You can also configure a kiosk account and app for single-app kiosk within [XML in a provisioning package](lock-down-windows-10-to-specific-apps.md) by using a [kiosk profile](lock-down-windows-10-to-specific-apps.md#profile).
|
||||
>
|
||||
>Be sure to check the [configuration recommendations](kiosk-prepare.md) before you set up your kiosk.
|
||||
|
||||
|
||||
|
||||
@ -171,8 +169,6 @@ Set-AssignedAccess -AppName <CustomApp> -UserSID <usersid>
|
||||
|
||||
[Learn how to get the AppName](https://msdn.microsoft.com/library/windows/hardware/mt620046%28v=vs.85%29.aspx) (see **Parameters**).
|
||||
|
||||
[Learn how to get the SID](https://go.microsoft.com/fwlink/p/?LinkId=615517).
|
||||
|
||||
To remove assigned access, using PowerShell, run the following cmdlet.
|
||||
|
||||
```
|
||||
|
||||
@ -39,8 +39,7 @@ New features and improvements | In update
|
||||
|
||||
You can configure multi-app kiosks using [Microsoft Intune](#intune) or a [provisioning package](#provision).
|
||||
|
||||
>[!TIP]
|
||||
>Be sure to check the [configuration recommendations](kiosk-prepare.md) before you set up your kiosk.
|
||||
|
||||
|
||||
|
||||
<span id="intune"/>
|
||||
|
||||
@ -25,8 +25,6 @@ For digital signage, simply select a digital sign player as your kiosk app. You
|
||||
|
||||
>[!TIP]
|
||||
>Kiosk Browser can also be used in [single-app kiosks](kiosk-single-app.md) and [multi-app kiosk](lock-down-windows-10-to-specific-apps.md) as a web browser. For more information, see [Guidelines for web browsers](guidelines-for-assigned-access-app.md#guidelines-for-web-browsers).
|
||||
>
|
||||
>Be sure to check the [configuration recommendations](kiosk-prepare.md) before you set up your kiosk.
|
||||
|
||||
Kiosk Browser must be downloaded for offline licensing using Microsoft Store for Business. You can deploy Kiosk Browser to devices running Windows 10, version 1803.
|
||||
|
||||
|
||||
@ -32,7 +32,8 @@
|
||||
"globalMetadata": {
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "MSDN.windows-deploy"
|
||||
"depot_name": "MSDN.windows-deploy",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
@ -40,4 +41,4 @@
|
||||
"template": [],
|
||||
"dest": "windows-deploy"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
@ -42,7 +42,8 @@
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "MSDN.win-development"
|
||||
"depot_name": "MSDN.win-development",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
@ -51,4 +52,4 @@
|
||||
"dest": "win-development",
|
||||
"markdownEngineName": "dfm"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 223 KiB |
@ -39,7 +39,8 @@
|
||||
"ms.date": "04/05/2017",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "MSDN.win-device-security"
|
||||
"depot_name": "MSDN.win-device-security",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
@ -47,4 +48,4 @@
|
||||
"template": [],
|
||||
"dest": "win-device-security"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
@ -44,7 +44,8 @@
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "MSDN.windows-hub"
|
||||
"depot_name": "MSDN.windows-hub",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
@ -53,4 +54,4 @@
|
||||
"dest": "windows-hub",
|
||||
"markdownEngineName": "dfm"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
@ -32,7 +32,8 @@
|
||||
"globalMetadata": {
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "MSDN.keep-secure"
|
||||
"depot_name": "MSDN.keep-secure",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
@ -40,4 +41,4 @@
|
||||
"template": [],
|
||||
"dest": "keep-secure"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
@ -32,7 +32,8 @@
|
||||
"globalMetadata": {
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "MSDN.windows-manage"
|
||||
"depot_name": "MSDN.windows-manage",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
@ -40,4 +41,4 @@
|
||||
"template": [],
|
||||
"dest": "windows-manage"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
@ -32,7 +32,8 @@
|
||||
"globalMetadata": {
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "MSDN.windows-plan"
|
||||
"depot_name": "MSDN.windows-plan",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
@ -40,4 +41,4 @@
|
||||
"template": [],
|
||||
"dest": "windows-plan"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
@ -36,13 +36,19 @@
|
||||
"breadcrumb_path": "/windows/windows-10/breadcrumb/toc.json",
|
||||
"ms.technology": "windows",
|
||||
"ms.topic": "article",
|
||||
"feedback_system": "GitHub",
|
||||
"feedback_system": "GitHub",
|
||||
"feedback_github_repo": "MicrosoftDocs/windows-itpro-docs",
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app"
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "MSDN.privacy",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
"fileMetadata": {},
|
||||
"template": [],
|
||||
"dest": "privacy",
|
||||
"markdownEngineName": "markdig"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
@ -22,13 +22,13 @@ Applies to:
|
||||
- Windows 10, version 1803
|
||||
- Windows 10, version 1709
|
||||
|
||||
Microsoft uses Windows diagnostic data to keep Windows secure and up-to-date, troubleshoot problems, and make product improvements. For users who have turned on "Tailored experiences", it can also be used to offer you personalized tips, ads, and recommendations to enhance Microsoft products and services for your needs. This article describes all types of diagnostic data collected by Windows at the Full level (inclusive of data collected at Basic), with comprehensive examples of data we collect per each type. For additional, detailed technical descriptions of Basic data items, see [Windows 10, version 1803 Basic level diagnostic events and fields](https://docs.microsoft.com/windows/configuration/basic-level-windows-diagnostic-events-and-fields).
|
||||
Microsoft uses Windows diagnostic data to keep Windows secure and up-to-date, troubleshoot problems, and make product improvements. For users who have turned on "Tailored experiences", it can also be used to offer you personalized tips, ads, and recommendations to enhance Microsoft products and services for your needs. This article describes all types of diagnostic data collected by Windows at the Full level (inclusive of data collected at Basic), with comprehensive examples of data we collect per each type. For additional, detailed technical descriptions of Basic data items, see [Windows 10, version 1809 Basic level diagnostic events and fields](https://docs.microsoft.com/windows/configuration/basic-level-windows-diagnostic-events-and-fields).
|
||||
|
||||
In addition, this article provides references to equivalent definitions for the data types and examples from [ISO/IEC 19944:2017 Information technology -- Cloud computing -- Cloud services and devices: Data flow, data categories and data use](https://www.iso.org/standard/66674.html). Each data type also has a Data Use statement, for diagnostics and for Tailored experiences on the device, using the terms as defined by the standard. These Data Use statements define the purposes for which Microsoft processes each type of Windows diagnostic data, using a uniform set of definitions referenced at the end of this document and based on the ISO standard. Reference to the ISO standard provides additional clarity about the information collected, and allows easy comparison with other services or guidance that also references the standard.
|
||||
|
||||
The data covered in this article is grouped into the following types:
|
||||
|
||||
- Common data (diagnostic header information)
|
||||
- Common data extensions (diagnostic header information)
|
||||
- Device, Connectivity, and Configuration data
|
||||
- Product and Service Usage data
|
||||
- Product and Service Performance data
|
||||
@ -36,15 +36,15 @@ The data covered in this article is grouped into the following types:
|
||||
- Browsing History data
|
||||
- Inking, Typing, and Speech Utterance data
|
||||
|
||||
## Common data
|
||||
## Common data extensions
|
||||
Most diagnostic events contain a header of common data. In each example, the info in parentheses provides the equivalent definition for ISO/IEC 19944:2017.
|
||||
|
||||
**Data Use for Common data**
|
||||
**Data Use for Common data extensions**
|
||||
Header data supports the use of data associated with all diagnostic events. Therefore, Common data is used to [provide](#provide) Windows 10, and may be used to [improve](#improve), [personalize](#personalize), [recommend](#recommend), [offer](#offer), or [promote](#promote) Microsoft and third-party products and services, depending on the uses described in the **Data Use** statements for each data category.
|
||||
|
||||
### Data Description for Common data type
|
||||
### Data Description for Common data extensions type
|
||||
|
||||
#### Common data type
|
||||
#### Common data extensions type
|
||||
|
||||
Information that is added to most diagnostic events, if relevant and available:
|
||||
|
||||
@ -506,6 +506,6 @@ Use of the specified data categories to promote a product or service in or on a
|
||||
|
||||
Here are the list of data identification qualifiers and the ISO/IEC 19944:2017 reference:
|
||||
|
||||
- **<a name="#pseudo">Pseudonymized Data</a>** 8.3.3 Pseudonymized data. Microsoft usage notes are as defined.
|
||||
- **<a name="#anon">Anonymized Data</a>** 8.3.5 Anonymized data. Microsoft usage notes are as defined.
|
||||
- **<a name="#aggregate">Aggregated Data</a>** 8.3.6 Aggregated data. Microsoft usage notes are as defined.
|
||||
- **<a name="pseudo">Pseudonymized Data</a>** 8.3.3 Pseudonymized data. Microsoft usage notes are as defined.
|
||||
- **<a name="anon">Anonymized Data</a>** 8.3.5 Anonymized data. Microsoft usage notes are as defined.
|
||||
- **<a name="aggregate">Aggregated Data</a>** 8.3.6 Aggregated data. Microsoft usage notes are as defined.
|
||||
2
windows/release-information/TOC.yml
Normal file
2
windows/release-information/TOC.yml
Normal file
@ -0,0 +1,2 @@
|
||||
- name: Index
|
||||
href: index.md
|
||||
3
windows/release-information/breadcrumb/toc.yml
Normal file
3
windows/release-information/breadcrumb/toc.yml
Normal file
@ -0,0 +1,3 @@
|
||||
- name: Docs
|
||||
tocHref: /
|
||||
topicHref: /
|
||||
47
windows/release-information/docfx.json
Normal file
47
windows/release-information/docfx.json
Normal file
@ -0,0 +1,47 @@
|
||||
{
|
||||
"build": {
|
||||
"content": [
|
||||
{
|
||||
"files": [
|
||||
"**/*.md",
|
||||
"**/*.yml"
|
||||
],
|
||||
"exclude": [
|
||||
"**/obj/**",
|
||||
"**/includes/**",
|
||||
"_themes/**",
|
||||
"_themes.pdf/**",
|
||||
"README.md",
|
||||
"LICENSE",
|
||||
"LICENSE-CODE",
|
||||
"ThirdPartyNotices"
|
||||
]
|
||||
}
|
||||
],
|
||||
"resource": [
|
||||
{
|
||||
"files": [
|
||||
"**/*.png",
|
||||
"**/*.jpg"
|
||||
],
|
||||
"exclude": [
|
||||
"**/obj/**",
|
||||
"**/includes/**",
|
||||
"_themes/**",
|
||||
"_themes.pdf/**"
|
||||
]
|
||||
}
|
||||
],
|
||||
"overwrite": [],
|
||||
"externalReference": [],
|
||||
"globalMetadata": {
|
||||
"breadcrumb_path": "/release-information/breadcrumb/toc.json",
|
||||
"extendBreadcrumb": true,
|
||||
"feedback_system": "None"
|
||||
},
|
||||
"fileMetadata": {},
|
||||
"template": [],
|
||||
"dest": "release-information",
|
||||
"markdownEngineName": "markdig"
|
||||
}
|
||||
}
|
||||
3
windows/release-information/index.md
Normal file
3
windows/release-information/index.md
Normal file
@ -0,0 +1,3 @@
|
||||
# Welcome to release-information!
|
||||
|
||||
test
|
||||
@ -38,12 +38,18 @@
|
||||
"ms.topic": "article",
|
||||
"feedback_system": "GitHub",
|
||||
"feedback_github_repo": "MicrosoftDocs/windows-itpro-docs",
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
"ms.author": "justinha"
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
"ms.author": "justinha",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "MSDN.security",
|
||||
"folder_relative_path_in_docset": "./"
|
||||
}
|
||||
}
|
||||
},
|
||||
"fileMetadata": {},
|
||||
"template": [],
|
||||
"dest": "security",
|
||||
"markdownEngineName": "dfm"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
@ -13,7 +13,7 @@ manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: conceptual
|
||||
ms.date: 04/02/2019
|
||||
ms.date: 04/17/2019
|
||||
---
|
||||
|
||||
# BitLocker Group Policy settings
|
||||
@ -238,11 +238,11 @@ This policy setting is used to control which unlock options are available for op
|
||||
|
||||
**Reference**
|
||||
|
||||
If you want to use BitLocker on a computer without a TPM, select the **Allow BitLocker without a compatible TPM** check box. In this mode, a USB drive is required for startup. Key information that is used to encrypt the drive is stored on the USB drive, which creates a USB key. When the USB key is inserted, access to the drive is authenticated and the drive is accessible. If the USB key is lost or unavailable, you need to use one of the BitLocker recovery options to access the drive.
|
||||
If you want to use BitLocker on a computer without a TPM, select **Allow BitLocker without a compatible TPM**. In this mode, a password or USB drive is required for startup. The USB drive stores the startup key that is used to encrypt the drive. When the USB drive is inserted, the startup key is authenticated and the operating system drive is accessible. If the USB drive is lost or unavailable, BitLocker recovery is required to access the drive.
|
||||
|
||||
On a computer with a compatible TPM, four types of authentication methods can be used at startup to provide added protection for encrypted data. When the computer starts, it can use:
|
||||
On a computer with a compatible TPM, additional authentication methods can be used at startup to improve protection for encrypted data. When the computer starts, it can use:
|
||||
|
||||
- only the TPM for authentication
|
||||
- only the TPM
|
||||
- insertion of a USB flash drive containing the startup key
|
||||
- the entry of a 4-digit to 20-digit personal identification number (PIN)
|
||||
- a combination of the PIN and the USB flash drive
|
||||
@ -392,7 +392,7 @@ This policy setting allows you to block direct memory access (DMA) for all hot p
|
||||
| **Policy description** | This setting helps prevent attacks that use external PCI-based devices to access BitLocker keys. |
|
||||
| **Introduced** | Windows 10, version 1703 |
|
||||
| **Drive type** | Operating system drives |
|
||||
| **Policy path** | Computer Configuration\Administrative Templates\Windows Components\BitLocker Drive Encryption\Operating System Drives|
|
||||
| **Policy path** | Computer Configuration\Administrative Templates\Windows Components\BitLocker Drive Encryption|
|
||||
| **Conflicts** | None |
|
||||
| **When enabled** | Every time the user locks the screen, DMA will be blocked on hot pluggable PCI ports until the user signs in again. |
|
||||
| **When disabled or not configured** | DMA is available on hot pluggable PCI devices if the device is turned on, regardless of whether a user is signed in.|
|
||||
|
||||
@ -33,12 +33,14 @@ You can create an app protection policy in Intune either with device enrollment
|
||||
- MAM has additional **Access** settings for Windows Hello for Business.
|
||||
- MAM can [selectively wipe company data](https://docs.microsoft.com/intune/apps-selective-wipe) from a user's personal device.
|
||||
- MAM requires an [Azure Active Direcory (Azure AD) Premium license](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis#what-are-the-azure-ad-licenses).
|
||||
- An Azure AD Premium license is also required for WIP auto-recovery, where a device can re-enroll and re-gain access to protected data. WIP auto-recovery depends on Azure AD registration to back up the encryption keys, which requires device auto-enrollment with MDM.
|
||||
- An Azure AD Premium license is also required for WIP auto-recovery, where a device can re-enroll and re-gain access to protected data. WIP auto-recovery depends on Azure AD registration to back up the encryption keys, which requires device auto-enrollment with MDM.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
Before you can create a WIP policy using Intune, you need to configure an MDM or MAM provider in Azure Active Directory (Azure AD). MAM requires an [Azure Active Direcory (Azure AD) Premium license](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis#what-are-the-azure-ad-licenses). An Azure AD Premium license is also required for WIP auto-recovery, where a device can re-enroll and re-gain access to protected data. WIP auto-recovery depends on Azure AD registration to back up the encryption keys, which requires device auto-enrollment with MDM.
|
||||
|
||||
## Configure the MDM or MAM provider
|
||||
|
||||
Before you can create a WIP policy using Intune, you need to configure an MDM or MAM provider in Azure Active Directory (Azure AD).
|
||||
|
||||
1. Sign in to the Azure portal.
|
||||
2. Click **Azure Active Directory** > **Mobility (MDM and MAM)** > **Microsoft Intune**.
|
||||
3. Click **Restore Default URLs** or enter the settings for MDM or MAM user scope and click **Save**:
|
||||
@ -61,7 +63,7 @@ Before you can create a WIP policy using Intune, you need to configure an MDM or
|
||||
|
||||
- **Platform.** Choose **Windows 10**.
|
||||
|
||||
- **Enrollment state.** Choose **Without enrollment** for MAM or **With enrollment** for MDM.
|
||||
- **Enrollment state.** Choose **Without enrollment** for MAM or **With enrollment** for MDM.
|
||||
|
||||
|
||||
|
||||
@ -308,11 +310,11 @@ For more info about AppLocker, see the [AppLocker](https://technet.microsoft.com
|
||||
|
||||
6. On the **Conditions** page, click **Path** and then click **Next**.
|
||||
|
||||
|
||||
|
||||
|
||||
7. Click **Browse Folders...** and select the path for the unsigned apps. For this example, we’re using "C:\Program Files".
|
||||
|
||||
|
||||
|
||||
|
||||
8. On the **Exceptions** page, add any exceptions and then click **Next**.
|
||||
|
||||
@ -609,70 +611,6 @@ Optionally, if you don’t want everyone in your organization to be able to shar
|
||||
>[!NOTE]
|
||||
>For more info about setting the **AllowAzureRMSForEDP** and the **RMSTemplateIDForEDP** MDM settings, see the [EnterpriseDataProtection CSP](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/enterprisedataprotection-csp) topic. For more info about setting up and using a custom template, see [Configuring custom templates for the Azure Rights Management service](https://docs.microsoft.com/information-protection/deploy-use/configure-custom-templates) topic.
|
||||
|
||||
### Configure Windows Hello for Business for MAM
|
||||
If you created a WIP policy for MAM, you can turn on Windows Hello for Business, letting your employees use it as a sign-in method for their devices.
|
||||
|
||||
**To turn on and configure Windows Hello for Business**
|
||||
|
||||
1. From the **Client apps - App protection policies** blade, click the name of your policy, and then click **Advanced settings** from the menu that appears.
|
||||
|
||||
The **Advanced settings** blade appears.
|
||||
|
||||
2. Choose to turn on and configure the Windows Hello for Business settings:
|
||||
|
||||
|
||||
|
||||
- **Use Windows Hello for Business as a method for signing into Windows.** Turns on Windows Hello for Business. The options are:
|
||||
|
||||
- **On.** Turns on Windows Hello For Business for anyone assigned to this policy.
|
||||
|
||||
- **Off.** Turns off Windows Hello for Business.
|
||||
|
||||
- **Set the minimum number of characters required for the PIN.** Enter a numerical value (4-127 characters) for how many characters must be used to create a valid PIN. Default is 4 characters.
|
||||
|
||||
- **Configure the use of uppercase letters in the Windows Hello for Business PIN.** Lets you decide whether uppercase letters can be used in a valid PIN. The options are:
|
||||
|
||||
- **Allow the use of uppercase letters in PIN.** Lets an employee use uppercase letters in a valid PIN.
|
||||
|
||||
- **Require the use of at least one uppercase letter in PIN.** Requires an employee to use at least 1 uppercase letter in a valid PIN.
|
||||
|
||||
- **Do not allow the use of uppercase letters in PIN.** Prevents an employee from using uppercase letters in a valid PIN.
|
||||
|
||||
- **Configure the use of lowercase letters in the Windows Hello for Business PIN.** Lets you decide whether lowercase letters can be used in a valid PIN. The options are:
|
||||
|
||||
- **Allow the use of lowercase letters in PIN.** Lets an employee use lowercase letters in a valid PIN.
|
||||
|
||||
- **Require the use of at least one lowercase letter in PIN.** Requires an employee to use at least 1 lowercase letter in a valid PIN.
|
||||
|
||||
- **Do not allow the use of lowercase letters in PIN.** Prevents an employee from using lowercase letters in a valid PIN.
|
||||
|
||||
- **Configure the use of special characters in the Windows Hello for Business PIN.** Lets you decide whether special characters can be used in a valid PIN. The options are:
|
||||
|
||||
- **Allow the use of special characters in PIN.** Lets an employee use special characters in a valid PIN.
|
||||
|
||||
- **Require the use of at least one special character in PIN.** Requires an employee to use at least 1 special character in a valid PIN.
|
||||
|
||||
- **Do not allow the use of special characters in PIN.** Prevents an employee from using special characters in a valid PIN.
|
||||
|
||||
- **Specify the period of time (in days) that a PIN can be used before the system requires the user to change it.** Enter a numerical value (0-730 days) for how many days can pass before a PIN must be changed. If you enter a value of 0, the PIN never expires.
|
||||
|
||||
- **Specify the number of past PINs that can be associated to a user account that can't be reused.** Enter a numerical value (0-50 days) for how many days can pass before an employee can reuse a previous PIN. If you enter a value of 0, a PINs can be reused immediately and past PINs aren't stored.
|
||||
|
||||
>[!NOTE]
|
||||
>PIN history is not preserved through a PIN reset.
|
||||
|
||||
- **Number of authentication failures allowed before the device will be wiped.** Enter a numerical value for how many times the PIN can be incorrectly entered before wiping the device of corporate data. If you enter a value of 0, the device is never wiped, regardless of the number of incorrect PIN entries.<p>This setting has different behavior for mobile devices and desktops.
|
||||
|
||||
- **On mobile devices.** When an employee reaches the value set here, the device is wiped of corporate data.
|
||||
|
||||
- **On desktop devices.** When an employee reaches the value set here, the desktop is put into BitLocker recovery mode, instead of being wiped. You must have BitLocker installed on the device or this setting is ignored.
|
||||
|
||||
- **Maximum amount of time (in minutes) allowed after the device is idle that will cause the device to become PIN or password locked.** Enter a numerical value for how many days can pass before a PIN must be changed. If you enter a value of 0, the device never becomes PIN or password locked while idle.
|
||||
|
||||
>[!NOTE]
|
||||
>You can set this value to be anything; however, it can't be longer than the time specified by the **Settings** app. If you exceed the maximum timeout value, this setting is ignored.
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
- [How to collect Windows Information Protection (WIP) audit event logs](collect-wip-audit-event-logs.md)
|
||||
@ -685,5 +623,7 @@ If you created a WIP policy for MAM, you can turn on Windows Hello for Business,
|
||||
|
||||
- [Intune MAM Without Enrollment](https://blogs.technet.microsoft.com/configmgrdogs/2016/02/04/intune-mam-without-enrollment/)
|
||||
|
||||
- [Azure RMS Documentation Update for May 2016](https://blogs.technet.microsoft.com/enterprisemobility/2016/05/31/azure-rms-documentation-update-for-may-2016/)
|
||||
|
||||
>[!NOTE]
|
||||
>Help to make this topic better by providing us with edits, additions, and feedback. For info about how to contribute to this topic, see [Editing Windows IT professional documentation](https://github.com/Microsoft/windows-itpro-docs/blob/master/CONTRIBUTING.md).
|
||||
|
||||
@ -13,7 +13,7 @@ manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: conceptual
|
||||
ms.date: 04/11/2019
|
||||
ms.date: 04/15/2019
|
||||
---
|
||||
|
||||
# How Windows Information Protection (WIP) protects a file that has a sensitivity label
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 34 KiB |
@ -12,7 +12,7 @@ manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: conceptual
|
||||
ms.date: 04/10/2019
|
||||
ms.date: 04/05/2019
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
@ -125,7 +125,7 @@ This table provides info about the most common problems you might encounter whil
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>By design, files in the Windows directory tree (%windir% or C:\Windows) cannot be encrypted because they need to be accessed by the system even when no user is signed in. If a file in the Windows directory gets encrypted by one user, the system and other users can't access it.
|
||||
<td>By design, files in the Windows directory (%windir% or C:/Windows) cannot be encrypted because they need to be accessed by any user. If a file in the Windows directory gets encypted by one user, other users can't access it.
|
||||
</td>
|
||||
<td>Any attempt to encrypt a file in the Windows directory will return a file access denied error. But if you copy or drag and drop an encrypted file to the Windows directory, it will retain encryption to honor the intent of the owner.
|
||||
</td>
|
||||
|
||||
@ -1018,23 +1018,17 @@
|
||||
###### [Synchronize directory service data](security-policy-settings/synchronize-directory-service-data.md)
|
||||
###### [Take ownership of files or other objects](security-policy-settings/take-ownership-of-files-or-other-objects.md)
|
||||
|
||||
### [Windows security guidance for enterprises](windows-security-configuration-framework/windows-security-compliance.md)
|
||||
|
||||
### [Windows security compliance](windows-security-configuration-framework/windows-security-compliance.md)
|
||||
#### [Windows security baselines](windows-security-configuration-framework/windows-security-baselines.md)
|
||||
##### [Security Compliance Toolkit](windows-security-configuration-framework/security-compliance-toolkit-10.md)
|
||||
##### [Get support](windows-security-configuration-framework/get-support-for-security-baselines.md)
|
||||
#### [Windows SECCON framework](windows-security-configuration-framework/windows-security-configuration-framework.md)
|
||||
##### [SECCON 1 enterprise administrator security](windows-security-configuration-framework/level-1-enterprise-administrator-security.md)
|
||||
##### [SECCON 2 enterprise dev/ops security](windows-security-configuration-framework/level-2-enterprise-devops-security.md)
|
||||
##### [SECCON 3 enterprise VIP security](windows-security-configuration-framework/level-3-enterprise-vip-security.md)
|
||||
##### [SECCON 4 enterprise high security](windows-security-configuration-framework/level-4-enterprise-high-security.md)
|
||||
##### [SECCON 5 enterprise security](windows-security-configuration-framework/level-5-enterprise-security.md)
|
||||
####Windows Security Blog Posts
|
||||
##### [Sticking with Well-Known and Proven Solutions](windows-security-configuration-framework/windows-security-blog/sticking-with-well-known-and-proven-solutions.md)
|
||||
##### [Why We’re Not Recommending "FIPS Mode" Anymore](windows-security-configuration-framework/windows-security-blog/why-were-not-recommending-fips-mode-anymore.md)
|
||||
##### [Configuring Account Lockout](windows-security-configuration-framework/windows-security-blog/configuring-account-lockout.md)
|
||||
##### [Blocking Remote Use of Local Accounts](windows-security-configuration-framework/windows-security-blog/blocking-remote-use-of-local-accounts.md)
|
||||
##### [Dropping the “Untrusted Font Blocking” setting](windows-security-configuration-framework/windows-security-blog/dropping-the-untrusted-font-blocking-setting.md)
|
||||
#### [Windows security configuration framework](windows-security-configuration-framework/windows-security-configuration-framework.md)
|
||||
##### [Level 5 enterprise security](windows-security-configuration-framework/level-5-enterprise-security.md)
|
||||
##### [Level 4 enterprise high security](windows-security-configuration-framework/level-4-enterprise-high-security.md)
|
||||
##### [Level 3 enterprise VIP security](windows-security-configuration-framework/level-3-enterprise-vip-security.md)
|
||||
##### [Level 2 enterprise dev/ops workstation](windows-security-configuration-framework/level-2-enterprise-devops-security.md)
|
||||
##### [Level 1 enterprise administrator workstation](windows-security-configuration-framework/level-1-enterprise-administrator-security.md)
|
||||
|
||||
### [MBSA removal and alternatives](mbsa-removal-and-guidance.md)
|
||||
|
||||
|
||||
@ -0,0 +1,101 @@
|
||||
---
|
||||
title: Get support
|
||||
description: This article, and the articles it links to, answers frequently asked question on how to get support for Windows baselines, the Security Compliance Toolkit (SCT), and related topics in your organization
|
||||
keywords: virtualization, security, malware
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.author: sagaudre
|
||||
author: justinha
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: conceptual
|
||||
ms.date: 06/25/2018
|
||||
---
|
||||
|
||||
# Get Support
|
||||
|
||||
**What is the Microsoft Security Compliance Manager (SCM)?**
|
||||
|
||||
The Security Compliance Manager (SCM) is now retired and is no longer supported. The reason is that SCM was an incredibly complex and large program that needed to be updated for every Windows release. It has been replaced by the Security Compliance Toolkit (SCT). To provide a better service for our customers, we have moved to SCT with which we can publish baselines through the Microsoft Download Center in a lightweight .zip file that contains GPO backups, GPO reports, Excel spreadsheets, WMI filters, and scripts to apply the settings to local policy.
|
||||
|
||||
More information about this change can be found on the [Microsoft Security Guidance blog](https://blogs.technet.microsoft.com/secguide/2017/06/15/security-compliance-manager-scm-retired-new-tools-and-procedures/).
|
||||
|
||||
**Where can I get an older version of a Windows baseline?**
|
||||
|
||||
Any version of Windows baseline before Windows 10 1703 can still be downloaded using SCM. Any future versions of Windows baseline will be available through SCT. See the version matrix in this article to see if your version of Windows baseline is available on SCT.
|
||||
|
||||
- [SCM 4.0 Download](https://technet.microsoft.com/solutionaccelerators/cc835245.aspx)
|
||||
- [SCM Frequently Asked Questions (FAQ)](https://social.technet.microsoft.com/wiki/contents/articles/1836.microsoft-security-compliance-manager-scm-frequently-asked-questions-faq.aspx)
|
||||
- [SCM Release Notes](https://social.technet.microsoft.com/wiki/contents/articles/1864.microsoft-security-compliance-manager-scm-release-notes.aspx)
|
||||
- [SCM baseline download help](https://social.technet.microsoft.com/wiki/contents/articles/1865.microsoft-security-compliance-manager-scm-baseline-download-help.aspx)
|
||||
|
||||
**What file formats are supported by the new SCT?**
|
||||
|
||||
The toolkit supports formats created by the Windows GPO backup feature (.pol, .inf, and .csv). Policy Analyzer saves its data in XML files with a .PolicyRules file extension. LGPO also supports its own LGPO text file format as a text-based analog for the binary registry.pol file format. See the LGPO documentation for more information. Keep in mind that SCM’s .cab files are no longer supported.
|
||||
|
||||
**Does SCT support Desired State Configuration (DSC) file format?**
|
||||
|
||||
Not yet. PowerShell-based DSC is rapidly gaining popularity, and more DSC tools are coming online to convert GPOs and DSC and to validate system configuration. We are currently developing a tool to provide customers with these features.
|
||||
|
||||
**Does SCT support the creation of System Center Configuration Manager (SCCM) DCM packs?**
|
||||
|
||||
No. A potential alternative is Desired State Configuration (DSC), a feature of the [Windows Management Framework](https://www.microsoft.com/download/details.aspx?id=40855). A tool that supports conversion of GPO backups to DSC format can be found [here](https://github.com/Microsoft/BaselineManagement).
|
||||
|
||||
**Does SCT support the creation of Security Content Automation Protocol (SCAP)-format policies?**
|
||||
|
||||
No. SCM supported only SCAP 1.0, which was not updated as SCAP evolved. The new toolkit likewise does not include SCAP support.
|
||||
|
||||
<br />
|
||||
|
||||
## Version Matrix
|
||||
|
||||
**Client Versions**
|
||||
|
||||
| Name | Build | Baseline Release Date | Security Tools |
|
||||
|---|---|---|---|
|
||||
|Windows 10 | [1709 (RS3)](https://blogs.technet.microsoft.com/secguide/2017/09/27/security-baseline-for-windows-10-fall-creators-update-v1709-draft/) <p> [1703 (RS2)](https://blogs.technet.microsoft.com/secguide/2017/08/30/security-baseline-for-windows-10-creators-update-v1703-final/) <p>[1607 (RS1)](https://blogs.technet.microsoft.com/secguide/2016/10/17/security-baseline-for-windows-10-v1607-anniversary-edition-and-windows-server-2016/) <p>[1511 (TH2)](https://blogs.technet.microsoft.com/secguide/2016/01/22/security-baseline-for-windows-10-v1511-threshold-2-final/) <p>[1507 (TH1)](https://blogs.technet.microsoft.com/secguide/2016/01/22/security-baseline-for-windows-10-v1507-build-10240-th1-ltsb-update/)| October 2017 <p>August 2017 <p>October 2016 <p>January 2016<p> January 2016 |[SCT 1.0](https://www.microsoft.com/download/details.aspx?id=55319) |
|
||||
Windows 8.1 |[9600 (April Update)](https://blogs.technet.microsoft.com/secguide/2014/08/13/security-baselines-for-windows-8-1-windows-server-2012-r2-and-internet-explorer-11-final/)| October 2013| [SCM 4.0](https://technet.microsoft.com/solutionaccelerators/cc835245.aspx) |
|
||||
Windows 8 |[9200](https://technet.microsoft.com/library/jj916413.aspx) |October 2012| [SCM 4.0](https://technet.microsoft.com/solutionaccelerators/cc835245.aspx)|
|
||||
Windows 7 |[7601 (SP1)](https://technet.microsoft.com/library/ee712767.aspx)| October 2009| [SCM 4.0](https://technet.microsoft.com/solutionaccelerators/cc835245.aspx) |
|
||||
| Vista |[6002 (SP2)](https://technet.microsoft.com/library/dd450978.aspx)| January 2007| [SCM 4.0](https://technet.microsoft.com/solutionaccelerators/cc835245.aspx) |
|
||||
| Windows XP |[2600 (SP3)](https://technet.microsoft.com/library/cc163061.aspx)| October 2001| [SCM 4.0](https://technet.microsoft.com/solutionaccelerators/cc835245.aspx)|
|
||||
|
||||
<br />
|
||||
|
||||
**Server Versions**
|
||||
|
||||
| Name | Build | Baseline Release Date | Security Tools |
|
||||
|---|---|---|---|
|
||||
|Windows Server 2016 | [SecGuide](https://blogs.technet.microsoft.com/secguide/2016/10/17/security-baseline-for-windows-10-v1607-anniversary-edition-and-windows-server-2016/) |October 2016 |[SCT 1.0](https://www.microsoft.com/download/details.aspx?id=55319) |
|
||||
|Windows Server 2012 R2|[SecGuide](https://blogs.technet.microsoft.com/secguide/2016/10/17/security-baseline-for-windows-10-v1607-anniversary-edition-and-windows-server-2016/)|August 2014 | [SCT 1.0](https://www.microsoft.com/download/details.aspx?id=55319)|
|
||||
|Windows Server 2012|[Technet](https://technet.microsoft.com/library/jj898542.aspx) |2012| [SCM 4.0](https://technet.microsoft.com/solutionaccelerators/cc835245.aspx) |
|
||||
Windows Server 2008 R2 |[SP1](https://technet.microsoft.com/library/gg236605.aspx)|2009 | [SCM 4.0](https://technet.microsoft.com/solutionaccelerators/cc835245.aspx) |
|
||||
| Windows Server 2008 |[SP2](https://technet.microsoft.com/library/cc514539.aspx)| 2008 | [SCM 4.0](https://technet.microsoft.com/solutionaccelerators/cc835245.aspx) |
|
||||
|Windows Server 2003 R2|[Technet](https://technet.microsoft.com/library/cc163140.aspx)| 2003 | [SCM 4.0](https://technet.microsoft.com/solutionaccelerators/cc835245.aspx)|
|
||||
|Windows Server 2003|[Technet](https://technet.microsoft.com/library/cc163140.aspx)|2003|[SCM 4.0](https://technet.microsoft.com/solutionaccelerators/cc835245.aspx)|
|
||||
|
||||
<br />
|
||||
|
||||
**Microsoft Products**
|
||||
|
||||
| Name | Details | Security Tools |
|
||||
|---|---|---|
|
||||
Internet Explorer 11 | [SecGuide](https://blogs.technet.microsoft.com/secguide/2014/08/13/security-baselines-for-windows-8-1-windows-server-2012-r2-and-internet-explorer-11-final/)|[SCT 1.0](https://www.microsoft.com/download/details.aspx?id=55319)|[SCM 4.0](https://technet.microsoft.com/solutionaccelerators/cc835245.aspx)|
|
||||
|Internet Explorer 10|[Technet](https://technet.microsoft.com/library/jj898540.aspx)|[SCM 4.0](https://technet.microsoft.com/solutionaccelerators/cc835245.aspx) |
|
||||
|Internet Explorer 9|[Technet](https://technet.microsoft.com/library/hh539027.aspx)|[SCM 4.0](https://technet.microsoft.com/solutionaccelerators/cc835245.aspx)
|
||||
|Internet Explorer 8|[Technet](https://technet.microsoft.com/library/ee712766.aspx)|[SCM 4.0](https://technet.microsoft.com/solutionaccelerators/cc835245.aspx)
|
||||
|Exchange Server 2010|[Technet](https://technet.microsoft.com/library/hh913521.aspx)| [SCM 4.0](https://technet.microsoft.com/solutionaccelerators/cc835245.aspx)
|
||||
|Exchange Server 2007|[Technet](https://technet.microsoft.com/library/hh913520.aspx)| [SCM 4.0](https://technet.microsoft.com/solutionaccelerators/cc835245.aspx)
|
||||
|Microsoft Office 2010|[Technet](https://technet.microsoft.com/library/gg288965.aspx)| [SCM 4.0](https://technet.microsoft.com/solutionaccelerators/cc835245.aspx)
|
||||
|Microsoft Office 2007 SP2|[Technet](https://technet.microsoft.com/library/cc500475.aspx)| [SCM 4.0](https://technet.microsoft.com/solutionaccelerators/cc835245.aspx)
|
||||
|
||||
<br />
|
||||
|
||||
> [!NOTE]
|
||||
> Browser baselines are built-in to new OS versions starting with Windows 10
|
||||
|
||||
## See also
|
||||
|
||||
[Windows security baselines](windows-security-baselines.md)
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 122 KiB After Width: | Height: | Size: 62 KiB |
@ -14,9 +14,13 @@ ms.localizationpriority: medium
|
||||
# Threat Protection
|
||||
[Windows Defender Advanced Threat Protection (Windows Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559) is a unified platform for preventative protection, post-breach detection, automated investigation, and response. Windows Defender ATP protects endpoints from cyber threats; detects advanced attacks and data breaches, automates security incidents and improves security posture.
|
||||
|
||||
>[!Note]
|
||||
> The Windows Defender Security Center is currently going through rebranding. All references to Windows Defender will be replaced with Microsoft Defender. You will see the updates in the user interface and in the documentation library in next few months.
|
||||
|
||||
<center><h2>Windows Defender ATP</center></h2>
|
||||
<table>
|
||||
<tr>
|
||||
<td><a href="#tvm"><center><img src="images/TVM_icon.png"> <br><b>Threat & Vulnerability Management</b></center></a></td>
|
||||
<td><a href="#asr"><center><img src="images/ASR_icon.png"> <br><b>Attack surface reduction</b></center></a></td>
|
||||
<td><center><a href="#ngp"><img src="images/NGP_icon.png"><br> <b>Next generation protection</b></a></center></td>
|
||||
<td><center><a href="#edr"><img src="images/EDR_icon.png"><br> <b>Endpoint detection and response</b></a></center></td>
|
||||
@ -25,15 +29,23 @@ ms.localizationpriority: medium
|
||||
<td><center><a href="#mte"><img src="images/MTE_icon.png"><br> <b>Microsoft Threat Experts</b></a></center></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td colspan="6">
|
||||
<td colspan="7">
|
||||
<a href="#apis"><center><b>Management and APIs</a></b></center></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td colspan="6"><a href="#mtp"><center><b>Microsoft Threat Protection</a></center></b></td>
|
||||
<td colspan="7"><a href="#mtp"><center><b>Microsoft Threat Protection</a></center></b></td>
|
||||
</tr>
|
||||
</table>
|
||||
<br>
|
||||
|
||||
<a name="tvm"></a>
|
||||
|
||||
**[Threat & Vulnerability Management](windows-defender-atp/next-gen-threat-and-vuln-mgt.md)**<br>
|
||||
This built-in capability uses a game-changing risk-based approach to the discovery, prioritization, and remediation of endpoint vulnerabilities and misconfigurations.
|
||||
- [Risk-based Threat & Vulnerability Management](windows-defender-atp/next-gen-threat-and-vuln-mgt.md)
|
||||
- [What's in the dashboard and what it means for my organization](windows-defender-atp/tvm-dashboard-insights.md)
|
||||
- [Configuration score](windows-defender-atp/configuration-score.md)
|
||||
- [Scenarios](windows-defender-atp/threat-and-vuln-mgt-scenarios.md)
|
||||
|
||||
<a name="asr"></a>
|
||||
|
||||
|
||||
@ -0,0 +1,72 @@
|
||||
---
|
||||
title: Microsoft Security Compliance Toolkit 1.0
|
||||
description: This article describes how to use the Security Compliance Toolkit in your organization
|
||||
keywords: virtualization, security, malware
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.author: sagaudre
|
||||
author: justinha
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: conceptual
|
||||
ms.date: 11/26/2018
|
||||
---
|
||||
|
||||
# Microsoft Security Compliance Toolkit 1.0
|
||||
|
||||
## What is the Security Compliance Toolkit (SCT)?
|
||||
|
||||
The Security Compliance Toolkit (SCT) is a set of tools that allows enterprise security administrators to download, analyze, test, edit, and store Microsoft-recommended security configuration baselines for Windows and other Microsoft products.
|
||||
|
||||
The SCT enables administrators to effectively manage their enterprise’s Group Policy Objects (GPOs). Using the toolkit, administrators can compare their current GPOs with Microsoft-recommended GPO baselines or other baselines, edit them, store them in GPO backup file format, and apply them broadly through Active Directory or individually through local policy.
|
||||
<p></p>
|
||||
|
||||
The Security Compliance Toolkit consists of:
|
||||
|
||||
- Windows 10 security baselines
|
||||
- Windows 10 Version 1809 (October 2018 Update)
|
||||
- Windows 10 Version 1803 (April 2018 Update)
|
||||
- Windows 10 Version 1709 (Fall Creators Update)
|
||||
- Windows 10 Version 1703 (Creators Update)
|
||||
- Windows 10 Version 1607 (Anniversary Update)
|
||||
- Windows 10 Version 1511 (November Update)
|
||||
- Windows 10 Version 1507
|
||||
|
||||
- Windows Server security baselines
|
||||
- Windows Server 2019
|
||||
- Windows Server 2016
|
||||
- Windows Server 2012 R2
|
||||
|
||||
- Microsoft Office security baseline
|
||||
- Office 2016
|
||||
|
||||
- Tools
|
||||
- Policy Analyzer tool
|
||||
- Local Group Policy Object (LGPO) tool
|
||||
|
||||
|
||||
You can [download the tools](https://www.microsoft.com/download/details.aspx?id=55319) along with the baselines for the relevant Windows versions. For more details about security baseline recommendations, see the [Microsoft Security Guidance blog](https://blogs.technet.microsoft.com/secguide/).
|
||||
|
||||
## What is the Policy Analyzer tool?
|
||||
|
||||
The Policy Analyzer is a utility for analyzing and comparing sets of Group Policy Objects (GPOs). Its main features include:
|
||||
- Highlight when a set of Group Policies has redundant settings or internal inconsistencies
|
||||
- Highlight the differences between versions or sets of Group Policies
|
||||
- Compare GPOs against current local policy and local registry settings
|
||||
- Export results to a Microsoft Excel spreadsheet
|
||||
|
||||
Policy Analyzer lets you treat a set of GPOs as a single unit. This makes it easy to determine whether particular settings are duplicated across the GPOs or are set to conflicting values. Policy Analyzer also lets you capture a baseline and then compare it to a snapshot taken at a later time to identify changes anywhere across the set.
|
||||
|
||||
More information on the Policy Analyzer tool can be found on the [Microsoft Security Guidance blog](https://blogs.technet.microsoft.com/secguide/2016/01/22/new-tool-policy-analyzer/) or by [downloading the tool](https://www.microsoft.com/download/details.aspx?id=55319).
|
||||
|
||||
## What is the Local Group Policy Object (LGPO) tool?
|
||||
|
||||
LGPO.exe is a command-line utility that is designed to help automate management of Local Group Policy.
|
||||
Using local policy gives administrators a simple way to verify the effects of Group Policy settings, and is also useful for managing non-domain-joined systems.
|
||||
LGPO.exe can import and apply settings from Registry Policy (Registry.pol) files, security templates, Advanced Auditing backup files, as well as from formatted “LGPO text” files.
|
||||
It can export local policy to a GPO backup.
|
||||
It can export the contents of a Registry Policy file to the “LGPO text” format that can then be edited, and can build a Registry Policy file from an LGPO text file.
|
||||
|
||||
Documentation for the LGPO tool can be found on the [Microsoft Security Guidance blog](https://blogs.technet.microsoft.com/secguide/2016/01/21/lgpo-exe-local-group-policy-object-utility-v1-0/) or by [downloading the tool](https://www.microsoft.com/download/details.aspx?id=55319).
|
||||
@ -12,7 +12,7 @@ manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: conceptual
|
||||
ms.date: 04/10/2019
|
||||
ms.date: 10/16/2017
|
||||
---
|
||||
|
||||
# AppLocker
|
||||
@ -92,7 +92,7 @@ AppLocker is included with enterprise-level editions of Windows. You can author
|
||||
|
||||
### Using AppLocker on Server Core
|
||||
|
||||
AppLocker on Server Core installations is not supported. This applies to all versions of Windows Server.
|
||||
AppLocker on Server Core installations is not supported.
|
||||
|
||||
### Virtualization considerations
|
||||
|
||||
|
||||
@ -12,7 +12,7 @@ manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: conceptual
|
||||
ms.date: 03/11/2019
|
||||
ms.date: 09/21/2017
|
||||
---
|
||||
|
||||
# Requirements to use AppLocker
|
||||
@ -31,15 +31,14 @@ To use AppLocker, you need:
|
||||
- For Group Policy deployment, at least one device with the Group Policy Management Console (GPMC) or Remote Server Administration Tools (RSAT) installed to host the AppLocker rules.
|
||||
- Devices running a supported operating system to enforce the AppLocker rules that you create.
|
||||
|
||||
>[!NOTE]
|
||||
>You can use Software Restriction Policies with AppLocker, but with some limitations. For more info, see [Use AppLocker and Software Restriction Policies in the same domain](use-applocker-and-software-restriction-policies-in-the-same-domain.md).
|
||||
>**Note:** You can use Software Restriction Policies with AppLocker, but with some limitations. For more info, see [Use AppLocker and Software Restriction Policies in the same domain](use-applocker-and-software-restriction-policies-in-the-same-domain.md).
|
||||
|
||||
## Operating system requirements
|
||||
|
||||
The following table shows AppLocker features supported by different versions of Windows.
|
||||
The following table show the on which operating systems AppLocker features are supported.
|
||||
|
||||
| Version | Can be configured | Can be enforced | Available rules | Notes |
|
||||
|---|---|---|---|---|
|
||||
| - | - | - | - | - |
|
||||
| Windows 10| Yes| Yes| Packaged apps<br/>Executable<br/>Windows Installer<br/>Script<br/>DLL| You can use the [AppLocker CSP](https://msdn.microsoft.com/library/windows/hardware/dn920019.aspx) to configure AppLocker policies on any edition of Windows 10 supported by Mobile Device Management (MDM). You can only manage AppLocker with Group Policy on devices running Windows 10 Enterprise, Windows 10 Education, and Windows Server 2016. |
|
||||
| Windows Server 2016<br/>Windows Server 2012 R2<br/>Windows Server 2012| Yes| Yes| Packaged apps<br/>Executable<br/>Windows Installer<br/>Script<br/>DLL| |
|
||||
| Windows 8.1 Pro| Yes| No| N/A||
|
||||
@ -56,7 +55,8 @@ The following table shows AppLocker features supported by different versions of
|
||||
| Windows 7 Enterprise| Yes| Yes| Executable<br/>Windows Installer<br/>Script<br/>DLL| Packaged app rules will not be enforced.|
|
||||
| Windows 7 Professional| Yes| No| Executable<br/>Windows Installer<br/>Script<br/>DLL| No AppLocker rules are enforced.|
|
||||
|
||||
Previous versions of Windows can use Software Restriction Policies.
|
||||
|
||||
AppLocker is not supported on versions of the Windows operating system not listed above. Software Restriction Policies can be used with those versions. However, the SRP Basic User feature is not supported on the above operating systems.
|
||||
|
||||
## See also
|
||||
- [Administer AppLocker](administer-applocker.md)
|
||||
|
||||
@ -1,6 +1,12 @@
|
||||
# [Windows Defender Advanced Threat Protection](windows-defender-advanced-threat-protection.md)
|
||||
|
||||
## [Overview](overview.md)
|
||||
### [Threat & Vulnerability Management](next-gen-threat-and-vuln-mgt.md)
|
||||
#### [What's in the dashboard and what it means for my organization](tvm-dashboard-insights.md)
|
||||
#### [Configuration score](configuration-score.md)
|
||||
#### [Scenarios](threat-and-vuln-mgt-scenarios.md)
|
||||
|
||||
|
||||
### [Attack surface reduction](overview-attack-surface-reduction.md)
|
||||
#### [Hardware-based isolation](overview-hardware-based-isolation.md)
|
||||
##### [Application isolation](../windows-defender-application-guard/wd-app-guard-overview.md)
|
||||
@ -32,6 +38,7 @@
|
||||
##### [Investigate an IP address](investigate-ip-windows-defender-advanced-threat-protection.md)
|
||||
##### [Investigate a domain](investigate-domain-windows-defender-advanced-threat-protection.md)
|
||||
##### [Investigate a user account](investigate-user-windows-defender-advanced-threat-protection.md)
|
||||
|
||||
|
||||
#### Machines list
|
||||
##### [View and organize the Machines list](machines-view-overview-windows-defender-advanced-threat-protection.md)
|
||||
@ -70,10 +77,11 @@
|
||||
|
||||
|
||||
### [Secure score](overview-secure-score-windows-defender-advanced-threat-protection.md)
|
||||
|
||||
### [Microsoft Threat Experts](microsoft-threat-experts.md)
|
||||
|
||||
### [Threat analytics](threat-analytics.md)
|
||||
|
||||
|
||||
|
||||
### [Advanced hunting](overview-hunting-windows-defender-advanced-threat-protection.md)
|
||||
#### [Query data using Advanced hunting](advanced-hunting-windows-defender-advanced-threat-protection.md)
|
||||
##### [Advanced hunting reference](advanced-hunting-reference-windows-defender-advanced-threat-protection.md)
|
||||
@ -81,23 +89,16 @@
|
||||
#### [Custom detections](overview-custom-detections.md)
|
||||
#####[Create custom detections rules](custom-detection-rules.md)
|
||||
|
||||
|
||||
### [Management and APIs](management-apis.md)
|
||||
#### [Understand threat intelligence concepts](threat-indicator-concepts-windows-defender-advanced-threat-protection.md)
|
||||
#### [Windows Defender ATP APIs](apis-intro.md)
|
||||
#### [Managed security service provider support](mssp-support-windows-defender-advanced-threat-protection.md)
|
||||
|
||||
|
||||
### [Microsoft Threat Protection](threat-protection-integration.md)
|
||||
#### [Protect users, data, and devices with conditional access](conditional-access-windows-defender-advanced-threat-protection.md)
|
||||
#### [Microsoft Cloud App Security in Windows overview](microsoft-cloud-app-security-integration.md)
|
||||
#### [Information protection in Windows overview](information-protection-in-windows-overview.md)
|
||||
|
||||
|
||||
|
||||
### [Microsoft Threat Experts](microsoft-threat-experts.md)
|
||||
|
||||
|
||||
### [Portal overview](portal-overview-windows-defender-advanced-threat-protection.md)
|
||||
|
||||
|
||||
@ -212,6 +213,8 @@
|
||||
|
||||
### [Configure Secure score dashboard security controls](secure-score-dashboard-windows-defender-advanced-threat-protection.md)
|
||||
|
||||
### [Configure and manage Microsoft Threat Experts capabilities](configure-microsoft-threat-experts.md)
|
||||
|
||||
### Management and API support
|
||||
#### [Onboard machines](onboard-configure-windows-defender-advanced-threat-protection.md)
|
||||
##### [Onboard previous versions of Windows](onboard-downlevel-windows-defender-advanced-threat-protection.md)
|
||||
@ -343,11 +346,6 @@
|
||||
|
||||
#### [Configure managed security service provider (MSSP) support](configure-mssp-support-windows-defender-advanced-threat-protection.md)
|
||||
|
||||
|
||||
|
||||
|
||||
### [Configure and manage Microsoft Threat Experts capabilities](configure-microsoft-threat-experts.md)
|
||||
|
||||
### Configure Microsoft Threat Protection integration
|
||||
#### [Configure conditional access](configure-conditional-access-windows-defender-advanced-threat-protection.md)
|
||||
#### [Configure Microsoft Cloud App Security in Windows](microsoft-cloud-app-security-config.md)
|
||||
@ -385,8 +383,6 @@
|
||||
##### [Offboarding machines](offboard-machines-windows-defender-advanced-threat-protection.md)
|
||||
|
||||
#### [Configure Windows Security app time zone settings](time-settings-windows-defender-advanced-threat-protection.md)
|
||||
|
||||
|
||||
|
||||
|
||||
## [Troubleshoot Windows Defender ATP](troubleshoot-wdatp.md)
|
||||
|
||||
@ -42,6 +42,8 @@ To effectively build queries that span multiple tables, you need to understand t
|
||||
| AdditionalFields | string | Additional information about the event in JSON array format |
|
||||
| AlertId | string | Unique identifier for the alert |
|
||||
| AppGuardContainerId | string | Identifier for the virtualized container used by Application Guard to isolate browser activity |
|
||||
| Category | string | Type of threat indicator or breach activity identified by the alert |
|
||||
| ClientVersion | string | Version of the endpoint agent or sensor running on the machine |
|
||||
| ComputerName | string | Fully qualified domain name (FQDN) of the machine |
|
||||
| ConnectedNetworks | string | Networks that the adapter is connected to. Each JSON array contains the network name, category (public, private or domain), a description, and a flag indicating if it’s connected publicly to the internet. |
|
||||
| DefaultGateways | string | Default gateway addresses in JSON array format |
|
||||
@ -73,6 +75,8 @@ To effectively build queries that span multiple tables, you need to understand t
|
||||
| Ipv4Dhcp | string | IPv4 address of DHCP server |
|
||||
| Ipv6Dhcp | string | IPv6 address of DHCP server |
|
||||
| IsAzureADJoined | boolean | Boolean indicator of whether machine is joined to the Azure Active Directory |
|
||||
| IsAzureInfoProtectionApplied | boolean | Indicates whether the file is encrypted by Azure Information Protection |
|
||||
| IsWindowsInfoProtectionApplied | boolean | Indicates whether Windows Information Protection (WIP) policies apply to the file |
|
||||
| LocalIP | string | IP address assigned to the local machine used during communication |
|
||||
| LocalPort | int | TCP port on the local machine used during communication |
|
||||
| LocalIPType | string | Type of IP address, for example Public, Private, Reserved, Loopback, Teredo, FourToSixMapping, and Broadcast |
|
||||
@ -89,6 +93,7 @@ To effectively build queries that span multiple tables, you need to understand t
|
||||
| OSArchitecture | string | Architecture of the operating system running on the machine |
|
||||
| OSBuild | string | Build version of the operating system running on the machine |
|
||||
| OSPlatform | string | Platform of the operating system running on the machine. This indicates specific operating systems, including variations within the same family, such as Windows 10 and Windows 7. |
|
||||
| OsVersion | string | Version of the operating system running on the machine |
|
||||
| PreviousRegistryKey | string | Original registry key of the registry value before it was modified |
|
||||
| PreviousRegistryValueData | string | Original data of the registry value before it was modified |
|
||||
| PreviousRegistryValueName | string | Original name of the registry value before it was modified |
|
||||
@ -110,8 +115,12 @@ To effectively build queries that span multiple tables, you need to understand t
|
||||
| RemotePort | int | TCP port on the remote device that was being connected to |
|
||||
| RemoteUrl | string | URL or fully qualified domain name (FQDN) that was being connected to |
|
||||
| ReportId | long | Event identifier based on a repeating counter. To identify unique events, this column must be used in conjunction with the ComputerName and EventTime columns. |
|
||||
| Severity | string | Indicates the potential impact (high, medium, or low) of the threat indicator or breach activity identified by the alert |
|
||||
| SensitivityLabel | string | Label applied to an email, file, or other content to classify it for information protection |
|
||||
| SensitivitySubLabel | string | Sublabel applied to an email, file, or other content to classify it for information protection; sensitivity sublabels are grouped under sensitivity labels but are treated independently |
|
||||
| SHA1 | string | SHA-1 of the file that the recorded action was applied to |
|
||||
| SHA256 | string | SHA-256 of the file that the recorded action was applied to. This field is usually not populated—use the SHA1 column when available. |
|
||||
| RegistryMachineTag | string | Machine tag added through the registry |
|
||||
| Table | string | Table that contains the details of the event |
|
||||
| TunnelingType | string | Tunneling protocol, if the interface is used for this purpose, for example 6to4, Teredo, ISATAP, PPTP, SSTP, and SSH |
|
||||
|
||||
|
||||
@ -0,0 +1,56 @@
|
||||
---
|
||||
title: Overview of Configuration score in Microsoft Defender Security Center
|
||||
description: Expand your visibility into the overall security configuration posture of your organization
|
||||
keywords: configuration score, mdatp configuration score, secure score, security controls, improvement opportunities, security configuration score over time, security posture, baseline
|
||||
search.product: Windows 10
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.author: dolmont
|
||||
author: DulceMontemayor
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: conceptual
|
||||
ms.date: 04/11/2019
|
||||
---
|
||||
# Configuration score
|
||||
**Applies to:**
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
[!include[Prerelease<73>information](prerelease.md)]
|
||||
|
||||
>[!NOTE]
|
||||
> Secure score is now part of Threat & Vulnerability Management as Configuration score. We’ll keep the secure score page available for a few weeks. View the [Secure score](https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-atp/overview-secure-score-windows-defender-advanced-threat-protection) page.
|
||||
|
||||
The Microsoft Defender Advanced Threat Protection Configuration score gives you visibility and control over your organization's security posture based on security best practices.
|
||||
|
||||
Your configuration score widget shows the collective security configuration state of your machines across the following categories:
|
||||
- Application
|
||||
- Operating system
|
||||
- Network
|
||||
- Accounts
|
||||
- Security controls
|
||||
|
||||
## How it works
|
||||
|
||||
What you'll see in the configuration score widget is the product of meticulous and ongoing vulnerability discovery process aggregated with configuration discovery assessments that continuously:
|
||||
- Compare collected configurations to the collected benchmarks to discover misconfigured assets
|
||||
- Map configurations to vulnerabilities that can be remediated or partially remediated (risk reduction) by remediating the misconfiguration
|
||||
- Collect and maintain best practice configuration benchmarks (vendors, security feeds, internal research teams)
|
||||
- Collect and monitor changes of security control configuration state from all assets
|
||||
|
||||
From the widget, you'd be able to see which security aspect require attention. You can click the configuration score categories and it will take you to the **Security recommendations** page to see more details and understand the context of the issue. From there, you can take action based on security benchmarks.
|
||||
|
||||
## Improve your configuration score
|
||||
The goal is to improve your configuration score by remediating the issues in the security recommendations list. You can filter the view based on:
|
||||
- **Related component** - **Accounts**, **Application**, **Network**, **OS**, or **Security controls**
|
||||
- **Remediation type** - **Configuration change** or **Software update**
|
||||
|
||||
## Related topics
|
||||
- [Risk-based Threat & Vulnerability Management](next-gen-threat-and-vuln-mgt.md)
|
||||
- [Threat & Vulnerability Management dashboard overview](tvm-dashboard-insights.md)
|
||||
- [Scenarios](threat-and-vuln-mgt-scenarios.md)
|
||||
@ -0,0 +1,44 @@
|
||||
---
|
||||
title: Configure Threat & Vulnerability Management in Windows Defender ATP
|
||||
description: Configure your Threat & Vulnerability Management to allow security administrators and IT administrators to collaborate seamlessly to remediate issues via Microsoft intune and Microsoft System Center Configuration Manager (SCCM) integrations.
|
||||
keywords: RBAC, Threat & Vulnerability Management configuration, Threat & Vulnerability Management integrations, Microsft Intune integration with TVM, SCCM integration with TVM
|
||||
search.product: Windows 10
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.author: dolmont
|
||||
author: DulceMontemayor
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
---
|
||||
# Configure Threat & Vulnerability Management
|
||||
**Applies to:**
|
||||
- [Windows Defender Advanced Threat Protection Windows Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
[!include[Prerelease<73>information](prerelease.md)]
|
||||
|
||||
This section guides you through the steps you need to take to configure Threat & Vulnerability Management's integration with Microsoft Intune or Microsoft System Center Configuration Manager (SCCM) for a seamless collaboration of issue remediation.
|
||||
|
||||
### Before you begin
|
||||
>[!IMPORTANT]
|
||||
Threat & Vulnerability Management data currently supports Windows 10 machines. Upgrade to Windows 10 to account for the rest of your devices’ threat and vulnerability exposure data.</br>
|
||||
|
||||
Ensure that you have the right RBAC permissions to configure your Threat & Vulnerability Management integration with Microsoft Intune or Microsoft System Center Configuration Manager (SCCM).
|
||||
|
||||
>[!WARNING]
|
||||
>Only Intune and SCCM enrolled devices are supported in this scenario.</br>
|
||||
>Use any of the following options to enroll devices in Intune:
|
||||
>- IT Admin: For more information on how to enabling auto-enrollment, see [Windows Enrollment](https://docs.microsoft.com/intune/windows-enroll#enable-windows-10-automatic-enrollment)
|
||||
>- End-user: For more information on how to enroll your Windows 10 device in Intune, see [Enroll your Windows 10 device in Intune](https://docs.microsoft.com/intune-user-help/enroll-your-w10-device-access-work-or-school)
|
||||
>- End-user alternative: For more information on joining an Azure AD domain, see [Set up Azure Active Directory joined devices](https://docs.microsoft.com/azure/active-directory/device-management-azuread-joined-devices-setup).
|
||||
|
||||
## Related topics
|
||||
- [Risk-based Threat & Vulnerability Management](next-gen-threat-and-vuln-mgt.md)
|
||||
- [Threat & Vulnerability Management dashboard overview](tvm-dashboard-insights.md)
|
||||
- [Configuration score](configuration-score.md)
|
||||
- [Scenarios](threat-and-vuln-mgt-scenarios.md)
|
||||
@ -9,7 +9,7 @@ ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.author: dolmont
|
||||
author: DulceMV
|
||||
author: DulceMontemayor
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
|
||||
@ -31,6 +31,9 @@ Learn about the minimum requirements and initial steps you need to take to get s
|
||||
|
||||
The following capabilities are available across multiple products that make up the Windows Defender ATP platform.
|
||||
|
||||
**Threat & Vulnerability Management**<br>
|
||||
Effectively identifying, assessing, and remediating endpoint weaknesses is pivotal in running a healthy security program and reducing organizational risk. This infrastructure correlates endpoint detection and response (EDR) insights with endpoint vulnerabilities real-time, thus reducing organizational vulnerability exposure and increasing threat resilience.
|
||||
|
||||
**Attack surface reduction**<br>
|
||||
The attack surface reduction set of capabilities provide the first line of defense in the stack. By ensuring configuration settings are properly set and exploit mitigation techniques are applied, these set of capabilities resist attacks and exploitations.
|
||||
|
||||
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 1.3 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 1.2 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 19 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 137 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 13 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 21 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 995 B |
Binary file not shown.
|
After Width: | Height: | Size: 69 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 10 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 3.3 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 20 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 8.9 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 61 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 24 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 74 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 54 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 14 KiB |
@ -37,12 +37,9 @@ You can define the conditions for when entities are identified as malicious or s
|
||||
## Create an allowed or blocked list
|
||||
1. In the navigation pane, select **Settings** > **Automation allowed/blocked list**.
|
||||
|
||||
2. Select the tab of the type of entity you'd like to create an exclusion for. You can choose any of the following entities:
|
||||
- File hash
|
||||
- Certificate
|
||||
- IP address
|
||||
|
||||
3. Click **Add system exclusion**.
|
||||
2. Select the tab of the type of entity you'd like to create an exclusion for. Currently, you can add a rule for certificates.
|
||||
|
||||
3. Select **Add allowed/blocked list rule**.
|
||||
|
||||
4. For each attribute specify the exclusion type, details, and their corresponding required values.
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.author: dolmont
|
||||
author: DulceMV
|
||||
author: DulceMontemayor
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
|
||||
@ -0,0 +1,67 @@
|
||||
---
|
||||
title: Next-generation Threat & Vulnerability Management
|
||||
description: This new capability uses a game-changing risk-based approach to the discovery, prioritization, and remediation of endpoint vulnerabilities and misconfigurations.
|
||||
keywords: threat and vulnerability management, MDATP-TVM, vulnerability management, threat and vulnerability scanning
|
||||
search.product: Windows 10
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.author: dolmont
|
||||
author: DulceMontemayor
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: conceptual
|
||||
---
|
||||
|
||||
# Threat & Vulnerability Management
|
||||
**Applies to:**
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
[!include[Prerelease<73>information](prerelease.md)]
|
||||
|
||||
Effectively identifying, assessing, and remediating endpoint weaknesses is pivotal in running a healthy security program and reducing organizational risk. Threat & Vulnerability Management serves as an infrustructure for reducing organizational exposure, hardening endpoint surface area, and increasing organizational resilience.
|
||||
|
||||
It helps organizations discover vulnerabilities and misconfigurations in real-time, based on sensors, without the need of agents or periodic scans. It prioritizes vulnerabilities based on the threat landscape, detections in your organization, sensitive information on vulnerable devices, and business context.
|
||||
|
||||
## Next-generation capabilities
|
||||
Threat & Vulnerability Management is built-in, real-time, cloud-powered, fully integrated with Microsoft endpoint security stack, the Microsoft Intelligent Security Graph, and the application analytics knowledgebase.
|
||||
|
||||
It is the first solution in the industry to automate the remediation process through integration with Microsoft Intune and Microsoft System Center Configuration Manager (SCCM) for patching, configuration changes, or upgrades.
|
||||
>[!Note]
|
||||
> Microsoft Intune and Microsoft System Center Configuration Manager (SCCM) integration will be available in the coming weeks.
|
||||
|
||||
It provides the following solutions to frequently-cited gaps across security operations, security administration, and IT administration workflows and communication.
|
||||
- Real-time endpoint detection and response (EDR) insights correlated with endpoint vulnerabilities
|
||||
- Linked machine vulnerability and security configuration assessment data in the context of exposure discovery
|
||||
- Built-in remediation processes through Microsoft Intune and Microsoft System Center Configuration Manager
|
||||
|
||||
### Real-time discovery
|
||||
|
||||
To discover endpoint vulnerabilities and misconfiguration, Threat & Vulnerability Management uses the same agentless built-in Microsoft Defender ATP sensors to reduce cumbersome network scans and IT overhead, and provides:
|
||||
- Real-time device inventory. Devices onboarded to Microsoft Defender ATP automatically report and push vulnerability and security configuration data to the dashboard.
|
||||
- Visibility into software and vulnerabilities. Optics into the organization’s software inventory, as well as software changes like installations, uninstallations, and patches. Newly discovered vulnerabilities are reported with actionable mitigation recommendations for 1st and 3rd party applications.
|
||||
- Application runtime context. Constant visibility into application usage patterns for better prioritization and decision-making. Critical dependencies, such as vulnerable runtime libraries being loaded by other applications, are made visible.
|
||||
- Configuration posture. Visibility into organizational security configuration, surfacing issues like disabled antivirus, enabled SMBv1, or misconfigurations that could allow escalation of privileges. Issues are reported in the dashboard with actionable security recommendations.
|
||||
|
||||
### Intelligence-driven prioritization
|
||||
|
||||
Threat & Vulnerability Management helps customers prioritize and focus on those weaknesses that pose the most urgent and the highest risk to the organization. Rather than using static prioritization by severity scores, Threat & Vulnerability Management in Microsoft Defender ATP highlights the most critical weaknesses that need attention by fusing its security recommendations with dynamic threat and business context:
|
||||
- Exposing emerging attacks in the wild. Through its advanced cyber data and threat analytics platform, Threat & Vulnerability Management dynamically aligns the prioritization of its security recommendations to focus on vulnerabilities that are currently being exploited in the wild and emerging threats that pose the highest risk.
|
||||
- Pinpointing active breaches. Microsoft Defender ATP correlates Threat & Vulnerability Management and EDR insights to provide the unique ability to prioritize vulnerabilities that are currently being exploited in an active breach within the organization.
|
||||
- Protecting high-value assets. Microsoft Defender ATP’s integration with Azure Information Protection allows Threat & Vulnerability Management to call attention to exposed machines with business-critical applications, confidential data, or high-value users.
|
||||
|
||||
### Seamless remediation
|
||||
|
||||
Microsoft Defender ATP’s Threat & Vulnerability Management allows security administrators and IT administrators to collaborate seamlessly to remediate issues.
|
||||
- One-click remediation requests to IT. Through Microsoft Defender ATP’s integration with Microsoft Intune and System Center Configuration Manager (SCCM), security administrators can create a remediation task in Microsoft Intune with one click. We plan to expand this capability to other IT security management platforms.
|
||||
- Alternate mitigations. Threat & Vulnerability Management provides insights on additional mitigations, such as configuration changes that can reduce risk associated with software vulnerabilities.
|
||||
- Real-time remediation status. Microsoft Defender ATP provides real-time monitoring of the status and progress of remediation activities across the organization.
|
||||
|
||||
## Related topics
|
||||
- [Threat & Vulnerability Management dashboard overview](tvm-dashboard-insights.md)
|
||||
- [Configuration score](configuration-score.md)
|
||||
- [Scenarios](threat-and-vuln-mgt-scenarios.md)
|
||||
@ -33,6 +33,7 @@ Understand the concepts behind the capabilities in Windows Defender ATP so you t
|
||||
|
||||
Topic | Description
|
||||
:---|:---
|
||||
[Threat & Vulnerability Management](next-gen-threat-and-vuln-mgt.md) | Reduce organizational vulnerability exposure and increase threat resilience while seamlessly connecting workflows across security stakeholders—security administrators, security operations, and IT administrators in remediating threats.
|
||||
[Attack surface reduction](overview-attack-surface-reduction.md) | Leverage the attack surface reduction capabilities to protect the perimeter of your organization.
|
||||
[Next generation protection](../windows-defender-antivirus/windows-defender-antivirus-in-windows-10.md) | Learn about the antivirus capabilities in Windows Defender ATP so you can protect desktops, portable computers, and servers.
|
||||
[Endpoint detection and response](overview-endpoint-detection-response.md) | Understand how Windows Defender ATP continuously monitors your organization for possible attacks against systems, networks, or users in your organization and the features you can use to mitigate and remediate threats.
|
||||
|
||||
@ -108,10 +108,13 @@ Icon | Description
|
||||
 | Automated investigation - running
|
||||
 | Automated investigation - remediated
|
||||
 | Automated investigation - partially remediated
|
||||
 | Threat & Vulnerability Management - threat insights
|
||||
 | Threat & Vulnerability Management - possible active alert
|
||||
 | Threat & Vulnerability Management - recommendation insights
|
||||
|
||||
|
||||
## Related topics
|
||||
- [Understand the Windows Defender Advanced Threat Protection portal](use-windows-defender-advanced-threat-protection.md)
|
||||
- [View the Security operations dashboard](security-operations-dashboard-windows-defender-advanced-threat-protection.md)
|
||||
- [View the Secure Score dashboard and improve your secure score](secure-score-dashboard-windows-defender-advanced-threat-protection.md)
|
||||
- [View the Threat analytics dashboard and take recommended mitigation actions](threat-analytics-dashboard-windows-defender-advanced-threat-protection.md)
|
||||
- [View the Threat analytics dashboard and take recommended mitigation actions](threat-analytics-dashboard-windows-defender-advanced-threat-protection.md)
|
||||
|
||||
@ -0,0 +1,107 @@
|
||||
---
|
||||
title: Threat & Vulnerability Management scenarios
|
||||
description:
|
||||
keywords:
|
||||
search.product: Windows 10
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.author: dolmont
|
||||
author: DulceMontemayor
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Threat & Vulnerability Management scenarios
|
||||
**Applies to:**
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
[!include[Prerelease<73>information](prerelease.md)]
|
||||
|
||||
## Before you begin
|
||||
Ensure that your machines:
|
||||
- Are onboarded to Microsoft Defender Advanced Threat Protection
|
||||
- Running with Windows 10 1709 (Fall Creators Update) or later
|
||||
- Have the following mandatory updates installed:
|
||||
- (1) RS3 customers | [KB4493441](https://support.microsoft.com/en-us/help/4493441/windows-10-update-kb4493441)
|
||||
- (2) RS4 customers | [KB4493464](https://support.microsoft.com/en-us/help/4493464)
|
||||
- Have at least one security recommendation that can be viewed in the machine page
|
||||
- Are tagged or marked as co-managed
|
||||
|
||||
|
||||
## Reduce your threat and vulnerability exposure
|
||||
Threat & Vulnerability Management introduces a new exposure score metric which visually represents how exposed your machines are to imminent threats.
|
||||
|
||||
The exposure score is continuously calculated on each device in the organization and influenced by the following factors:
|
||||
- Weaknesses, such as vulnerabilities and misconfigurations discovered on the device
|
||||
- External and internal threats such as public exploit code and security alerts
|
||||
- Likelihood of the device getting breached given its current security posture
|
||||
- Value of the device to the organization given its role and content
|
||||
|
||||
The exposure score is broken down into the following levels:
|
||||
- 0 to 29: low exposure score
|
||||
- 30 to 69: medium exposure score
|
||||
- 70 to 100: high exposure score
|
||||
|
||||
You can reduce the exposure score by remediating issues based on prioritized security recommendations. Each software has weaknesses that are transformed into recommendations and prioritized based on risk to the organization.
|
||||
|
||||
To lower down your threat and vulnerability exposure:
|
||||
|
||||
1. Review the **Top security recommendations** from your **Threat & Vulnerability Management dashboard**, and select the first item on the list. This opens the **Security recommendation** page.
|
||||
|
||||
>>
|
||||
|
||||
>[!NOTE]
|
||||
> There are two types of recommendations:
|
||||
> - <i>Security update</i> which refers to recommendations that require a package installation
|
||||
> - <i>Configuration</i> change which refers to recommendations that require a registry or GPO modification
|
||||
> Always prioritize recommendations that are associated with ongoing threats. These recommendations are marked with the threat insight  icon.
|
||||
|
||||
2. In the **Security recommendations** page, you will see the description of what needs to be done and why. It shows the vulnerability details, such as the associated exploits affecting what machines and its business impact. Click **Open software page** option from the flyout menu. 
|
||||
|
||||
3. Click **Installed machines** and select the affected machine from the list to open the flyout page with the relevant machine details, exposure and risk levels, alert and incident activities. 
|
||||
|
||||
4. Click **Open machine page** to connect to the machine and apply the selected recommendation. 
|
||||
|
||||
5. Allow a few hours for the changes to propagate in the system.
|
||||
|
||||
6. Review the machine **Security recommendation** tab again. The recommendation you've chosen to remediate won't be listed there anymore, and the exposure score should decrease.
|
||||
|
||||
## Improve your security configuration
|
||||
>[!NOTE]
|
||||
> Secure score is now part of Threat & Vulnerability Management as [configuration score](configuration-score.md). We’ll keep the secure score page available for a few weeks. View the [secure score](https://securitycenter.windows.com/securescore) page.
|
||||
|
||||
Remediating issues in the security recommendations list will improve your configuration. As you do so, your configuration score improves, which means building your organization's resilience against cybersecurity threats and vulnerabilities stronger.
|
||||
|
||||
1. From the Configuration score widget, select **Security controls**. This opens the **Security recommendations** page showing the list of issues related to security controls.
|
||||
|
||||
>>
|
||||
|
||||
2. Select the first item on the list. This opens the flyout menu with the description of the security controls issue, a short description of the potential risk, insights, configuration ID, exposed machines, and business impact. Click **Remediation options**.
|
||||
|
||||
|
||||
3. Read the description to understand the context of the issue and what to do next. Select a due date, add notes, and select **Export all remediation activity data to CSV** so you can attach it to the email that you can send to your IT Administrator for follow-up.
|
||||
|
||||
>>.
|
||||
|
||||
>You will see a confirmation message that the remediation task has been created.
|
||||
>
|
||||
|
||||
4. Save your CSV file.
|
||||
|
||||
|
||||
5. Send a follow up email to your IT Administrator and allow the time that you have alloted for the remediation to propagate in the system.
|
||||
|
||||
6. Review the machine **Configuration score** widget again. The number of the security controls issues will decrease. When you click **Security controls** to go back to the **Security recommendations** page, the item that you have addressed will not be be listed there anymore, and your configuration score should increase.
|
||||
|
||||
|
||||
## Related topics
|
||||
- [Risk-based Threat & Vulnerability Management](next-gen-threat-and-vuln-mgt.md)
|
||||
- [Threat & Vulnerability Management dashboard overview](tvm-dashboard-insights.md)
|
||||
- [Configuration score](configuration-score.md)
|
||||
|
||||
@ -0,0 +1,76 @@
|
||||
---
|
||||
title: What's in the dashboard and what it means for my organization's security posture
|
||||
description:
|
||||
keywords:
|
||||
search.product: Windows 10
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.author: dolmont
|
||||
author: DulceMontemayor
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: conceptual
|
||||
---
|
||||
# Threat & Vulnerability Management dashboard overview
|
||||
|
||||
**Applies to:**
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
[!include[Prerelease<73>information](prerelease.md)]
|
||||
|
||||
>Want to experience Microsoft Defender ATP? [Sign up for a free trial.](https://www.microsoft.com/en-us/WindowsForBusiness/windows-atp?ocid=docs-wdatp-portaloverview-abovefoldlink)
|
||||
|
||||
Threat & Vulnerability Management is a component of Microsoft Defender ATP, and provides both security administrators and security operations teams with unique value, including:
|
||||
- Real-time endpoint detection and response (EDR) insights correlated with endpoint vulnerabilities
|
||||
- Invaluable machine vulnerability context during incident investigations
|
||||
- Built-in remediation processes through Microsoft Intune and Microsoft System Center Configuration Manager (SCCM)
|
||||
|
||||
>[!NOTE]
|
||||
> Microsoft Intune and Microsoft System Center Configuration Manager (SCCM) integration will be available in the coming weeks.
|
||||
|
||||
You can use the Threat & Vulnerability Management capability in [Microsoft Defender Security Center](https://securitycenter.windows.com/) to:
|
||||
- View exposure and configuration scores side-by-side with top security recommendations, software vulnerability, remediation activities, and exposed machines
|
||||
- Correlate EDR insights with endpoint vulnerabilities and process them
|
||||
- Select remediation options, triage and track the remediation tasks
|
||||
|
||||
## Threat & Vulnerability Management in Microsoft Defender Security Center
|
||||
When you open the portal, you’ll see the main areas of the capability:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
- (1) Menu in the navigation pane
|
||||
- (2) Threat & Vulnerability Management icon
|
||||
- (3) Threat & Vulnerability Management dashboard
|
||||
|
||||
You can navigate through the portal using the menu options available in all sections. Refer to the following table for a description of each section.
|
||||
|
||||
Area | Description
|
||||
:---|:---
|
||||
(1) Menu | Select menu to expand the navigation pane and see the names of the Threat & Vulnerability Management capabilities.
|
||||
(2) Threat & Vulnerability Management navigation pane | Use the navigation pane to move across the **Threat and Vulnerability Management Dashboard**, **Security recommendations**, **Remediation**, and **Software inventory**.
|
||||
**Dashboards** | Get a high-level view of the organization exposure score, MDATP configuration score, top remediation activities, top security recommendations, top vulnerable software, and top exposed machines data.
|
||||
**Security recommendations** | See the list of security recommendations, their related components, insights, number or exposed devices, impact, and request for remediation. You can click each item on the list and it will open a flyout pane where you will see vulnerability details, and have the option to open the software page, and see the remediation options.
|
||||
**Remediation** | See the remediation activity, related component, remediation type, status, due date, option to export the remediation and process data to CSV.
|
||||
**Software inventory** | See the list of applications, versions, weaknesses, whether there’s an exploit found on the application, prevalence in the organization, how many were installed, how many exposed devices are there, and the numerical value of the impact. You can select each item in the list and opt to open the software page which shows the vulnerabilities and misconfigurations associated and its machine and version distribution details.
|
||||
(3) Threat & Vulnerability Management dashboard | Access the **Exposure score**, **Configuration score**, **Exposure distribution**, **Top security recommendations**, **Top vulnerable software**, **Top remediation activities**, **Top exposed machines**, and **Threat campaigns**.
|
||||
**Organization Exposure score** | See the current state of your organization’s device exposure to threats and vulnerabilities. Several factors affect your organization’s exposure score: weaknesses discovered in your devices, likelihood of your devices to be breached, value of the devices to your organization, and relevant alerts discovered with your devices. The goal is to lower down your organization’s exposure score to be more secure. To reduce the score, you need to remediate the related security configuration issues listed in the security recommendations.
|
||||
**MDATP Configuration score** | See the security posture of your organization’s operating system, applications, network, accounts and security controls. The goal is to increase your configuration score by remediating the related security configuration issues. You can click the bars and it will take you to the **Security recommendation** page for details.
|
||||
**Machine exposure distribution** | See how many machines are exposed based on their exposure level. You can click the sections in the doughnut chart and it will take you to the **Machines list** page where you'll see the affected machine names, exposure level side by side with risk level, among other details such as domain, OS platform, its health state, when it was last seen, and its tags.
|
||||
**Top security recommendations** | See the collated security recommendations which are sorted and prioritized based on your organization’s risk exposure and the urgency that it requires. Useful icons also quickly calls your attention on possible active alerts , associated public exploits , and recommendation insights . You can drill down on the security recommendation to see the potential risks, list of exposed machines, and read the insights. Thus, providing you with an informed decision to either proceed with a remediation request. Click **Show more** to see the rest of the security recommendations in the list.
|
||||
**Top vulnerable software** | Get real-time visibility into the organizational software inventory, with stack-ranked list of vulnerable software installed on your network’s devices and how they impact on your organizational exposure score. Click each item for details or **Show more** to see the rest of the vulnerable application list in the **Software inventory** page.
|
||||
**Top remediation activities** | Track the remediation activities generated from the security recommendations. You can click each item on the list to see the details in the **Remediation** page or click **Show more** to see the rest of the remediation activities.
|
||||
**Top exposed machines** | See the exposed machine names and their exposure level. You can click each machine name from the list and it will take you to the machine page where you can view the alerts, risks, incidents, security recommendations, installed software, discovered vulnerabilities associated with the exposed machines. You can also do other EDR-related tasks in it, such as: manage tags, initiate automated investigations, initiate a live response session, collect an investigation package, run antivirus scan, restrict app execution, and isolate machine. You can also click **Show more** to see the rest of the exposed machines list.
|
||||
|
||||
See [Microsoft Defender ATP icons](https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-atp/portal-overview-windows-defender-advanced-threat-protection#windows-defender-atp-icons) for more information on the icons used throughout the portal.
|
||||
|
||||
## Related topics
|
||||
- [Risk-based Threat & Vulnerability Management](next-gen-threat-and-vuln-mgt.md)
|
||||
- [Configuration score](configuration-score.md)
|
||||
- [Scenarios](threat-and-vuln-mgt-scenarios.md)
|
||||
@ -23,9 +23,15 @@ ms.topic: conceptual
|
||||
|
||||
Here are the new features in the latest release of Windows Defender ATP as well as security features in Windows 10 and Windows Server.
|
||||
|
||||
## April 2019
|
||||
### In preview
|
||||
The following capability is included in the April 2019 preview release.
|
||||
|
||||
- [Threat & Vulnerability Management](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/next-gen-threat-and-vuln-mgt) <BR> A new built-in capability that uses a risk-based approach to the discovery, prioritization, and remediation of endpoint vulnerabilities and misconfigurations.
|
||||
|
||||
## March 2019
|
||||
### In preview
|
||||
The following capability are included in the February 2019 preview release.
|
||||
The following capability are included in the March 2019 preview release.
|
||||
|
||||
- [Machine health and compliance report](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/machine-reports-windows-defender-advanced-threat-protection) <BR> The machine health and compliance report provides high-level information about the devices in your organization.
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Windows Defender Advanced Threat Protection
|
||||
description: Windows Defender Advanced Threat Protection is an enterprise security platform that helps secops to prevent, detect, investigate, and respond to possible cybersecurity threats related to advanced persistent threats.
|
||||
keywords: introduction to Windows Defender Advanced Threat Protection, introduction to Windows Defender ATP, cybersecurity, advanced persistent threat, enterprise security, machine behavioral sensor, cloud security, analytics, threat intelligence, attack surface reduction, next generation protection, automated investigation and remediation, microsoft threat experts, secure score, advanced hunting, microsoft threat protection
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.product: Windows 10
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -47,9 +47,8 @@ Windows Defender ATP uses the following combination of technology built into Win
|
||||
<center><h2>Windows Defender ATP</center></h2>
|
||||
<table>
|
||||
<tr>
|
||||
<td>
|
||||
<a href="#asr">
|
||||
<center><img src="images/ASR_icon.png"><br><b>Attack surface reduction</b></center></a></td>
|
||||
<td><a href="#tvm"><center><img src="images/TVM_icon.png"> <br><b>Threat & Vulnerability Management</b></center></a></td>
|
||||
<td><a href="#asr"><center><img src="images/ASR_icon.png"><br><b>Attack surface reduction</b></center></a></td>
|
||||
<td><center><a href="#ngp"><img src="images/ngp_icon.png"><br> <b>Next generation protection</b></a></center></td>
|
||||
<td><center><a href="#edr"><img src="images/edr_icon.png"><br> <b>Endpoint detection and response</b></a></center></td>
|
||||
<td><center><a href="#ai"><img src="images/AR_icon.png"><br> <b>Automated investigation and remediation</b></a></center></td>
|
||||
@ -57,23 +56,27 @@ Windows Defender ATP uses the following combination of technology built into Win
|
||||
<td><center><a href="#mte"><img src="images/MTE_icon.png"><br> <b>Microsoft Threat Experts</b></a></center></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td colspan="6">
|
||||
<td colspan="7">
|
||||
<a href="#apis"><center><b>Management and APIs</a></b></center></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td colspan="6"><a href="#mtp"><center><b>Microsoft Threat Protection</a></center></b></td>
|
||||
<td colspan="7"><a href="#mtp"><center><b>Microsoft Threat Protection</a></center></b></td>
|
||||
</tr>
|
||||
</table>
|
||||
<br>
|
||||
|
||||
|
||||
<a name="asr"></a>
|
||||
|
||||
|
||||
>[!TIP]
|
||||
>- Learn about the latest enhancements in Windows Defender ATP: [What's new in Windows Defender ATP](https://cloudblogs.microsoft.com/microsoftsecure/2018/11/15/whats-new-in-windows-defender-atp/).
|
||||
>- Windows Defender ATP demonstrated industry-leading optics and detection capabilities in the recent MITRE evaluation. Read: [Insights from the MITRE ATT&CK-based evaluation](https://cloudblogs.microsoft.com/microsoftsecure/2018/12/03/insights-from-the-mitre-attack-based-evaluation-of-windows-defender-atp/).
|
||||
|
||||
<a name="tvm"></a>
|
||||
|
||||
**[Threat & Vulnerability Management](next-gen-threat-and-vuln-mgt.md)**<br>
|
||||
This built-in capability uses a game-changing risk-based approach to the discovery, prioritization, and remediation of endpoint vulnerabilities and misconfigurations.
|
||||
|
||||
<a name="asr"></a>
|
||||
|
||||
**[Attack surface reduction](overview-attack-surface-reduction.md)**<br>
|
||||
The attack surface reduction set of capabilities provide the first line of defense in the stack. By ensuring configuration settings are properly set and exploit mitigation techniques are applied, these set of capabilities resist attacks and exploitations.
|
||||
|
||||
|
||||
@ -95,6 +95,7 @@
|
||||
#### [Create an Outbound Program or Service Rule](create-an-outbound-program-or-service-rule.md)
|
||||
#### [Create Inbound Rules to Support RPC](create-inbound-rules-to-support-rpc.md)
|
||||
#### [Create WMI Filters for the GPO](create-wmi-filters-for-the-gpo.md)
|
||||
#### [Create Windows Firewall rules in Intune](create-windows-firewall-rules-in-intune.md)
|
||||
#### [Enable Predefined Inbound Rules](enable-predefined-inbound-rules.md)
|
||||
#### [Enable Predefined Outbound Rules](enable-predefined-outbound-rules.md)
|
||||
#### [Exempt ICMP from Authentication](exempt-icmp-from-authentication.md)
|
||||
|
||||
@ -0,0 +1,140 @@
|
||||
---
|
||||
title: Create Windows Firewall rules in Intune (Windows 10)
|
||||
description: Explains how to create Windows Firewall rules in Intune
|
||||
ms.assetid: 47057d90-b053-48a3-b881-4f2458d3e431
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: tewchen
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: conceptual
|
||||
ms.date: 04/11/2019
|
||||
---
|
||||
|
||||
# Create Windows Firewall rules in Intune
|
||||
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
|
||||
>[!IMPORTANT]
|
||||
>This information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
|
||||
|
||||
To get started, open Device Configuration in Intune, then create a new profile.
|
||||
Choose Windows 10 as the platform, and Endpoint Protection as the profile type.
|
||||
Select Windows Defender Firewall.
|
||||
Add a firewall rule to this new Endpoint Protection profile using the Add button at the bottom of the blade.
|
||||
|
||||
|
||||
|
||||
>[!IMPORTANT]
|
||||
>A single Endpoint Protection profile may contain up to a maximum of 150 firewall rules. If a client device requires more than 150 rules, then multiple profiles must be assigned to it.
|
||||
|
||||
## Firewall rule components
|
||||
|
||||
Following table has description for each field.
|
||||
|
||||
|
||||
| Property | Type | Description |
|
||||
|----------|------|-------------|
|
||||
| DisplayName | String | The display name of the rule. Does not need to be unique. |
|
||||
| Description | String | The description of the rule. |
|
||||
| PackageFamilyName | String | The package family name of a Microsoft Store application that's affected by the firewall rule. |
|
||||
| FilePath | String | The full file path of an app that's affected by the firewall rule. |
|
||||
| FullyQualifiedBinaryName | String | The fully qualified binary name. |
|
||||
| ServiceName | String | The name used in cases when a service, not an application, is sending or receiving traffic. |
|
||||
| Protocol | Nullable Integer - default value is null which maps to All | 0-255 number representing the [IP protocol](https://www.wikipedia.org/wiki/List_of_IP_protocol_numbers) (TCP = 6, UDP = 17). If not specified, the default is All. |
|
||||
| LocalPortRanges | String array | List of local port ranges. For example, "100-120", "200", "300-320". If not specified, the default is All. |
|
||||
| RemotePortRanges | String array | List of remote port ranges. For example, "100-120", "200", "300-320". If not specified, the default is All. |
|
||||
| LocalAddressRanges | String array | List of local addresses covered by the rule. Valid tokens include:<br>- "\*" indicates any local address. If present, this must be the only token included.<br>- A subnet can be specified using either the subnet mask or network prefix notation. If neither a subnet mask not a network prefix is specified, the subnet mask defaults to 255.255.255.255.<br>- A valid IPv6 address.<br>- An IPv4 address range in the format of "start address - end address" with no spaces included.<br>- An IPv6 address range in the format of "start address - end address" with no spaces included.<br>Default is any address. |
|
||||
| RemoteAddressRanges | String array | List of tokens specifying the remote addresses covered by the rule.Tokens are case insensitive. Valid tokens include:<br>- "\*" indicates any remote address. If present, this must be the only token included.<br>- "Defaultgateway"<br>- "DHCP"<br>- "DNS"<br>- "WINS"<br>- "Intranet"<br>- "RmtIntranet"<br>- "Internet"<br>- "Ply2Renders"<br>- "LocalSubnet" indicates any local address on the local subnet. This token is not case-sensitive.<br>- A subnet can be specified using either the subnet mask or network prefix notation. If neither a subnet mask not a network prefix is specified, the subnet mask defaults to 255.255.255.255.<br>- A valid IPv6 address.<br>- An IPv4 address range in the format of "start address - end address" with no spaces included.<br>- An IPv6 address range in the format of "start address - end address" with no spaces included.<br>Default is any address. |
|
||||
| ProfileTypes | WindowsFirewallNetworkProfileTypes | Specifies the profiles to which the rule belongs. If not specified, the default is All. |
|
||||
| Action| StateManagementSetting | The action the rule enforces. If not specified, the default is Allowed. |
|
||||
| TrafficDirection | WindowsFirewallRuleTrafficDirectionType | The traffic direction that the rule is enabled for. If not specified, the default is Out. |
|
||||
| InterfaceTypes | WindowsFirewallRuleInterfaceTypes | The interface types of the rule. |
|
||||
| EdgeTraversal | StateManagementSetting | Indicates whether edge traversal is enabled or disabled for this rule.<br>The EdgeTraversal setting indicates that specific inbound traffic is allowed to tunnel through NATs and other edge devices using the Teredo tunneling technology. In order for this setting to work correctly, the application or service with the inbound firewall rule needs to support IPv6. The primary application of this setting allows listeners on the host to be globally addressable through a Teredo IPv6 address.<br>New rules have the EdgeTraversal property disabled by default. |
|
||||
| LocalUserAuthorizations | String | Specifies the list of authorized local users for the app container. This is a string in Security Descriptor Definition Language (SDDL) format. |
|
||||
|
||||
|
||||
## Application
|
||||
Control connections for an app or program.
|
||||
Apps and programs can be specified either file path, package family name, or Windows service short name.
|
||||
|
||||
The file path of an app is its location on the client device.
|
||||
For example, C:\Windows\System\Notepad.exe.
|
||||
[Learn more](https://aka.ms/intunefirewallfilepathrule)
|
||||
|
||||
Package family names can be retrieved by running the Get-AppxPackage command from PowerShell.
|
||||
[Learn more](https://aka.ms/intunefirewallPackageNameFromPowerShell)
|
||||
|
||||
Windows service short names are used in cases when a service, not an application, is sending or receiving traffic.
|
||||
Default ia All.
|
||||
|
||||
[Learn more](https://aka.ms/intunefirewallServiceNameRule)
|
||||
|
||||
## Protocol
|
||||
Select the protocol for this port rule. Transport layer protocols—TCP and UDP—allow you to specify ports or port ranges. For custom protocols, enter a number between 0 and 255 representing the IP protocol.
|
||||
|
||||
Default is Any.
|
||||
|
||||
[Learn more](https://aka.ms/intunefirewallprotocolrule)
|
||||
|
||||
## Local ports
|
||||
Comma separated list of ranges. For example, *100-120,200,300-320*. Default is All.
|
||||
|
||||
[Learn more](https://aka.ms/intunefirewalllocalportrule)
|
||||
|
||||
## Remote ports
|
||||
Comma separated list of ranges. For example, *100-120,200,300-320*. Default is All.
|
||||
|
||||
[Learn more](https://aka.ms/intunefirewallremoteportrule)
|
||||
|
||||
## Local addresses
|
||||
Comma separated list of local addresses covered by the rule. Valid tokens include:
|
||||
- \* indicates any local address. If present, this must be the only token included.
|
||||
- A subnet can be specified using either the subnet mask or network prefix notation. If neither a subnet mask nor a network prefix is specified, the subnet mask default is 255.255.255.255.
|
||||
- A valid IPv6 address.
|
||||
- An IPv4 address range in the format of "start address - end address" with no spaces included.
|
||||
- An IPv6 address range in the format of "start address - end address" with no spaces included. Default is Any address.
|
||||
|
||||
[Learn more](https://aka.ms/intunefirewalllocaladdressrule)
|
||||
|
||||
## Remote addresses
|
||||
List of comma separated tokens specifying the remote addresses covered by the rule. Tokens are case insensitive. Valid tokens include:
|
||||
- \* indicates any remote address. If present, this must be the only token included.
|
||||
- Defaultgateway
|
||||
- DHCP
|
||||
- DNS
|
||||
- WINS
|
||||
- Intranet (supported on Windows versions 1809+)
|
||||
- RmtIntranet (supported on Windows versions 1809+)
|
||||
- Internet (supported on Windows versions 1809+)
|
||||
- Ply2Renders (supported on Windows versions 1809+)
|
||||
- LocalSubnet indicates any local address on the local subnet.
|
||||
- A subnet can be specified using either the subnet mask or network prefix notation. If neither a subnet mask not a network prefix is specified, the subnet mask defaults to 255.255.255.255.
|
||||
- A valid IPv6 address.
|
||||
- An IPv4 address range in the format of "start address - end address" with no spaces included.
|
||||
- An IPv6 address range in the format of "start address - end address" with no spaces included.
|
||||
|
||||
Default is Any address.
|
||||
|
||||
[Learn more](https://aka.ms/intunefirewallremotaddressrule)
|
||||
|
||||
## Edge traversal (coming soon)
|
||||
Indicates whether edge traversal is enabled or disabled for this rule. The EdgeTraversal setting indicates that specific inbound traffic is allowed to tunnel through NATs and other edge devices using the Teredo tunneling technology. In order for this setting to work correctly, the application or service with the inbound firewall rule needs to support IPv6. The primary application of this setting allows listeners on the host to be globally addressable through a Teredo IPv6 address. New rules have the EdgeTraversal property disabled by default.
|
||||
|
||||
[Learn more](https://aka.ms/intunefirewalledgetraversal)
|
||||
|
||||
## Authorized users
|
||||
Specifies the list of authorized local users for this rule. A list of authorized users cannot be specified if the rule being authored is targeting a Windows service. Default is all users.
|
||||
|
||||
[Learn more](https://aka.ms/intunefirewallauthorizedusers)
|
||||
|
||||
## Configuring firewall rules programmatically
|
||||
|
||||
Coming soon.
|
||||
|
||||
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 608 KiB |
@ -0,0 +1,80 @@
|
||||
---
|
||||
title: Windows security baselines
|
||||
description: This article, and the articles it links to, describe how to use Windows security baselines in your organization
|
||||
keywords: virtualization, security, malware
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.author: sagaudre
|
||||
author: justinha
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: conceptual
|
||||
ms.date: 06/25/2018
|
||||
---
|
||||
|
||||
# Windows security baselines
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows Server 2016
|
||||
- Office 2016
|
||||
|
||||
## Using security baselines in your organization
|
||||
|
||||
Microsoft is dedicated to providing its customers with secure operating systems, such as Windows 10 and Windows Server, and secure apps, such as Microsoft Edge. In addition to the security assurance of its products, Microsoft also enables you to have fine control over your environments by providing various configuration capabilities.
|
||||
|
||||
Even though Windows and Windows Server are designed to be secure out-of-the-box, many organizations still want more granular control over their security configurations. To navigate the large number of controls, organizations need guidance on configuring various security features. Microsoft provides this guidance in the form of security baselines.
|
||||
|
||||
We recommend that you implement an industry-standard configuration that is broadly known and well-tested, such as Microsoft security baselines, as opposed to creating a baseline yourself. This helps increase flexibility and reduce costs.
|
||||
|
||||
Here is a good blog about [Sticking with Well-Known and Proven Solutions](https://blogs.technet.microsoft.com/fdcc/2010/10/06/sticking-with-well-known-and-proven-solutions/).
|
||||
|
||||
## What are security baselines?
|
||||
|
||||
Every organization faces security threats. However, the types of security threats that are of most concern to one organization can be completely different from another organization. For example, an e-commerce company may focus on protecting its Internet-facing web apps, while a hospital may focus on protecting confidential patient information. The one thing that all organizations have in common is a need to keep their apps and devices secure. These devices must be compliant with the security standards (or security baselines) defined by the organization.
|
||||
|
||||
A security baseline is a group of Microsoft-recommended configuration settings that explains their security impact. These settings are based on feedback from Microsoft security engineering teams, product groups, partners, and customers.
|
||||
|
||||
## Why are security baselines needed?
|
||||
|
||||
Security baselines are an essential benefit to customers because they bring together expert knowledge from Microsoft, partners, and customers.
|
||||
|
||||
For example, there are over 3,000 Group Policy settings for Windows 10, which does not include over 1,800 Internet Explorer 11 settings. Of these 4,800 settings, only some are security-related. Although Microsoft provides extensive guidance on different security features, exploring each one can take a long time. You would have to determine the security impact of each setting on your own. Then, you would still need to determine the appropriate value for each setting.
|
||||
|
||||
In modern organizations, the security threat landscape is constantly evolving, and IT pros and policy-makers must keep up with security threats and make required changes to Windows security settings to help mitigate these threats. To enable faster deployments and make managing Windows easier, Microsoft provides customers with security baselines that are available in consumable formats, such as Group Policy Objects backups.
|
||||
|
||||
## How can you use security baselines?
|
||||
|
||||
You can use security baselines to:
|
||||
- Ensure that user and device configuration settings are compliant with the baseline.
|
||||
- Set configuration settings. For example, you can use Group Policy, System Center Configuration Manager, or Microsoft Intune to configure a device with the setting values specified in the baseline.
|
||||
|
||||
## Where can I get the security baselines?
|
||||
|
||||
You can download the security baselines from the [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=55319). This download page is for the Security Compliance Toolkit (SCT), which comprises tools that can assist admins in managing baselines in addition to the security baselines.
|
||||
|
||||
The security baselines are included in the [Security Compliance Toolkit (SCT)](security-compliance-toolkit-10.md), which can be downloaded from the Microsoft Download Center. The SCT also includes tools to help admins manage the security baselines.
|
||||
|
||||
[](security-compliance-toolkit-10.md)
|
||||
[](get-support-for-security-baselines.md)
|
||||
|
||||
## Community
|
||||
|
||||
[](https://blogs.technet.microsoft.com/secguide/)
|
||||
|
||||
## Related Videos
|
||||
|
||||
You may also be interested in this msdn channel 9 video:
|
||||
- [Defrag Tools](https://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-174-Security-Baseline-Policy-Analyzer-and-LGPO)
|
||||
|
||||
## See Also
|
||||
|
||||
- [System Center Configuration Manager (SCCM)](https://www.microsoft.com/cloud-platform/system-center-configuration-manager)
|
||||
- [Operations Management Suite](https://www.microsoft.com/cloud-platform/operations-management-suite)
|
||||
- [Configuration Management for Nano Server](https://blogs.technet.microsoft.com/grouppolicy/2016/05/09/configuration-management-on-servers/)
|
||||
- [Microsoft Security Guidance Blog](https://blogs.technet.microsoft.com/secguide/)
|
||||
- [Microsoft Security Compliance Toolkit Download](https://www.microsoft.com/download/details.aspx?id=55319)
|
||||
- [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=55319)
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 62 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 12 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 21 KiB |
@ -1,74 +0,0 @@
|
||||
---
|
||||
title: Blocking Remote Use of Local Accounts
|
||||
description: Covers the issues and tradeoffs of enabling account lockout and how tightly to enforce it.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: aaronmar
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: conceptual
|
||||
ms.date: 03/15/2019
|
||||
---
|
||||
|
||||
# Blocking Remote Use of Local Accounts
|
||||
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
- Windows Server
|
||||
|
||||
The use of local accounts for remote access in Active Directory environments is problematic for a number of reasons.
|
||||
By far, the biggest problem is that when an administrative local account has the same user name and password on multiple machines, an attacker with administrative rights on one machine can easily obtain the account’s password hash from the local Security Accounts Manager (SAM) database and use it to gain administrative rights over the other machines using “pass the hash” techniques.
|
||||
|
||||
Our latest security guidance responds to these problems by taking advantage of new Windows features to block remote logons by local accounts.
|
||||
Windows 8.1 and Windows Server 2012 R2 introduced two new security identifiers (SIDs), which are also defined on Windows 7, Windows 8, Windows Server 2008 R2 and Windows Server 2012 after installing [KB 2871997](http://support.microsoft.com/kb/2871997):
|
||||
|
||||
- S-1-5-113: NT AUTHORITY\Local account
|
||||
- S-1-5-114: NT AUTHORITY\Local account and member of Administrators group
|
||||
|
||||
The former SID is added to the user’s access token at the time of logon if the user account being authenticated is a local account.
|
||||
The latter SID is also added to the token if the local account is a member of the BUILTIN\Administrators group.
|
||||
These SIDs can grant or deny access to all local accounts or all administrative local accounts – for example, in User Rights Assignments to “Deny access to this computer from the network” and “Deny log on through Remote Desktop Services”, as we recommend in our latest security guidance.
|
||||
Prior to the definition of these SIDs, you would have had to explicitly name each local account to be restricted to achieve the same effect.
|
||||
|
||||
In the initial release of the Windows 8.1 and Windows Server 2012 R2 guidance, we denied network and remote desktop logon to “Local account” (S-1-5-113) for all Windows client and server configurations, which blocks all remote access for all local accounts.
|
||||
|
||||
We have since discovered that Failover Clustering relies on a non-administrative local account (CLIUSR) for cluster node management and that blocking its network logon access causes cluster services to fail.
|
||||
Because the CLIUSR account is not a member of the Administrators group, replacing S-1-5-113 with S-1-5-114 in the “Deny access to this computer from the network” setting allows cluster services to work correctly while still providing protection against “pass the hash” types of attacks by denying network logon to administrative local accounts.
|
||||
|
||||
While we could keep the guidance as it is and add a “special case” footnote for failover cluster scenarios, we will instead opt to simplify deployments and change the Windows Server 2012 R2 Member Server baseline as follows:
|
||||
|
||||
Policy Path
|
||||
|
||||
|
||||
Computer Configuration\Windows Settings\Local Policies\User Rights Assignment
|
||||
|
||||
|
||||
Policy Name
|
||||
|
||||
|
||||
Deny access to this computer from the network
|
||||
|
||||
|
||||
Original Value
|
||||
|
||||
|
||||
Guests, Local account (*)
|
||||
|
||||
|
||||
New Value
|
||||
|
||||
|
||||
Guests, Local account and member of Administrators group (*)
|
||||
|
||||
The guidance also recommends adding Domain Admins and Enterprise Admins to these restrictions except on domain controllers and dedicated admin workstations.
|
||||
DA and EA are domain-specific and can’t be specified in generic GPO baselines.
|
||||
|
||||
Note that this change applies only to the Member Server baseline and that the restriction on remote desktop logon is not being changed.
|
||||
Organizations can still choose to deny network access to “Local account” for non-clustered servers.
|
||||
|
||||
Note also that the restrictions on local accounts are intended for Active Directory domain-joined systems.
|
||||
Non-joined, workgroup Windows computers cannot authenticate domain accounts, so if you apply restrictions against remote use of local accounts on these systems, you will be able to log on only at the console.
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user