mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-18 00:07:23 +00:00
Merged PR 9158: 6/18 PM Publish
This commit is contained in:
commit
97972b86f8
@ -464,6 +464,12 @@ The following table lists the operating systems that are supported for MBAM Clie
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Windows 10 IoT</p></td>
|
||||
<td align="left"><p>Enterprise</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>32-bit or 64-bit</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Windows 10</p></td>
|
||||
<td align="left"><p>Enterprise</p></td>
|
||||
@ -518,6 +524,12 @@ The following table lists the operating systems that are supported for MBAM Grou
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Windows 10 IoT</p></td>
|
||||
<td align="left"><p>Enterprise</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>32-bit or 64-bit</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Windows 10</p></td>
|
||||
<td align="left"><p>Enterprise</p></td>
|
||||
|
@ -136,10 +136,12 @@ Digging this further with Fiddler – it does look like once we click on Reports
|
||||
|
||||
**Workaround:** Looking at the site.master code and noticed the X-UA mode was dictated as IE8. As IE8 is WAY past the end of life, and customer is using IE11. Update the setting to the below code. This allows the site to utilize IE11 rendering technologies
|
||||
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=Edge" />
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=Edge" />
|
||||
|
||||
Original setting is:
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=8" />
|
||||
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=8" />
|
||||
|
||||
|
||||
This is the reason why the issue was not seen with other browsers like Chrome, Firefox etc.
|
||||
|
||||
|
@ -27,6 +27,9 @@ Steps are provided in sections that follow the recommended setup process:
|
||||
|
||||
Update Compliance is offered as a solution in the Microsoft Operations Management Suite (OMS), a collection of cloud-based servicing for monitoring and automating your on-premise and cloud environments. For more information about OMS, see [Operations Management Suite overview](https://azure.microsoft.com/en-us/documentation/articles/operations-management-suite-overview/) or the Azure [Log Analytics overview](https://azure.microsoft.com/services/log-analytics/).
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Update Compliance is a free solution for Azure subscribers.
|
||||
|
||||
If you are already using OMS, skip to step **6** to add Update Compliance to your workspace.
|
||||
|
||||
>[!NOTE]
|
||||
|
@ -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.
|
||||
|
@ -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,7 +42,6 @@ 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**.
|
||||
|
||||
|
@ -10,7 +10,7 @@ ms.pagetype: security
|
||||
ms.author: macapara
|
||||
author: mjcaparas
|
||||
ms.localizationpriority: high
|
||||
ms.date: 04/24/2018
|
||||
ms.date: 06/18/2018
|
||||
---
|
||||
|
||||
# Onboard machines to the Windows Defender ATP service
|
||||
@ -61,6 +61,7 @@ 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 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.
|
||||
|
Loading…
x
Reference in New Issue
Block a user