Add Knowledge Base articles and documentation updates

docs/kb/1secure/_category_.json

@@ -0,0 +1,6 @@
+{
+  "label": "Knowledge Base Articles",
+  "position": 999,
+  "collapsed": true,
+  "collapsible": true
+}

docs/kb/1secure/configure_proxy_for_rdp_connections_(installupdate_certificate_to_prevent_rdp_certificate_warnings).md

@@ -0,0 +1,153 @@
+---
+description: >-
+  This article outlines the process for installing or updating a certificate to prevent Remote Desktop Protocol (RDP) certificate warnings during SbPAM workflows.
+keywords:
+  - RDP
+  - certificate installation
+  - SbPAM
+sidebar_label: Configure Proxy for RDP Connections
+tags: []
+title: "Configure Proxy for RDP Connections (Install/Update Certificate to Prevent RDP Certificate Warnings)"
+knowledge_article_id: kA04u0000000HRRCA2
+products:
+  - onesecure
+---
+
+# Configure Proxy for RDP Connections (Install/Update Certificate to Prevent RDP Certificate Warnings)
+
+## Overview
+
+This article outlines the process for installing or updating a certificate to prevent Remote Desktop Protocol (RDP) certificate warnings during SbPAM workflows.
+
+## Prerequisites
+
+- Windows Server must have the **Certification Authority** and **Certification Authority Web Enrollment** roles installed and configured. This ensures that the **Certification Authority** utility can be successfully launched and accessed via a web browser (`https://<servername>/certsrv`).
+
+  > **IMPORTANT:** The Certification Authority's post-deployment configuration must be completed after installing both prerequisite roles.
+
+  ![Certification Authority post-deployment configuration dialog with required options visible](./images/servlet_image_22726c8e5cb9.png)
+
+- The domain must have the **Enrollment Policy** set to enable automatic enrollment and renewal. The **Certificate Enrollment Policy** for user and computer certificates is configured in the **Group Policy** snap-in under **Default Domain Policy** (or another group policy applied to all systems that will access an NPS server on a group-by-group basis). To configure this:
+
+  1. On the Domain Controller, open the **Group Policy** snap-in.
+  2. Navigate to **Computer Configuration > Policies > Windows Settings > Security Settings > Public Key Policies** and enable the **Certificate Services - Certificate Enrollment Policy**.
+
+## Instructions
+
+### Generate Certificate
+
+> **NOTE:** If you already have a certificate to install, you can skip to the **Adding the Certificate to Each SbPAM Proxy Server** section below.
+
+1. Open **Certification Authority**, open your CA, right-click **Certificate Templates**, and click **Manage**.  
+   ![Certification Authority console with Certificate Templates context menu open](./images/servlet_image_ebb3b2e4c66a.png)
+
+2. In the **Certificate Templates Console**, right-click **Workstation Authentication**, and click **Duplicate Template**.  
+   ![Certificate Templates Console with Duplicate Template option highlighted](./images/servlet_image_e3eecaa55357.png)
+
+3. On the **General** tab, change the name to **Client-Server Authentication** and enable the **Publish certificate in Active Directory** checkbox.  
+   ![General tab of template properties with name and publish option highlighted](./images/servlet_image_35245db9daa9.png)
+
+4. On the **Subject Name** tab, enable the **Supply in the request** radio button.  
+   ![Subject Name tab with Supply in the request option selected](./images/servlet_image_2b1a501d40fd.png)
+
+5. On the **Extensions** tab, select **Application Policies** and click **Edit**. Click **Add**, then select **Server Authentication**. Click **OK** until you return to the **Properties of New Template** dialog.  
+   ![Extensions tab with Application Policies and Server Authentication highlighted](./images/servlet_image_9ccee298858e.png)
+
+6. On the **Security** tab, select **Domain Computers** and enable the checkbox to allow **Autoenroll**. Click **OK** and then close the Certificate Templates Console.  
+   ![Security tab with Domain Computers and Autoenroll option checked](./images/servlet_image_d2bd2889a956.png)
+
+7. Back in **Certification Authority**, right-click **Certificate Templates**, hover over **New**, and click **Certificate Template to Issue**.  
+   ![Certification Authority with Certificate Template to Issue option highlighted](./images/servlet_image_4e7a38bb30d6.png)
+
+8. Select **Client-Server Authentication** and click **OK**.  
+   ![Certificate Template selection dialog with Client-Server Authentication selected](./images/servlet_image_d8afec47d2b9.png)
+
+9. On the desktop, create a text file named **request.inf** with the following content (replace the **red** text with your server certificate name):
+
+   ```plaintext
+   [Version]
+   Signature="$Windows NT$"
+   [NewRequest]
+   Subject = "CN=**sbpam-3.sblab.local**"
+   KeySpec = 1
+   KeyLength = 2048
+   Exportable = TRUE
+   MachineKeySet = FALSE
+   SMIME = False
+   PrivateKeyArchive = FALSE
+   UserProtected = FALSE
+   UseExistingKeySet = FALSE
+   ProviderName = "Microsoft RSA SChannel Cryptographic Provider"
+   ProviderType = 12
+   RequestType = PKCS10
+   KeyUsage = 0xa0
+   HashAlgorithm = SHA256
+   [Extensions]
+   2.5.29.17 = "{text}"
+   _continue_ = "dns=**sbpam-3.sblab.local**&"
+   [EnhancedKeyUsageExtension]
+   OID=1.3.6.1.5.5.7.3.1
+   ```
+
+10. Open Command Prompt as Administrator, change directory to the Desktop (or the location of your **request.inf** file), and run:
+
+    ```plaintext
+    certreq -new request.inf rdp.csr
+    ```
+
+    ![Command Prompt showing certreq command execution](./images/servlet_image_117381e3f99f.png)
+
+11. To sign the certificate request, use your preferred signing mechanism. The following example uses Active Directory Certificate Services (`https://<servername>/certsrv`).  
+    ![Certificate Services web enrollment home page](./images/servlet_image_c706e5610294.png) ![Certificate Services advanced certificate request page](./images/servlet_image_0f3e849ec385.png)
+
+    Click **Request a certificate**, then click **advanced certificate request**.
+
+12. Open the saved certificate signing request (**rdp.csr**) from the previous step in Notepad. Copy the certificate request into the **Saved Request** field. Select **Client-Server Authentication** from the **Certificate Template** dropdown. Click **Submit**.  
+    ![Certificate request submission form with fields filled](./images/servlet_image_21d63c042bef.png)
+
+    Leave other settings at default values, and click **Submit**.
+
+13. Select **DER encoded** and click **Download certificate**.  
+    ![Certificate download page with DER encoded option selected](./images/servlet_image_ff7ee6960cb2.png)
+
+14. Open the downloaded certificate and select **Install Certificate**. Proceed with all default values and complete the wizard.  
+    ![Certificate installation wizard with default options](./images/servlet_image_9751657fe7cd.png)
+
+15. To export the certificate, view certificates for the current user by launching **certmgr.msc** using the Windows **Run** menu.  
+    ![Windows Run dialog with certmgr.msc entered](./images/servlet_image_f5c0eb62aa44.png)
+
+    Right-click the installed certificate (the certificate using the **Client-Server Authentication** template) and click **Export...**.  
+    ![Certificate export context menu](./images/servlet_image_4f237c8e6acb.png)
+
+16. In the **Certificate Export Wizard**, change the **Export Private Key** option to **Yes, export the private key**.  
+    ![Certificate Export Wizard with Export Private Key option selected](./images/servlet_image_9a7649f21943.png)
+
+17. For **Export File Format**, select **Personal Information Exchange - PKCS #12 (.PFX)**. Select the following checkboxes:
+
+    - Include all certificates in the certification path if possible
+    - Enable certificate privacy
+
+    ![Export File Format options with PKCS #12 and checkboxes selected](./images/servlet_image_491abdc2366b.png)
+
+18. For **Security**, enter a password of your choosing and select the AES256-SHA256 encryption option (3DES is no longer recommended by NIST).
+
+    > **IMPORTANT:** For **File to Export**, the file name **must** be **rdp.pfx**. If it is named anything else, importing the .pfx file on each proxy server will not work.  
+    ![Export dialog with rdp.pfx file name entered](./images/servlet_image_808a1a23eec9.png)
+
+19. This certificate can now be imported to each SbPAM Proxy Server.
+
+### Adding the Certificate to Each SbPAM Proxy Server
+
+1. Copy **rdp.pfx** (from the previous steps) to each SbPAM Proxy Server.
+
+2. On each SbPAM Proxy Server, run the following command via an elevated **Command Prompt**, and enter the certificate's password when prompted.
+
+   > **IMPORTANT:** The path to **sbpam-proxy.exe** may be different depending on the install path you selected when installing SbPAM and/or distributed proxy services.
+
+   ```plaintext
+   "C:\Program Files\Stealthbits\PAM\ProxyService\sbpam-proxy.exe" ca import -p [PATH]\rdp.pfx
+   ```
+
+   ![Command Prompt showing sbpam-proxy.exe ca import command](./images/servlet_image_07c7409683d2.png)
+
+3. The new certificate has now been imported to an SbPAM Proxy Server. Repeat this process for all SbPAM Proxy Servers if using more than one. (The default installation of SbPAM uses one proxy service on the SbPAM server itself; however, additional proxy services can be distributed.)

docs/kb/1secure/how_to_confirm_permissions_for_active_directory_5._domains_0.collection_ad_domaincontrollers.md

@@ -0,0 +1,100 @@
+---
+description: >-
+  This article provides step-by-step instructions to verify the permissions of the account used in Netwrix Enterprise Auditor for the AD_DomainControllers job.
+keywords:
+  - Active Directory
+  - Netwrix Enterprise Auditor
+  - permissions
+sidebar_label: Confirm Permissions for AD Domain Controllers
+tags: []
+title: "How to Confirm Permissions for Active Directory > 5. Domains > 0.Collection > AD_DomainControllers"
+knowledge_article_id: kA0Qk0000001hNtKAI
+products:
+  - onesecure
+---
+
+# How to Confirm Permissions for Active Directory > 5. Domains > 0.Collection > AD_DomainControllers
+
+## Question
+
+How can you verify if the account used in Netwrix Enterprise Auditor (NEA) for this job has the correct access?
+
+## Answer
+
+The AD_DomainControllers job for the NEA Active Directory module uses the following permissions for a least privilege model:
+
+- [Read access to CN=Servers, %SITEDN% and its children](#testcnsiteandchild)
+- [Read access to %PARTITIONDNS% and its children](#testpartandchild)
+- [Read access to %SCHEMADN%](#testschem)
+- [Read access to %SITESDN% and its children](#testsiteandchild)
+
+### General Steps to Start with `ldp.exe`
+
+1. Launch **`ldp.exe`**.
+   - Press **`Win + R`**, type **`ldp.exe`**, and hit **`Enter`**.
+2. Connect to a **Domain Controller**.
+   - Navigate to **Connection > Connect**.
+   - Enter the Domain Controller name used by the **AD_DomainControllers job** and port (default is `389` or `636` for LDAPS).
+   - Click **OK**.
+3. Bind Using the **User Account**.
+   - Go to **Connection > Bind**.
+   - Enter the **credentials** for the **user account** whose access you want to test.
+   - Click **OK**.
+
+### Testing Read Access to CN=Servers, %SITEDN% and Its Children
+
+1. Navigate to **`CN=Servers,%SITEDN%`**.
+   - Click **View > Tree**.
+   - Enter the Base DN:
+     ```
+     CN=Servers,CN=<SiteName>,CN=Sites,CN=Configuration,DC=<DomainComponent>,DC=<DomainComponent>
+     ```
+     - Replace **`<SiteName>`** with the site name (e.g., `Default-First-Site-Name`).
+       - If unsure, run **`nltest /dsgetsite`** from AdminPS on the DC to get the SiteName.
+     - Replace **`<DomainComponent>`** with your domain components (e.g., `example,DC=com`).
+   - Click **OK**.
+2. Verify **Access**.
+   - Expand **`CN=Servers`** and check if you can browse and view its children.
+   - If successful, then the user has **Read access**.
+
+### Testing Read Access to %PARTITIONDNS% and Its Children
+
+1. Navigate to the **Partition DN**.
+   - Click **View > Tree**.
+   - Enter the Base DN:
+     ```
+     DC=<DomainComponent>,DC=<DomainComponent>
+     ```
+     - Use your domain's **distinguished name** (e.g., `DC=example,DC=com`).
+   - Click **OK**.
+2. Verify **Access**.
+   - Expand the **domain node** and check if you can view objects and attributes within it.
+   - If you can browse the structure, then the user has **Read access**.
+
+### Testing Read Access to %SCHEMADN%
+
+1. Navigate to the **Schema DN**.
+   - Click **View > Tree**.
+   - Enter the Base DN:
+     ```
+     CN=Schema,CN=Configuration,DC=<DomainComponent>,DC=<DomainComponent>
+     ```
+     - Replace **`<DomainComponent>`** with your domain components.
+   - Click **OK**.
+2. Verify **Access**.
+   - Expand **`CN=Schema`** and check if you can view its objects and attributes.
+   - If successful, then the user has **Read access** to the schema.
+
+### Testing Read Access to %SITESDN% and Its Children
+
+1. Navigate to the **Sites DN**.
+   - Click **View > Tree**.
+   - Enter the Base DN:
+     ```
+     CN=Sites,CN=Configuration,DC=<DomainComponent>,DC=<DomainComponent>
+     ```
+     - Replace **`<DomainComponent>`** with your **domain components**.
+   - Click **OK**.
+2. Verify **Access**.
+   - Expand **`CN=Sites`** and check if you can browse through the sites and view their child objects.
+   - If successful, then the user has **Read access** to the sites.

docs/kb/1secure/index.md

@@ -0,0 +1,51 @@
+---
+title: "Knowledge Base"
+description: Browse our knowledge base articles by category"
+---
+
+# Knowledge Base
+
+Welcome to the knowledge base. Browse articles by category below.
+
+## Categories
+
+### [Installation & Setup](./installation/)
+Articles about installing, uninstalling, and setting up the product
+
+### [Configuration](./configuration/)
+Articles about configuring various product features
+
+### [Group Management](./group-management/)
+Managing groups, smart groups, and dynasties
+
+### [User Management](./user-management/)
+Managing users and user profiles
+
+### [Reports & Analytics](./reporting/)
+Generate reports and export data
+
+### [Troubleshooting](./troubleshooting/)
+Resolve common issues and errors
+
+### [Integration](./integration/)
+Integrate with external services and APIs
+
+### [Administration](./administration/)
+System administration and maintenance
+
+### [Best Practices](./best-practices/)
+Recommended practices and how-to guides
+
+## Quick Links
+
+- [Installation & Setup](./installation/)
+- [Troubleshooting Guide](./troubleshooting/)
+- [Best Practices](./best-practices/)
+- [Integration Guide](./integration/)
+
+## Need Help?
+
+If you can't find what you're looking for, please:
+1. Use the search function above
+2. Check the main documentation
+3. Contact [support](https://www.netwrix.com/support.html)

docs/kb/1secure/password-never-expires-report-shows-incorrect-data.md

@@ -0,0 +1,35 @@
+---
+description: >-
+  Netwrix OneSecutre may report the Password never expires setting as enabled
+  for accounts even though Active Directory shows it as disabled. This article
+  explains the cause (a GPO with maxPasswordAge=0) and how to resolve it.
+keywords:
+  - password never expires
+  - maxPasswordAge
+  - GPO
+  - Group Policy
+  - Active Directory
+  - Netwrix OneSecutre
+  - password policy
+  - report
+products:
+  - onesecure
+sidebar_label: Password Never Expires Report Shows Incorrect Data
+tags: []
+title: "Password Never Expires Report Shows Incorrect Data"
+knowledge_article_id: kA0Qk0000000YkrKAE
+---
+
+# Password Never Expires Report Shows Incorrect Data
+
+## Symptom
+
+In Netwrix 1Secure, the **Password never expires** setting is incorrectly reported as enabled for particular accounts. When you review **Active Directory Users and Computers** settings, the setting is disabled for affected accounts.
+
+## Cause
+
+A GPO with the `maxPasswordAge=0` parameter is applied to the affected accounts. The parameter causes Netwrix OneSecutre to report the **Password never expires** setting as enabled.
+
+## Resolution
+
+In the corresponding GPO, set the `maxPasswordAge` parameter to any non-zero value. This will allow Netwrix OneSecutre to correctly report the affected accounts.