Seeker / Product capabilities
Sensitive data discovery that adapts to your environment.
Bring files, systems, databases and cloud services into view. Choose direct scans, on-demand Dissolving Agents or Managed Agents, and review the findings from your Seeker console.
What you can discover
From accessible files and databases to Microsoft cloud content and public code.
02 / DeploymentHow you can scan
Match the execution model to the source, access requirements and environment.
03 / ResultsWhat comes next
Review findings, refine scope, repeat supported scans and report what matters.
01 / Coverage
Follow the data.
Across your environment.
Supported sources, grouped by what they contain. Choose how to reach them in the scan models below.
Files & file shares
Local drives and accessible SMB shares. Scan file content with the permissions of the configured identity.
Local drives · SMBWindows & Mac systems
Reach endpoint files through supported remote workflows or persistent Managed Agents.
Windows · macOSRelational databases
Scan database tables and review findings with table, field and row context.
SQL Server · PostgreSQL · Oracle · MySQLMicrosoft cloud
Scan accessible OneDrive and SharePoint Online files through Microsoft Graph.
Identity and tenant permissions applyWebsites & public code
Scan accessible web content. Search public GitHub code for organization-related credential exposure.
Web content · Public GitHub searchWindows Search indexes
Run fast cursory checks, including indexed Outlook and OneNote content where available.
Limited by index scope and freshnessWindows folder-permission analysis is also available independently of content scanning. Explore permissions
02 / Scan methods
Choose how Seeker
reaches your systems.
Four ways to reach the data. Choose the access model and endpoint footprint that fit your environment.
Direct access
Centralized / direct scanning
Use the configured identity and its file-access permissions.
No remote endpoint agent required
On demand · temporary
Dissolving Agents
Mac’s documented dissolving workflow cleans staged components afterward; Windows uses temporary staging. Access and cleanup prerequisites still apply.
No permanent agent to maintain
Enrolled · persistent
Managed Agents
Use the managed model when ongoing enrollment and scheduled discovery fit your operations.
Persistent enrollment and scheduling
Source-specific access
Applications & cloud sources
Permissions and service limits apply. OneDrive, SharePoint Online and GitHub workflows remain interactive, not scheduled.
Access follows source permissions
Dissolving Agents on Mac: macOS 12+ on Intel or Apple silicon. Managed Agents on Mac: macOS 15+ on Apple silicon. Permissions, connectivity and Full Disk Access requirements apply.
Review scan requirements03 / Deployment choice
Choose the footprint that fits.
Temporary execution or persistent enrollment. Two valid ways to bring remote discovery into your workflow.
Dissolving Agents
Run on demand.
Keep the agent temporary.
Scan remote Windows and Mac systems without maintaining a permanent Seeker installation on each endpoint.
Start when you need it. Run remote discovery without Managed Agent enrollment.
Work close to the data. Temporary components scan on the remote system and return findings centrally.
- 01
Stage
Prepare the temporary scanning components on the endpoint.
- 02
Scan
Execute remotely with the required access and permissions.
- 03
Return
Collect the findings centrally; the Mac workflow then cleans its staged components.
No permanently installed
Seeker Agent required.
Temporary does not mean zero prerequisites or zero traces. Windows temporary staging and Mac cleanup have their own requirements.
Managed Agents
Stay connected for
recurring discovery.
Install and enroll supported Windows and Mac agents for a persistent, centrally managed scanning presence.
Organize and schedule. Group Managed Agents and coordinate recurring scans, including monthly and week-of-month schedules.
Review centrally. Inspect agent inventory, scan information and reports through the managed workflow.
Agents retain pending results locally until delivery. Connectivity and Agent Manager availability still matter.
04 / Detection
Recognize the familiar.
Define what’s unique.
Start with built-in patterns and validators. Add regular expressions for the information that matters to your organization.
Personal data
SSNs and supported international identifiers.
Financial data
Payment cards, bank identifiers and financial patterns.
Secrets
Credentials, API keys and SSH-key patterns.
Custom detection
Organization-specific regular expressions.
Give a match more context.
- Validate the value
- Apply supported validators to help reduce false positives.
- Require supporting context
- Use companion expressions against relevant nearby text, paths or database context.
- Control the scope
- Choose file extensions and applicable path filters. Use path alerts to annotate findings.
- Choose what results retain
- Configure match examples and surrounding text. Last-four masking is available for supported SSN, card and Hong Kong ID results.
Extraction / File formats
Broad file-format support.
Use Windows IFilters to extract text from many document types, alongside Seeker’s internal and specialized extraction methods. Compatible providers and configured file extensions determine what can be read.
ZIP, PST and OST processing is available when appropriately configured. Test your extraction setup before a broad scan with Tools → Test Scanning for File Types.
Check extraction prerequisites06 / Repeatable operations
Make discovery a working practice.
Carry what you learn into the next scan, with saved scope, historical context and supported automation.
- 01
Discover
Choose targets, scan methods and patterns for the data in scope.
- 02
Review
Reload historical results and logs. Investigate locations, matches and context.
- 03
Refine
Save configurations and target lists. Manage reviewed path and file-hash exclusions.
- 04
Repeat
Schedule supported scans. Re-resolve configured Active Directory computer targets.
- 05
Report
Export findings for follow-up. Run previously saved definitions with SeekCL.
Choose result storage.
Use Seeker’s encrypted local SQLite database or Microsoft SQL Server for centralized result storage. Logs and schedules have their own storage behavior.
Refine deliberately.
Exclusions suppress matching future findings and also remove matching stored historical findings. Removing an exclusion does not restore those past results.
Schedule supported workflows.
Recurring scans can run daily, weekly or monthly. OneDrive, SharePoint Online and GitHub workflows remain interactive.
See what Seeker finds
in your environment.
Explore sensitive-data discovery across your systems and sources.