mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-19 20:33:42 +00:00
from master
This commit is contained in:
@ -88,6 +88,7 @@ The following table shows the TPM owner authorization values in the registry.
|
||||
| 2 | Delegated |
|
||||
| 4 | Full |
|
||||
|
||||
A value of 5 means discard the **Full** TPM owner authorization for TPM 1.2 but keep it for TPM 2.0.
|
||||
|
||||
If you enable this policy setting, the Windows operating system will store the TPM owner authorization in the registry of the local computer according to the TPM authentication setting you choose.
|
||||
|
||||
|
@ -31,6 +31,7 @@ Some ways to store credentials are not protected by Windows Defender Credential
|
||||
- Digest and CredSSP credentials
|
||||
- When Windows Defender Credential Guard is enabled, neither Digest nor CredSSP have access to users' logon credentials. This implies no Single Sign-On use for these protocols.
|
||||
- Supplied credentials for NTLM authentication are not protected. If a user is prompted for and enters credentials for NTLM authentication, these credentials are vulnerable to be read from LSASS memory. Note that these same credentials are vulnerable to key loggers as well.-
|
||||
- Kerberos service tickets are not protected by Credential Guard, but the Kerberos Ticket Granting Ticket (TGT) is.
|
||||
- When Windows Defender Credential Guard is deployed on a VM, Windows Defender Credential Guard protects secrets from attacks inside the VM. However, it does not provide additional protection from privileged system attacks originating from the host.
|
||||
- Windows logon cached password verifiers (commonly called "cached credentials")
|
||||
do not qualify as credentials because they cannot be presented to another computer for authentication, and can only be used locally to verify credentials. They are stored in the registry on the local computer and provide validation for credentials when a domain-joined computer cannot connect to AD DS during user logon. These “cached logons”, or more specifically, cached domain account information, can be managed using the security policy setting **Interactive logon: Number of previous logons to cache** if a domain controller is not available.
|
||||
|
@ -193,18 +193,16 @@ In this example, you'd get the following info:
|
||||
Where the text, `O=MICROSOFT CORPORATION, L=REDMOND, S=WASHINGTON, C=US` is the publisher name to enter in the **Publisher Name** box.
|
||||
|
||||
### Add an AppLocker policy file
|
||||
For this example, we’re going to add an AppLocker XML file to the **App Rules** list. You’ll use this option if you want to add multiple apps at the same time. For more info about AppLocker, see the [AppLocker](https://technet.microsoft.com/itpro/windows/keep-secure/applocker-overview) content.
|
||||
Now we’re going to add an AppLocker XML file to the **App Rules** list. You’ll use this option if you want to add multiple apps at the same time. The first example shows how to create a Packaged App rule for Store apps. The second example shows how to create an Executable rule by using a path for unsigned apps. For more info, see [AppLocker](https://technet.microsoft.com/itpro/windows/keep-secure/applocker-overview).
|
||||
|
||||
**To create an app rule and xml file using the AppLocker tool**
|
||||
**To create a Packaged App rule rule and xml file**
|
||||
1. Open the Local Security Policy snap-in (SecPol.msc).
|
||||
|
||||
2. In the left pane, expand **Application Control Policies**, expand **AppLocker**, and then click **Packaged App Rules**.
|
||||
2. In the left pane, click **Application Control Policies** > **AppLocker** > **Packaged App Rules**.
|
||||
|
||||

|
||||
|
||||
3. Right-click in the right-hand pane, and then click **Create New Rule**.
|
||||
|
||||
The **Create Packaged app Rules** wizard appears.
|
||||
3. Right-click **Packaged App Rules** > **Create New Rule**.
|
||||
|
||||
4. On the **Before You Begin** page, click **Next**.
|
||||
|
||||
@ -262,6 +260,39 @@ For this example, we’re going to add an AppLocker XML file to the **App Rules*
|
||||
```
|
||||
12. After you’ve created your XML file, you need to import it by using Microsoft Intune.
|
||||
|
||||
**To create an Executable rule and xml file for unsigned apps**
|
||||
1. Open the Local Security Policy snap-in (SecPol.msc).
|
||||
|
||||
2. In the left pane, click **Application Control Policies** > **AppLocker** > **Executable Rules**.
|
||||
|
||||
3. Right-click **Executable Rules** > **Create New Rule**.
|
||||
|
||||

|
||||
|
||||
4. On the **Before You Begin** page, click **Next**.
|
||||
|
||||
5. On the **Permissions** page, make sure the **Action** is set to **Allow** and the **User or group** is set to **Everyone**, and then click **Next**.
|
||||
|
||||
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**.
|
||||
|
||||
9. On the **Name** page, type a name and description for the rule and then click **Create**.
|
||||
|
||||
10. In the left pane, right-click **AppLocker** > **Export policy**.
|
||||
|
||||
11. In the **Export policy** box, browse to where the policy should be stored, give the policy a name, and then click **Save**.
|
||||
|
||||
The policy is saved and you’ll see a message that says 1 rule was exported from the policy.
|
||||
|
||||
12. After you’ve created your XML file, you need to import it by using Microsoft Intune.
|
||||
|
||||
**To import your Applocker policy file app rule using Microsoft Intune**
|
||||
1. From the **App Rules** area, click **Add**.
|
||||
|
||||
|
Binary file not shown.
After Width: | Height: | Size: 53 KiB |
Binary file not shown.
After Width: | Height: | Size: 28 KiB |
Binary file not shown.
After Width: | Height: | Size: 20 KiB |
@ -8,7 +8,7 @@ ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.author: justinha
|
||||
ms.date: 05/30/2018
|
||||
ms.date: 06/18/2018
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
@ -39,7 +39,7 @@ As an admin, you can address the question of who gets access to your data by usi
|
||||
In the end, all of these security measures have one thing in common: employees will tolerate only so much inconvenience before looking for ways around the security restrictions. For example, if you don’t allow employees to share files through a protected system, employees will turn to an outside app that more than likely lacks security controls.
|
||||
|
||||
### Using data loss prevention systems
|
||||
To help address this security insufficiency, company’s developed data loss prevention (also known as DLP) systems. Data loss prevention systems require:
|
||||
To help address this security insufficiency, companies developed data loss prevention (also known as DLP) systems. Data loss prevention systems require:
|
||||
- **A set of rules about how the system can identify and categorize the data that needs to be protected.** For example, a rule set might contain a rule that identifies credit card numbers and another rule that identifies Social Security numbers.
|
||||
|
||||
- **A way to scan company data to see whether it matches any of your defined rules.** Currently, Microsoft Exchange Server and Exchange Online provide this service for email in transit, while Microsoft SharePoint and SharePoint Online provide this service for content stored in document libraries.
|
||||
|
@ -42,8 +42,7 @@ You can define the conditions for when entities are identified as malicious or s
|
||||
- File hash
|
||||
- Certificate
|
||||
- IP address
|
||||
- DNS
|
||||
|
||||
|
||||
3. Click **Add system exclusion**.
|
||||
|
||||
4. For each attribute specify the exclusion type, details, and their corresponding required values.
|
||||
|
@ -10,21 +10,25 @@ ms.pagetype: security
|
||||
ms.author: macapara
|
||||
author: mjcaparas
|
||||
ms.localizationpriority: high
|
||||
ms.date: 04/24/2018
|
||||
ms.date: 06/19/2018
|
||||
---
|
||||
|
||||
# Onboard machines to the Windows Defender ATP service
|
||||
|
||||
**Applies to:**
|
||||
|
||||
- Windows 7 SP1 Enterprise
|
||||
- Windows 7 SP1 Pro
|
||||
- Windows 8.1 Enterprise
|
||||
- Windows 8.1 Pro
|
||||
- Windows 10 Enterprise
|
||||
- Windows 10 Education
|
||||
- Windows 10 Pro
|
||||
- Windows 10 Pro Education
|
||||
- macOS
|
||||
- Linux
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2016
|
||||
- macOS
|
||||
- Linux
|
||||
- Windows Defender Advanced Threat Protection (Windows Defender ATP)
|
||||
|
||||
[!include[Prerelease information](prerelease.md)]
|
||||
@ -44,6 +48,38 @@ Windows Defender Advanced Threat Protection requires one of the following Micros
|
||||
|
||||
For more information, see [Windows 10 Licensing](https://www.microsoft.com/en-us/Licensing/product-licensing/windows10.aspx#tab=2).
|
||||
|
||||
## Hardware and software requirements
|
||||
### Supported Windows versions
|
||||
- Windows 7 SP1 Enterprise
|
||||
- Windows 7 SP1 Pro
|
||||
- Windows 8.1 Enterprise
|
||||
- Windows 8.1 Pro
|
||||
- Windows 10
|
||||
- Windows 10 Enterprise
|
||||
- Windows 10 Education
|
||||
- Windows 10 Pro
|
||||
- Windows 10 Pro Education
|
||||
- Windows server
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2016
|
||||
- Windows Server, version 1803
|
||||
|
||||
Machines on your network must be running one of these editions.
|
||||
|
||||
The hardware requirements for Windows Defender ATP on machines is the same as those for the supported editions.
|
||||
|
||||
> [!NOTE]
|
||||
> Machines that are running mobile versions of Windows are not supported.
|
||||
|
||||
|
||||
### Other supported operating systems
|
||||
>[!NOTE]
|
||||
>You'll need to know the exact Linux distros and macOS X versions that are compatible with Windows Defender ATP for the integration to work.
|
||||
|
||||
- macOS X
|
||||
- Linux
|
||||
|
||||
|
||||
## Windows Defender Antivirus configuration requirement
|
||||
The Windows Defender ATP agent depends on the ability of Windows Defender Antivirus to scan files and provide information about them.
|
||||
|
||||
@ -61,7 +97,8 @@ For more information, see [Windows Defender Antivirus compatibility](../windows-
|
||||
Topic | Description
|
||||
:---|:---
|
||||
[Onboard Windows 10 machines](configure-endpoints-windows-defender-advanced-threat-protection.md) | You'll need to onboard machines for it to report to the Windows Defender ATP service. Learn about the tools and methods you can use to configure machines in your enterprise.
|
||||
[Onboard servers](configure-server-endpoints-windows-defender-advanced-threat-protection.md) | Onboard Windows Server 2012 R2 and Windows Server 2016 to Windows Defender ATP
|
||||
[Onboard previous versions of Windows](onboard-downlevel-windows-defender-advanced-threat-protection.md)| Onboard Windows 7 and Windows 8.1 machines to Windows Defender ATP.
|
||||
[Onboard servers](configure-server-endpoints-windows-defender-advanced-threat-protection.md) | Onboard Windows Server 2012 R2 and Windows Server 2016 to Windows Defender ATP.
|
||||
[Onboard non-Windows machines](configure-endpoints-non-windows-windows-defender-advanced-threat-protection.md) | Windows Defender ATP provides a centralized security operations experience for Windows as well as non-Windows platforms. You'll be able to see alerts from various supported operating systems (OS) in the Windows Defender ATP portal and better protect your organization's network. This experience leverages on a third-party security products' sensor data.
|
||||
[Run a detection test on a newly onboarded machine](run-detection-test-windows-defender-advanced-threat-protection.md) | Run a script on a newly onboarded machine to verify that it is properly reporting to the Windows Defender ATP service.
|
||||
[Configure proxy and Internet settings](configure-proxy-internet-windows-defender-advanced-threat-protection.md)| Enable communication with the Windows Defender ATP cloud service by configuring the proxy and Internet connectivity settings.
|
||||
|
@ -114,7 +114,7 @@ This tile shows statistics related to automated investigations in the last 30 da
|
||||
|
||||

|
||||
|
||||
You can click on **Automated investigations**, **Remidated investigations**, and **Alerts investigated** to navigate to the **Invesgations** page, filtered by the appropriate category. This lets you see a detailed breakdown of investigations in context.
|
||||
You can click on **Automated investigations**, **Remidated investigations**, and **Alerts investigated** to navigate to the **Investigations** page, filtered by the appropriate category. This lets you see a detailed breakdown of investigations in context.
|
||||
|
||||
## Users at risk
|
||||
The tile shows you a list of user accounts with the most active alerts and the number of alerts seen on high, medium, or low alerts.
|
||||
|
Reference in New Issue
Block a user