mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-14 06:17:22 +00:00
Style fixes
This commit is contained in:
parent
56876bef20
commit
c6eef76594
@ -142,8 +142,8 @@ The following fields are collected:
|
|||||||
| to_version | New security intelligence version. |
|
| to_version | New security intelligence version. |
|
||||||
| status | Status of the update indicating success or failure. |
|
| status | Status of the update indicating success or failure. |
|
||||||
| using_proxy | Whether the update was done over a proxy. |
|
| using_proxy | Whether the update was done over a proxy. |
|
||||||
| error | Error code in case of failed updates. |
|
| error | Error code if the update failed. |
|
||||||
| reason | Error message in case of failed updates. |
|
| reason | Error message if the update failed. |
|
||||||
|
|
||||||
#### Product and service performance data events
|
#### Product and service performance data events
|
||||||
|
|
||||||
@ -169,7 +169,7 @@ Diagnostic logs are collected only with the consent of the user as part of the f
|
|||||||
|
|
||||||
- All files under */var/log/microsoft/mdatp*
|
- All files under */var/log/microsoft/mdatp*
|
||||||
- Subset of files under */etc/opt/microsoft/mdatp* that are created and used by Microsoft Defender ATP for Linux
|
- Subset of files under */etc/opt/microsoft/mdatp* that are created and used by Microsoft Defender ATP for Linux
|
||||||
- Product installation and uninstalltion logs under */var/log/microsoft_mdatp_\*.log*
|
- Product installation and uninstallation logs under */var/log/microsoft_mdatp_\*.log*
|
||||||
|
|
||||||
### Optional diagnostic data
|
### Optional diagnostic data
|
||||||
|
|
||||||
@ -187,7 +187,7 @@ The following fields are collected:
|
|||||||
|
|
||||||
| Field | Description |
|
| Field | Description |
|
||||||
| -------------------------------------------------- | ----------- |
|
| -------------------------------------------------- | ----------- |
|
||||||
| connection_retry_timeout | Connection retry time out when communication with the cloud. |
|
| connection_retry_timeout | Connection retry time-out when communication with the cloud. |
|
||||||
| file_hash_cache_maximum | Size of the product cache. |
|
| file_hash_cache_maximum | Size of the product cache. |
|
||||||
| crash_upload_daily_limit | Limit of crash logs uploaded daily. |
|
| crash_upload_daily_limit | Limit of crash logs uploaded daily. |
|
||||||
| antivirus_engine.exclusions[].is_directory | Whether the exclusion from scanning is a directory or not. |
|
| antivirus_engine.exclusions[].is_directory | Whether the exclusion from scanning is a directory or not. |
|
||||||
|
@ -33,7 +33,7 @@ These applications can increase the risk of your network being infected with mal
|
|||||||
|
|
||||||
Microsoft Defender ATP for Linux can detect and report PUA files. When configured in blocking mode, PUA files are moved to the quarantine.
|
Microsoft Defender ATP for Linux can detect and report PUA files. When configured in blocking mode, PUA files are moved to the quarantine.
|
||||||
|
|
||||||
When a PUA is detected on an endpoint, Microsoft Defender ATP for Linux keeps a record of the infection in the threat history. This can be visualized from the Microsoft Defender Security Center portal or through the `mdatp` command-line tool. The threat name will contain the word "Application".
|
When a PUA is detected on an endpoint, Microsoft Defender ATP for Linux keeps a record of the infection in the threat history. The history can be visualized from the Microsoft Defender Security Center portal or through the `mdatp` command-line tool. The threat name will contain the word "Application".
|
||||||
|
|
||||||
## Configure PUA protection
|
## Configure PUA protection
|
||||||
|
|
||||||
|
@ -139,8 +139,8 @@ The following fields are collected:
|
|||||||
| to_version | New security intelligence version. |
|
| to_version | New security intelligence version. |
|
||||||
| status | Status of the update indicating success or failure. |
|
| status | Status of the update indicating success or failure. |
|
||||||
| using_proxy | Whether the update was done over a proxy. |
|
| using_proxy | Whether the update was done over a proxy. |
|
||||||
| error | Error code in case of failed updates. |
|
| error | Error code if the update failed. |
|
||||||
| reason | Error message in case of failed updates. |
|
| reason | Error message if the updated filed. |
|
||||||
|
|
||||||
#### Product and service performance data events
|
#### Product and service performance data events
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user