Build Your Security Data Lake in Hours

Building a log collection pipeline requires writing code to handle API  pagination, rate limiting, authentication, retries, and monitoring for each source. Then you need to maintain it as APIs change. Scanner Collect provides 30+ pre-built integrations that handle all of this automatically, getting you from zero to collecting logs in under 5  minutes instead of weeks of engineering time.

All logs are stored in your own S3 buckets in your AWS account. Scanner never takes custody of your data. You can deploy Scanner in the same region as your buckets to avoid cross-region costs and meet data residency requirements.

Yes! If you're already delivering logs to S3 (via CloudTrail,  third-party tools, or custom pipelines), Scanner can index them in place using S3 event notifications. Supports JSON, Parquet, CSV, and  plaintext formats.

Your logs stay in your S3 buckets as standard gzipped JSON files. You can continue using them with any tool. No vendor lock-in. The index files are also in your buckets - you can delete them if you no longer need Scanner's search capabilities.

Transformations and enrichment happen during ingestion, so they only  apply to new logs. Historical logs are not retroactively modified. If you need to re-process historical data with new transformations, you can trigger a re-indexing job.

Absolutely. Since logs are in your S3 buckets as standard JSON files, you can set up S3 event notifications to trigger Lambda functions, stream to Kinesis, or use any ETL tool to forward data wherever you need. Scanner doesn't lock you into any specific workflow.