Discovery Scanner and assessment scope

Assess before connecting a live workflow#

Discovery is a scoped assessment engagement. The offline scanner evaluates approved local files and keeps results local; the customer controls report sharing. Findings identify supported patterns, priorities and coverage gaps that can inform a pilot. They do not automatically remediate source data or govern live AI requests.

Distribution of native Windows x64 and macOS Intel packages is restricted and coordinated. Package availability, installation and operating-system support should be confirmed for the exact release rather than inferred from a source-code capability.

Qualify the source connection#

Local file assessment and optional SQL Server collection have different setup requirements. SQL Server needs approved credentials, least-privilege access, driver configuration, selected objects and customer-specific qualification. Read-only intent does not remove the need to agree query load and sensitive-data handling.

A separate PostgreSQL lsas-scan command performs bounded inventory and sampled email/SSN checks. PostgreSQL also stores optional connected reporting data. These facts do not make PostgreSQL a source type in every native file/SQL Server workspace.

Read the report as an assessment#

Keep the scanned population, supported formats, exclusions and sampling method with the findings. A sample containing no rule hits does not establish that the entire data estate is free of sensitive content. A finding describes a required control or issue; it does not prove source remediation occurred.

The report should support an accountable next step: confirm the finding, identify the relevant owner and select a potential control point. Avoid uploading or sharing customer content beyond the agreed assessment and support process.

Agree the commercial and operating scope#

The Discovery offering includes an agreed assessment scope, prioritized recommendations, an executive readout and the defined follow-up. Use the current Pricing page and engagement documents for environment limits, support allowances and conversion conditions. Additional sources or broader volume require separate scoping; this documentation does not change those terms.