> For the complete documentation index, see [llms.txt](https://docs.reveald.com/technical-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reveald.com/technical-documentation/data-sources-early-access/windows-ad-legacy-version.md).

# Windows AD (Legacy Version)

## About This Document

The guide outlines the process for applying a Windows Group Policy Object (GPO) to your organization's domain, for the purpose of allowing Epiphany to make remote calls to the local security accounts manager (SAM). 

Allowing Epiphany to enumerate users and groups in the local SAM database and Active Directory within your organization's domain will provide you with a qualitative risk based on your permission boundaries and privilege use.

{% hint style="danger" %}
A WMI filter should be applied to the GPO to ensure the policy is only applied to the specific versions of Windows listed below. \
\
<https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-firewall/create-wmi-filters-for-the-gpo>
{% endhint %}

## Version Compatibility <a href="#version-compatibility" id="version-compatibility"></a>

The document applies to the following software versions:​

* **Epiphany**: Epiphany Collector version 1.00.003 and later.
* **Windows**:
  * Windows 10, version 1607 and later
  * Windows 10, version 1511 with KB 4103198 installed
  * Windows 10, version 1507 with KB 4012606 installed
  * Windows 8.1 with KB 4102219 installed
  * Windows 7 with KB 4012218 installed
* **Windows Server**:
  * Windows Server 2019
  * Windows Server 2016
  * Windows Server 2012 R2 with KB 4012219 installed
  * Windows Server 2012 with KB 4012220 installed
  * Windows Server 2008 R2 with KB 4012218 installed

## Prerequisites

* [ ] Epiphany Intelligence Platform domain-joined service account.

## What is Needed for Integration

To integrate your newly configured dataset into Epiphany, you  need to provide the information shown below into Epiphany. The information below will be entered in your Windows AD data source configuration.

* **Data Source Name:** The name for the Windows AD data source configuration.
* **Data Source Owner**: Your organizational stakeholder for this data source.
* **Data Source Notes**: Add additional information about the data source.
* **Username**: The Windows AD account username you created.
* **Password**: The password for the user account listed above.
* **Domain**: Fully qualified domain name (FQDN) of the Windows AD data source domain.
* **Domain Controller**: FQDN of the Windows AD data source domain controller.
* **Global Catalog** : FQDN of the Windows AD data source global catalog.&#x20;

[Legal Notice](/technical-documentation/legal-notice.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.reveald.com/technical-documentation/data-sources-early-access/windows-ad-legacy-version.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.