# DISCOVER FAQs
Can I customise the types of sensitive data DISCOVER searches for?
Yes, you can customise the types of sensitive data DISCOVER searches for. DISCOVER provides flexibility to customise scan jobs according to your organisation’s specific data governance needs. You have the option to include predefined data (PCI and PII) or custom data types.
Custom data types can be defined as:
* Regular expressions: for pattern-based detection (e.g., employee ID formats, internal codes).
* Filename expressions: to detect files with specific naming conventions or keywords.
* Sensitive words: to locate documents containing custom phrases, particular terms, or confidential references.
When configuring a scan job, you can select or deselect predefined data types, such as PII (Personally Identifiable Information) and PCI (Payment Card Information), as well as custom data types.
What is different between a One-time Scan and an Ongoing Scan?
One-time Scan and Ongoing Scan differ in how DISCOVER executes and maintains scan jobs:
**One-time Scan**
* Runs only once when initiated manually.
* Ideal for quick assessments, targeted scans, or validating scan configuration changes.
* After completion, the scan won’t run again unless manually initiated.
* No automatic re-scan or scheduling is attached.
**Ongoing Scan**
* Configured to run at scheduled intervals.
* Automatically scans new or modified data sources according to the defined schedule.
* Used for routine monitoring, compliance tracking, and detection of newly introduced sensitive data.
How does agentless scanning work compared to scanning server-based scanning?
The difference is where the Scanning Server runs and what it scans.
| Agentless scanning | Scanning server-based scanning |
| --------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| The DISCOVER Scanning Server is installed on one host or VM. | The DISCOVER Scanning Server is installed on the same device being scanned. |
| The Scanning Server connects remotely to target devices and services over WinRM, SSH, SMB, or Microsoft 365 APIs. | The Scanning Server scans files locally on that same device. |
| Remote targets do **not** need any DISCOVER component installed. | The scanned device already has the Scanning Server installed because it is performing its own local scan. |
| Best for file servers, cloud services, shared infrastructure, or environments where you want one host to scan many targets. | Best for devices that need local scanning, such as roaming devices or systems you want to scan directly on the device itself. |
| Performance depends on network connectivity, protocol access, and target permissions. | Performance depends mainly on the resources of the device running the Scanning Server. |
What types of files does DISCOVER scan?
DISCOVER scans a wide range of file types across endpoints and storage systems, including:
| Category | File Types /Extensions |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| C Family | .c, .h, .cpp, .cc, .cxx, .hpp, .hh, .hxx, .cs, .m, .mm |
| Java & JVM | .java, .kt, .kts, .scala, .sc, .groovy, .gvy, .gy, .gsh, .clj, .cljs, .cljc, .edn |
| Web & Scripting | .js, .mjs, .cjs, .ts, .tsx, .html, .htm, .css, .scss, .sass, .less, .php, .php3, .php4, .php5, .php7, .phtml, .py, .pyw, .pyi, .rb, .erb, .rake, .gemspec, .lua |
| Systems & Functional | .rs, .go, .swift, .hs, .lhs, .erl, .hrl, .ex, .exs, .ml, .mli, .mll, .mly, .fs, .fsi, .fsx, .fsscript |
| Legacy / Academic | .f, .for, .f90, .f95, .f03, .f08, .cbl, .cob, .cpy, .pas, .pp, .dpr, .adb, .ads, .ada, .lisp, .lsp, .cl, .scm, .ss, .pro |
| Microsoft & ASP.Net | .vb, .bas, .frm, .cls, .asp, .aspx, .ascx, .config, .vbhtml, .cshtml |
| Shell & Admin | .sh, .bash, .zsh, .ksh, .bat, .cmd, .ps1, .psm1, .psd1, .pl, .pm, .t |
| Data Science / Analytics | .r, .rmd, .m, .jl, .sql, .psql, .sas, .sps, .do |
| Modern / Niche | .dart, .cr, .nim, .nims, .zig |
| Assembly / HDL | .asm, .s, .inc, .vhd, .vhdl, .v, .sv, .svh |
| Other Languages | .cfm, .cfc, .st, .apl, .dyalog, .ijs, .hack, .hh |
| Build / Infra / Config | Makefile, Dockerfile, CMakeLists.txt, BUILD, WORKSPACE, .mk, .cmake, .gradle, .gradle.kts, .bzl, .tf, .tfvars, .csproj, .vbproj, .fsproj, .json, .yaml, .yml, .md, .xml |
| Scripts & Source Code | .ps1, .bat, .cmd, .sh, .pl, .rb, .py, .php, .js, .ts, .java, .c, .cpp, .cs |
| Autodesk | .dwg, .dxf, .dwt, .ipt, .iam, .idw, .ipn, .rvt, .rfa, .nwc, .nwd, .f3d, .fbx, .3ds, .max, .mb, .ma |
| SolidWorks | .sldprt, .sldasm, .slddrw |
| PTC Creo | .prt, .asm, .drw, .neu, .xpr, .xas |
| CATIA | .catpart, .catproduct, .catdrawing, .cgr |
| Siemens NX / Solid Edge | .prt, .par, .asm, .dft |
| STEP / IGES (Neutral Exchange) | .step, .stp, .iges, .igs |
| 3D Modeling / 3D Designs | .stl, .obj, .ply, .3ds, .fbx, .gltf, .glb, .usd, .usdz, .vrml, .wrl, .lwo, .lws, .lxo, .ztl, .zpr, .hip, .hiplc, .hipnc, .prefab, .unity, .uasset, .umap, .pak, .amf, .3mf, .gcode, .pts, .ptx, .e57, .xyz, .las, .laz, .usdz, .gltf, .glb, .vrml, .x3d |
| Office Documents | .doc, .docx, .dot, .dotx, .rtf, .odt |
| Spreadsheets | .xls, .xlsx, .xlsm, .xlsb, .csv, .ods |
| Presentations | .ppt, .pptx, .pps, .odp |
| Text & Notes | .txt, .log, .md, .nfo |
| PDF & Publishing | .pdf, .xps, .pub |
| Email & Messaging | .msg, .eml, .pst, .ost, .mbox |
| Databases / Structured Data | .sql, .db, .sqlite, .mdb, .accdb, .dbf, .ora, .myd, .ibd |
| Config & Code Snippets | .ini, .cfg, .conf, .yaml, .yml, .json, .xml, .env |
| Images / Media | .jpg, .jpeg, .png, .gif, .bmp, .tif, .tiff, .ico, .heic |
| Backup & Export | .bak, .bkf, .gho, .vhd, .vhdx, .qcow2, .ova, .ovf |
| Logs & Monitoring | .log, .evt, .evtx |
| Financial / Accounting | .qbw, .qbb, .qfx, .ofx, .mny, .gnucash |
| Healthcare / PHI | .dcm, .hl7, .cda |
What happens if the Scanning Server device or the target device goes offline during a scan?
DISCOVER scans involve multiple connections:
* **Scanning Server ↔ Management Console connection:**
* If this connection goes offline, both the management console and the scanning server will continuously attempt to re-establish a connection.
* Data transfer from the scanning server to the management console is temporarily halted, but the scan continues.
* **Scanning Server ↔ Target device connection:**
* If a target device goes offline, the scan for that specific device pauses.
* Once the target comes back online, the scan resumes from where it left off.
* Other targets assigned to the same scanning server continue scanning uninterrupted.
* **Scanning Server self-scan:**
* This does not require network connectivity. It continues even if the scanning server or the management console is offline.
* However, data cannot be sent to the management console until the scanning server-server connection is restored.
How do I monitor the progress of ongoing scans?
You can monitor ongoing scans via the **DISCOVER Management Console**:
1. Navigate to **DISCOVER** > **Scans**.
2. In the scans list, check each scan's status.
| Status | Explaination |
| ----------- | ------------------------------------------------ |
| Not Started | The scan has been created but has not yet begun. |
| In Progress | The scan is currently running. |
| Completed | The scan has been completed. |
| Terminated | The scan was stopped manually. |
{% hint style="info" %}
Make sure to refresh the page to see the latest status, as this will update the display with any recent changes to the scanning server’s connectivity or activity.
{% endhint %}
How can I generate reports of discovered sensitive data?
Reports are automatically generated after each scan job. To download the generated reports:
1. Go to **DISCOVER** > **Results**.
2. Select a completed scan job from the list and click **Download.**
Reports will be downloaded as Excel (`.xlsx`) files.
Which environments and platforms does DISCOVER support?
DISCOVER supports scanning across a range of Windows environments and select Microsoft cloud services.
**Supported Environments**
* **Windows Operating Systems:**
* Windows 10 and 11
* Windows Server 2019, 2022, and 2025
* **File Servers:**
* SMB-based file servers
**Supported Cloud Services**
* Microsoft Exchange
* Microsoft SharePoint
DISCOVER connects to these systems using protocols such as SMB, WinRM, and SSH, enabling scanning across environments.
What are the firewall or port requirements for DISCOVER?
Yes, DISCOVER requires the following firewall and ports:
| Port | Service |
| ---- | ------------- |
| 22 | SSH |
| 445 | SMB |
| 443 | HTTPS |
| 5986 | WinRM (HTTPS) |
| 3306 | MySQL |
| 6379 | Redis |
Can I schedule scans or run them on-demand?
Yes, DISCOVER allows both on-demand and scheduled scans:
* **On-demand scans:**
* You can run a scan immediately whenever needed.
* If a scan is already running on the same scanning server or host, the new scan is queued and will start once the current scan completes.
* One scan task per scanning server can run at a time; additional scans are processed sequentially.
* **Scheduled scans:**
* You can configure recurring scans on a fixed schedule (daily, weekly, monthly, or custom intervals).
* Each scan job can have its own schedule, data scope, and sensitivity rules.
* Ideal for continuous monitoring and compliance checks without manual intervention.
What should I do if the DISCOVER Scanning Server cannot connect to the Management Console?
If the Management Console cannot connect to the DISCOVER Scanning Server:
1. **Check Network Status** – Ensure the Management Console service and the Scanning Server can establish inter-communication over the network.
If the network is functioning correctly but the scanning server still appears offline,
2. **Check Registry Configuration** – Open the Windows Registry Editor and navigate to:\
`Computer\HKEY_LOCAL_MACHINE\SOFTWARE\GuardWare\DISCOVER`.
3. Confirm that the `organizationName` matches your Organisation
4. Confirm that the `serverPort` entry contains the correct HTTPS port value.
5. Confirm that the `serverIP` and `serverName` point to the correct domain address.
If the given values are incorrect, you will need to reconfigure the DISCOVER Scanning Server and re-establish the connection. To do this:
1. Click the Windows key (⊞), type **Task Scheduler**, and press **Enter**.
2. Search for **GuardWare Discover Agent Task,** right-click it, and select **End.**
3. Launch **Task Manager** by pressing **Ctrl + Shift + Esc** keys together.
4. Search for **GuardWare Scan Utility,** right-click the process, and select **End task.**
5. Open File Explorer, navigate to `C:\ProgramData\Guardware\GWScanningAgent`, and delete all the contents of the folder.
7. Navigate to `C:\Program Files\Guardware\Discover Agent`
8. **Right-click** `GuardWareDiscoverAgent.exe` and select **Run as administrator**.
9. In your browser, refresh the Management Console page to see the reflected changes.
Who can I contact for technical support or further assistance?
For assistance, contact GuardWare support at .
---
# Agent Instructions: 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.guardware.com/discover/frequently-asked-aquestions/discover-faqs.md?ask=
```
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.