S3 malware scanning

Scan S3 uploads before they disappear into the rest of your pipeline.

CypherScan Agent can receive Amazon S3 ObjectCreated events through the official AWS Lambda connector. Protected object scans become security observations that can flow into change history, attention decisions, verification, alerts, and Agent activity.

Set up S3 See Agent · $29/mo

Where it fits

Turn an upload event into a security workflow.

The connector runs as an AWS Lambda in your AWS account and reads protected objects when S3 emits an ObjectCreated event. CypherScan then records the resulting S3 asset and security observation so the event can participate in the same Agent attention pipeline as your other connected sources.

User uploads land in S3 before downstream processing or review.

You want object scan results to become durable security observations instead of isolated logs.

Your team wants an AWS-native event path using S3 ObjectCreated and Lambda.

You want qualifying changes to feed Agent attention, verification, alerts, and history.

Operational boundary

Keep AWS permissions narrow and the workflow explicit.

The official connector only needs permission to read the protected objects it is responsible for. Keep the CypherScan API key private, configure the intended bucket or prefix, and validate the workflow with a clean object before relying on it in production.

Start with one bucket and prove the path.

Follow the S3 integration guide for the event-driven setup, or try Scanner first if you only need an immediate file or URL check.

Open S3 setup Try Scanner free