> For the complete documentation index, see [llms.txt](https://docs.guardware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guardware.com/discover/about/introduction-to-discover.md).
# Introduction to DISCOVER
GuardWare DISCOVER is a cross-platform system designed to identify, classify, and manage sensitive data across enterprise environments. It operates across endpoints, file servers, email systems, and cloud services, helping organisations detect and reduce exposure of regulated and sensitive information including PCI, PII, PHI, as well as custom data types.
At its core, DISCOVER is built around a centralised model of control and distributed execution. This allows it to scale across diverse infrastructures while maintaining a single point of visibility and administration.
## System Architecture
The system is composed of three primary components that work together: the Management Console, the Scanning Server, and the Targets being scanned.
{% columns fullWidth="false" %}
{% column width="33.33333333333333%" %}
{% hint style="info" icon="1" %}
**Management Console**\
\
The central web application where scan jobs are scheduled, configurations are stored, and results are reviewed. It provides visibility into scan status, investigations, and remediation options.
{% endhint %}
{% endcolumn %}
{% column width="33.33333333333333%" %}
{% hint style="info" icon="2" %}
**Scanning Server**\
\
A dedicated host or virtual machine with the Scanning Agent installed. It receives scan and remediation tasks from the Management Console, executes them, and reports the results back.
{% endhint %}
{% endcolumn %}
{% column %}
{% hint style="info" icon="3" %}
**Targets**\
\
The systems and services scanned by GuardWare DISCOVER. Targets can include endpoints, SMB file shares, and cloud-based services such as Exchange Online, SharePoint Online, Gmail, and Google Drive.
{% endhint %}
{% endcolumn %}
{% endcolumns %}
## Scanning Agent Deployment Models
The Scanning Agent is installed on a machine to execute tasks received from the Management Console. It scans the targets and returns results and status to the Management Console.
DISCOVER supports two deployment models for the Scanning Agent, depending on the structure of the environment being scanned:
### Local Deployment
In a **Local deployment**, the Scanning Agent is installed directly on the target device, which scans its own local data. This requires the agent to be installed on each device individually.
### Scanning Server Deployment
The **Scanning Server deployment** introduces a centralised scanning model. In this setup, the Scanning Agent is installed on a dedicated server or virtual machine, which remotely scans multiple systems across the network. This is referred to as agentless scanning, as it removes the need for agent installation on each individual endpoint. This approach simplifies deployment in larger or more distributed environments.
{% hint style="info" %}
Although its primary role is remote scanning, a Scanning Server can also scan its own local files. In that case, the scan is treated as a local scan.
{% endhint %}
## Deployment and Setup Flow
Deploying GuardWare DISCOVER for scanning involves setting up the Management Console and then choosing how the Scanning Agent will be installed.
{% stepper %}
{% step %}
### Install the Management Console
The first step is installing the **Management Console** on a dedicated Windows system. This system becomes the central control point for all scanning activity, including configuration, scheduling, and reporting.
{% endstep %}
{% step %}
### Deploy the Scanning Agent
After the Management Console is operational, the next step is deploying the **Scanning Agent**. Depending on the chosen architecture, this may involve installing the Scanning Agent directly on endpoints for local scanning or deploying it on a dedicated host for remote (agentless) scanning.
In both cases, the Scanning Agent acts as the execution layer that carries out scan tasks assigned by the Management Console.\
[**Scanning Agent Deployment Guide→**](/setup-and-deploy/install-discover-agent/install-discover-agent.md)
{% endstep %}
{% step %}
### Configure and Run Scans
This includes adding scan targets, configuring Microsoft 365 credentials where necessary, and assigning data ownership where applicable. These configurations define what will be scanned and under what context.
Scan jobs can then be created and executed from the Management Console. Results are returned and displayed within the interface, allowing you to review findings, investigate files for sensitive data, and initiate remediation actions.\
[**DISCOVER Quick Start Guide →**](/discover/getting-started/discover-quick-start-guide.md)
{% endstep %}
{% endstepper %}
## Console Access and Operation
Familiarising administrators with the Management Console is essential, as all administrative and operational tasks are performed there. Functions are organised neatly, and related tools are grouped in the navigation menu for easy access.
Access to the console requires valid administrator credentials. After authentication, users must complete a second layer of verification using a time-based authenticator application. This ensures that access to sensitive scan data and system controls is properly secured.
Once logged in, the console provides a centralised view of all scan activity, including status, results, and historical reporting. From here, administrators can manage the full lifecycle of data discovery operations.
---
# 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, and the optional `goal` query parameter:
```
GET https://docs.guardware.com/discover/about/introduction-to-discover.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.