Table of Contents | ||||||
---|---|---|---|---|---|---|
|
Overview
Proofpoint's Email Isolation solution is a powerful tool for protecting against email-based threats, such as phishing and malware attacks. By isolating potentially dangerous email messages in a secure environment, Proofpoint prevents these messages from reaching end-users and reduces the risk of an attack succeeding.
With With Proofpoint Email Isolation, administrators can configure isolation policies based on specific criteria, such as sender reputation, attachment type, or keyword filtering. Isolated messages are stored securely and can be analyzed for threats, providing visibility into potential attacks and allowing organizations to take action to prevent them.
Proofpoint Browser Isolation secures the web browsing and email activities of your users. It uses cloud-based remote browser isolation to allow your people to access websites and their personal and corporate email freely, without exposing your organization to malware and data loss.
Devo collector features
Feature | Details |
---|---|
Allow parallel downloading ( |
|
Running environments |
|
Populated Devo events |
|
Flattening preprocessing |
|
Allowed source events obfuscation |
|
Data sources
Data source | Description | API endpoint | Collector service name | Devo table | Available from release |
---|---|---|---|---|---|
Browser and email isolation reports | Browser and email isolation report events |
|
|
|
|
URL isolation reports | URL isolation report events |
|
|
|
|
For more information on how the events are parsed, visit our page.
Vendor setup
Minimum configuration required for basic pulling
Although this collector supports advanced configuration, the fields required to retrieve data with basic configuration are defined below.
...
Setting | Details |
---|---|
| API key |
Steps
Action | Steps |
Obtain API key |
|
Assigning necessary permissions
Only the credentials above are required.
Run the collector
Once the data source is configured, you can either send us the required information if you want us to host and manage the collector for you (Cloud collector), or deploy and host the collector in your own machine using a Docker image (On-premise collector).
Rw ui tabs macro | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
This data collector can be run in any machine that has the Docker service available because it should be executed as a docker container. The following sections explain how to prepare all the required setup for having the data collector running. StructureThe following directory structure should be created for being used when running the collector:
Devo credentialsIn Devo, go to Administration → Credentials → X.509 Certificates, download the Certificate, Private key and Chain CA and save them in
Editing the config.yaml file
Replace the placeholders with your required values following the description table below:
Download the Docker imageThe collector should be deployed as a Docker container. Download the Docker image of the collector as a .tgz file by clicking the link in the following table:
Use the following command to add the Docker image to the system:
The Docker image can be deployed on the following services: DockerExecute the following command on the root directory
Docker ComposeThe following Docker Compose file can be used to execute the Docker container. It must be created in the
To run the container using docker-compose, execute the following command from the
We use a piece of software called Collector Server to host and manage all our available collectors. If you want us to host this collector for you, get in touch with us and we will guide you through the configuration. |
Collector services detail
This section is intended to explain how to proceed with specific actions for services.
Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
Internal process and deduplication methodProofpoint Isolation API stores events up to 30 days in the past. All isolation events are fetched on a polling basis. If there are more events available for a given time period than can be retrieved in a single page (limited to 10,000 records per page), the collector continues to fetch new events until none are available for the query window. Events are sorted by the Devo categorization and destinationAll events of this service are ingested into the table Setup outputA successful run has the following output messages for the setup module:
Puller output
After a successful collector’s execution (that is, no error logs found), you will see the following log message:
|
Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
Internal process and deduplication methodProofpoint Isolation API stores events up to 30 days in the past. All isolation events are fetched on a polling basis. If there are more events available for a given time period than can be retrieved in a single page (limited to 10,000 records per page), the collector continues to fetch new events until none are available for the query window. Events are sorted by the Devo categorization and destinationAll events of this service are ingested into the table tap.proofpoint.isolation.url_isolation. Setup outputA successful run has the following output messages for the setup module:
Puller output
After a successful collector’s execution (that is, no error logs were found), you should be able to see the following log message:
Restart the persistenceTo restart the service, the user must reconfigure the |
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This collector has different security layers that detect both an invalid configuration and abnormal operation. This table will help you detect and resolve the most common errors.
|
Collector operations
This section is intended to explain how to proceed with specific operations of this collector.
Expand | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||
InitializationThe initialization module is in charge of setup and running the input (pulling logic) and output (delivering logic) services and validating the given configuration. A successful run has the following output messages for the initializer module:
Events delivery and Devo ingestionThe event delivery module is in charge of receiving the events from the internal queues where all events are injected by the pullers and delivering them using the selected compatible delivery method. A successful run has the following output messages for the initializer module:
Sender servicesThe Integrations Factory Collector SDK has 3 different senders services depending on the event type to delivery (
Sender statisticsEach service displays its own performance statistics that allow checking how many events have been delivered to Devo by type:
|
Expand | ||
---|---|---|
| ||
To check the memory usage of this collector, look for the following log records in the collector which are displayed every 5 minutes by default, always after running the memory-free process.
|
Change log for v1.x.x
Release | Released on | Release type | Details | Recommendations | ||||||
---|---|---|---|---|---|---|---|---|---|---|
|
| Initial release | - |