A Windows member server is a computer that runs on Windows Server, belongs to a domain, and is not a domain controller. Windows member servers typically run different services and can act like a file server, print server, etc. For the sake of convenience, Windows member servers will be referred to as Windows servers in this guide.
ADAudit Plus is a real-time change auditing and user behavior analytics solution that helps keep your Windows servers secure and compliant. With ADAudit Plus, you can:
ADAudit Plus enables you to audit the following versions of Windows Server:
This guide takes you through the process of setting up ADAudit Plus and your Windows servers for real-time change auditing and user behavior analytics.
Log in to the ADAudit Plus web console. Go to the Server Audit tab → Configured Servers → Member Servers → Add Server. Enter the details needed to complete the configuration.
Note: ADAudit Plus can automatically configure the required audit policies for Windows server auditing. In the final step, you can either choose Yes to let ADAudit Plus automatically configure the required audit policies, or choose No to manually configure the required audit policies.
Audit policies must be configured to ensure that events are logged whenever any activity occurs.
Log in to the ADAudit Plus web console. Go to the Server Audit tab → Configured Servers → Member Servers → Audit Policy: Configure.
Note: ADAudit Plus can automatically configure the required audit policies for Windows server auditing. After clicking Audit Policy: Configure in the above step, you can either choose Yes to let ADAudit Plus automatically configure the required audit policies, or choose No to manually configure the required audit policies.
Note: Since configuring audit policies on individual computers is an elaborate process, a domain-level GPO is created and applied on all monitored computers.
Click ADAudit PlusMSPolicy, navigate to the right panel, and then select the Delegation tab → Advanced → Authenticated Users. Remove the Apply Group Policy permission.
Advanced audit policies help administrators exercise granular control over which activities get recorded in the logs, helping cut down on event noise. We recommend configuring advanced audit policies on Windows Server 2008 and above.
| Category | Subcategory | Audit Events |
|---|---|---|
| Account Logon | Audit Kerberos Authentication Service | Success and Failure |
| Account Management |
| Success Success and Failure |
| Detailed Tracking |
| Success |
| DS Access |
| Success |
| Logon/Logoff |
| Success and Failure Success |
| Object Access |
| Success and Failure |
| Policy Change |
| Success |
| System |
| Success |
Image showing: Account Logon category → Audit Kerberos Authentication Service subcategory → Both Success and Failure configured.
When using advanced audit policies, ensure that they are forced over legacy audit policies.
Due to the unavailability of advanced audit policies in Windows Server 2003 and earlier versions, legacy audit policies need to be configured for these types of servers.
| Category | Audit Events |
|---|---|
| Account Logon | Success and Failure |
| Audit Logon/Logoff | Success and Failure |
| Account Management | Success |
| Directory Service Access | Success |
| Process Tracking | Success |
| Object Access | Success |
| System Events | Success |
Image showing: Audit account logon events category → Both Success and Failure configured.
Event log size needs to be defined to prevent loss of audit data due to overwriting of events. To configure event log size and retention settings, follow the steps outlined below:
| Role | Operating System | Size |
|---|---|---|
| Windows file server | Windows Server 2003 | 512MB |
| Windows file server | Windows Server 2008 and above | 4,096MB |
To verify if the desired audit policies and security log settings are configured:
Log in to any computer that has the GPMC with Domain Admin credentials. Open the GPMC, right-click Group Policy Results, and open the Group Policy Results Wizard. Select the computer and user (current user), then verify if the desired settings as defined in step 2.2 are configured.
To verify if the desired events are getting logged:
Log in to any computer with Domain Admin credentials. Open Run, then type “eventvwr.msc”. Right-click on Event Viewer. Connect to the target computer, then verify if events corresponding to the configured audit policies are getting logged. For example, event ID 4768 should get logged when Success audit events is configured under the Audit Kerberos Authentication Service Subcategory, under the Account Logon Category (refer to step 2.2.1).