SendSafely Actions Library

Overview

While Enterprise customers can build their own SendSafely Actions, SendSafely also offers working proofs of concept for various Actions, which Enterprise customers can build upon or use as is. A list of these working examples follows.

To request the template for one of these Actions examples, please reach out to your SendSafely account rep. You should also reach out to your account rep if you're interested in purchasing Advisory Services from the SendSafely Solutions Engineering team, which can build you new working Actions POCs.

Please note that Actions which require access to the contents of SendSafely packages must be configured with a Portal Master Key (for all packages in your portal). All Actions examples in this list require such access.

AV Scanning Actions

• OPSWAT. This Action uses the OPSWAT Metadefender API to scan decrypted SendSafely package contents for malicious content. Packages containing malicious content can then be blocked or otherwise handled accordingly, and the appropriate stakeholders notified.
• Sophos. This Action uses the SophosLabs Intelix API to scan decrypted SendSafely package contents for malicious content. Packages containing malicious content can then be blocked or otherwise handled accordingly, and the appropriate stakeholders notified.
• CrowdStrike. This Action uses the CrowdStrike Falcon API to scan decrypted SendSafely package contents for malicious content. Packages containing malicious content can then be blocked or otherwise handled accordingly, and the appropriate stakeholders notified.

Compliance Storage Actions

• S3 Automatic Export. This Action programmatically exports decrypted SendSafely package contents to an S3 bucket for long-term storage. Many customers will use this Action to export package contents to a WORM bucket.

DLP Scanning Actions

• Google Cloud Data Loss Prevention (DLP) API. This Action uses the GCP DLP API to scan decrypted SendSafely package contents for sensitive material. Packages containing information in violation of your organization's DLP rules can then be blocked or otherwise handled accordingly, and the appropriate stakeholders notified.