Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/endpointprotector/admin/API Logs/_category_.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
{
"label": "Logs REST API",
"position": 190,
"collapsed": true,
"collapsible": true,
"link": {
"type": "doc",
"id": "logrestapi"
}
}
4 changes: 2 additions & 2 deletions docs/endpointprotector/admin/cap_module/capai.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ sidebar_position: 60

**Introduction**

As artificial intelligence tools become increasingly integrated into everyday business processes, Netwrix Endpoint Protector (EPP), a leader in Data Loss Prevention (DLP) technology, has addressed the need for enhanced visibility and control. With the introduction of EPP Client version 2511, users now have access to a feature that extends Data Loss Prevention to Large Language Models (LLMs).
As artificial intelligence tools become increasingly integrated into everyday business processes, Netwrix Endpoint Protector (EPP), a leader in Data Loss Prevention (DLP) technology, has addressed the need for enhanced visibility and control. Starting with EPP Client release 2511, Netwrix introduced a set of features that extends Data Loss Prevention to Large Language Models (LLMs).

**Key Features**

Expand All @@ -23,7 +23,7 @@ By implementing these controls, organizations can protect sensitive information

## AI Interaction Visibility and Control in Netwrix Endpoint Protector: Data Loss Prevention for LLMs

Endpoint Protector extends Data Loss Prevention to the most widely used AI technologies — including ChatGPT, Microsoft Copilot, Google Gemini, DeepSeek, X Grok, Claude, Meta AI, and Perplexity — ensuring secure and compliant use across your organization. Coverage includes the embedded Microsoft Copilot add-in in Windows 11, New Outlook, New Teams, and Edge. Endpoint Protector also provides visibility and control over ChatGPT, Claude, and Copilot native clients.
Endpoint Protector extends Data Loss Prevention to the most widely used AI technologies — including ChatGPT, Microsoft Copilot, Google Gemini, DeepSeek, X Grok, Claude, Meta AI, Perplexity and Cursor — ensuring secure and compliant use across your organization. Coverage includes the embedded Microsoft Copilot add-in in Windows 11, New Outlook, New Teams, and Edge. Endpoint Protector also provides visibility and control over ChatGPT, Claude, and Copilot native clients.

## Configure Netwrix EPP to Monitor AI Prompt Transactions

Expand Down
4 changes: 3 additions & 1 deletion docs/endpointprotector/admin/support.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,10 +6,12 @@ sidebar_position: 180

# Support

For additional support resources, please visit our [website](https://www.netwrix.com/support.html)
For additional support resources, visit our [website](https://www.netwrix.com/support.html)
where you can read manuals, view FAQs, watch videos and tutorials, access direct e-mail support, and
much more.

We also recommend tracking the [Netwrix Community Portal](https://community.netwrix.com/c/products/endpoint-protector/22), a section dedicated to Endpoint Protector. It includes knowledge-sharing posts, Release Notes, bug lists, known limitations, and upcoming deprecations.

You can contact our technical support team by submitting a ticket through the
[Netwrix Customer Portal](https://www.netwrix.com/sign_in.html?rf=my_products.html). A team member
will respond to your inquiry as soon as possible.
Expand Down
2 changes: 1 addition & 1 deletion docs/endpointprotector/gettingstarted.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ accidental loss. Ensure compliance and protect sensitive information with Netwri
Before starting, ensure that your environment meets the following requirements:

- Operating Systems: Windows, macOS, Linux,
- CPU x86 64bit or ARM64 bit,
- CPU x86 64 bit or ARM64 bit,
- Disk Space: Sufficient for agent installation,
- Network: Access to Endpoint Protector Server,

Expand Down
2 changes: 1 addition & 1 deletion docs/endpointprotector/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ safeguard critical business data.

## Supportability Notice

**Netwrix Endpoint Protector 2605 is now the current supported version.** To ensure optimal security, performance, and access to the latest features, Netwrix recommends upgrading to version 2602 or later.
To ensure optimal security, performance, and access to the latest features, Netwrix recommends upgrading to the latest versions of both the Server and Client components.

### Support Status Overview

Expand Down
10 changes: 5 additions & 5 deletions docs/endpointprotector/requirements/client.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ market. The resources it consumes or the bandwidth it uses is insignificant. The
consumed, and bandwidth used by the Client depends on the functions, settings, policies used, and
the endpoint’s hardware configuration. In an idle state, the base requirements are:

- CPU: At least 1 GHz dual-core 64bit architecture CPU
- CPU: At least 1 GHz dual-core x86 64bit or ARM64bit architecture CPU.
- RAM: 30 MB
- Bandwidth: Less than 1 Kbs (Kilobit per second) when idle. This may increase depending on usage
when sending logs or uploading shadow files.
Expand All @@ -20,7 +20,7 @@ the endpoint’s hardware configuration. In an idle state, the base requirements
For Content Aware Protection and eDiscovery scanning, more CPU and RAM are required.
:::

Below is a closer look at the resource consumption when all modules are enabled , function are
The following table shows the resource consumption when all modules are enabled, functions are
active, and policies are configured for a stress test:

| Module | Device Control | Content Aware Protection | eDiscovery |
Expand Down Expand Up @@ -48,11 +48,11 @@ attempt to scan each entry as it is written, which can lead to:
performance.

To prevent these conflicts and allow the Endpoint Protector Client to function without interference,
add exclusions for specific files, folders, and processes on Windows, macOS, and Linux, as outlined
below.
add exclusions for specific files, folders, and processes on Windows, macOS, and Linux, as described
in the following sections.

:::warning Important
Before escalating any Endpoint Client performance issue, please ensure that the security tool exclusions listed below for EPP have been configured and deployed on the affected endpoint, and that the computer has been rebooted.
Before escalating any Endpoint Client performance issue, ensure that the security tool exclusions in the following sections for EPP are configured and deployed on the affected endpoint, and that you have rebooted the computer.
:::

### Recommended Exclusions for Windows
Expand Down
4 changes: 2 additions & 2 deletions docs/endpointprotector/requirements/server.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ sidebar_position: 20

# Server Sizing

These guidelines define the minimal server requirements according to Netwrix best practices. Assigning higher resources than the minimum is recommended for improved performance and stability. When configuring storage, use SSD drives whenever possible. The following sections detail server sizing best practices based on the number of modules and connected clients.
These guidelines define the minimum server requirements according to Netwrix best practices. Netwrix recommends assigning higher resources than the minimum for improved performance and stability. For migration plans or environments with regular data exports or API calls, Netwrix recommends increasing EPP Server sizing. When configuring storage, use SSD drives whenever possible. The following sections detail server sizing best practices based on the number of modules and connected clients.

| **Number of endpoints** | **Modules** | **CPU Cores** | **RAM** | **HDD** |
|-------------------------|--------------|---------------|---------|---------|
Expand Down Expand Up @@ -48,5 +48,5 @@ eD = eDiscovery <br />
EE = Enforced Encryption <br />

:::note
If your deployment exceeds 20,000 endpoints, please consult Netwrix Support to determine the appropriate server sizing for your environment.
If your deployment exceeds 20,000 endpoints, consult Netwrix Support to determine the appropriate server sizing for your environment.
:::
Loading