Send Proofpoint TAP logs to LogPulse
Proofpoint Targeted Attack Protection: messages with a threat that were delivered or blocked, and clicks on threat URLs that were permitted or blocked.
Configure → Sources → Cloud. LogPulse reads the TAP SIEM API itself, without an agent. Events land in the email index with source proofpoint and fill the Email, Web data models.Overview
- TAP SIEM API to Integration poller
- Integration poller to index=email
LogPulse signs in to Proofpoint TAP with the credential you give it and fetches new events every five minutes by default. You can set the interval per integration, from one minute to 24 hours.
What you need
- A TAP service credential
- In LogPulse: a role that may manage API keys. Cloud integrations fall under that right.
1. Create a credential in Proofpoint TAP
| Field in LogPulse | Where you find it |
|---|---|
| Service principal | In the TAP dashboard: Settings, Connected Applications, Create New Credential. |
| Secret | Stored encrypted and never shown again. |
2. Add the integration in LogPulse
Go to Configure → Sources → Cloud and choose Proofpoint TAP. Fill in the fields, tick the data sources you want and save. LogPulse first tests the connection with your credential and tells you what is wrong when it fails.
What arrives
| Data source | Index | Source | Sourcetype | What it holds |
|---|---|---|---|---|
| SIEM events | email | proofpoint | proofpoint_tap_siem | Messages with a threat (delivered or blocked) and clicks on threat URLs (permitted or blocked): sender, recipient, subject, threat, scores and attachments. |
The index is the kind of data and the source is the product, so detection rules for that kind of data find Proofpoint TAP without changes.
Fields and data models
| Data model | What you get |
|---|---|
| Sender, recipient, subject, threat and attachments. | |
| Web | Clicks with user, URL, IP address and verdict. |
Field names follow the CIM field names. These are the fields LogPulse sets on Proofpoint TAP events; a field is left out when Proofpoint TAP did not send a value.
actioncampaign_idcategoryfile_hashfile_nameheader_fromhttp_user_agentidmessage_idquarantine_folderrecipientsendersignaturesrcsrc_ipsrc_usersubjectthreat_idthreat_statusthreat_typethreat_urlurluser
The original record of Proofpoint TAP is kept with each event under raw, so nothing the vendor sent is lost.
3. Check the data
The first events arrive within a few minutes. Check what came in:
earliest=-1h index IN (email) source IN (proofpoint)
| stats count by index, source, sourcetypeThe integration page in LogPulse shows when it last read events and the last error, if any.
Troubleshooting
The connection test names what is wrong. These are the answers you are most likely to see.
| What you see | What to do |
|---|---|
| Proofpoint refused the service principal and secret. | Create a new credential in the TAP dashboard under Settings, Connected Applications. |
| Proofpoint TAP keeps seven days; LogPulse skipped what is older | This shows after a pause of more than a week. The TAP SIEM API does not return older events, so that part cannot be read back. |
| The test passes but no events arrive. | Run the search above over a longer time. No results: check on the integration page that the data source is switched on and when it last read events. Proofpoint TAP may also simply have had nothing new. |
Frequently asked questions
- How do I send Proofpoint TAP logs to LogPulse?
- Add the Proofpoint TAP cloud integration under Configure, Sources, Cloud in LogPulse and fill in Service principal, Secret. LogPulse reads the TAP SIEM API itself, every five minutes by default; there is nothing to install.
- Which permissions does LogPulse need in Proofpoint TAP?
- A TAP service credential. Read access is enough for collecting logs.
- Which index does Proofpoint TAP data go to?
- The index is the kind of data: email. The source is the product: proofpoint. Each data source has its own sourcetype, listed on this page.
- Which data models does Proofpoint TAP fill?
- Email, Web. Detection rules and dashboards written for a data model work on Proofpoint TAP without changes.
- Which Proofpoint events get a high level?
- A threat message that was delivered and a click on a threat URL that was permitted: those got through. Blocked messages and blocked clicks arrive as a record of what Proofpoint stopped.