Proofpoint URL Defense

Proofpoint URL Defense

Overview

Proofpoint URL Defense rewrites URLs in email messages to route clicks through Proofpoint's analysis infrastructure. When a user clicks a rewritten URL, Proofpoint performs real-time analysis of the destination before allowing or blocking access. This provides click-time protection - even if a URL was clean when the email was delivered, it will be analyzed again at the moment the user clicks.

URL Defense is a critical layer of protection because many attacks use time-delayed weaponization: a URL is clean when the email is sent but becomes malicious hours or days later.

Anti-triggers

• The click event feed across all users and threats — this skill answers "who clicked this URL". The full permitted/blocked click stream is proofpoint-tap.
• Removing the message that carried the link — use proofpoint-quarantine if it is still held, or proofpoint-forensics if it was delivered.
• Turning URL rewriting on or off — rewrite behaviour is a Proofpoint policy setting, and no tool here changes it; use the Proofpoint console. The same is true on a Checkpoint Harmony tenant: that plugin exposes no policy tool either, so its URL_REWRITE configuration is console-only as well. Do not route this question to a Harmony skill expecting a tool to exist.

Key Concepts

URL Rewriting

Proofpoint rewrites URLs in email bodies and HTML attachments. The rewritten URL format is:

https://urldefense.proofpoint.com/v2/url?u=<encoded_original_url>&d=<domain_key>&c=<context>&r=<recipient_hash>&m=<message_hash>&s=<signature>&e=

Version 3 format:

https://urldefense.com/v3/__<encoded_url>__;!!<encoded_chars>!<signature>$

URL Rewrite Components

Click-Time Analysis

When a user clicks a rewritten URL, Proofpoint performs:

1. URL reputation check - Is this URL on known blocklists?
2. Real-time sandbox - Load the page in a sandbox and check for malicious content
3. Redirect chain following - Follow all redirects to the final destination
4. Content analysis - Check for credential harvesting forms, drive-by downloads
5. Verdict delivery - Allow, warn, or block based on analysis

Click-Time Verdicts

URL Encoding in v2

In the v2 rewrite format, the original URL is encoded:

• - replaces /
• _ replaces =
• Standard URL encoding for other special characters

URL Encoding in v3

In the v3 format, the original URL uses a different encoding:

• __ delimiters surround the encoded URL
• Special characters are encoded in the trailing !! section
• The $ terminates the URL

Field Reference

URL Analysis Fields

Decoded URL Fields

MCP Tools

Two tools, and that is the whole domain. proofpoint_url_decode takes an array, so batch decoding is the ordinary call, not a separate tool — pass one URL in a one-element array. proofpoint_url_analyze is also the verdict tool: the classification and risk score it returns are the verdict, so there is no separate verdict call to poll.

Not available through this plugin

Click activity is not keyed by URL anywhere. URL Defense here decodes and analyses; it has no click surface. Click records live in TAP — proofpoint_tap_get_clicks_permitted and proofpoint_tap_get_clicks_blocked — and both are keyed by time window, not by URL. To answer "who clicked this link", pull the clicks for the relevant window and filter the results on the URL yourself, and remember TAP's 24-hour SIEM ceiling: outside that window you get an empty result that reads like "nobody clicked" and means "no data".

Common Workflows

Decode a Rewritten URL

1. User or analyst provides a Proofpoint-rewritten URL
2. Call proofpoint_url_decode with urls set to a one-element array containing the full rewritten URL
3. Return the original decoded URL
4. Optionally call proofpoint_url_analyze to check the URL's current threat status

Investigate a Suspicious URL

1. Call proofpoint_url_analyze with the URL
2. Review the classification, risk score, and associated campaigns
3. If malicious, pull proofpoint_tap_get_clicks_permitted for the relevant time window and filter the results for this URL to see who clicked
4. Cross-reference with the rest of the TAP click events for full context
5. If the URL is being used in an active campaign, escalate to threat intelligence

Bulk URL Decoding

1. Extract all Proofpoint-rewritten URLs from an email or document
2. Call proofpoint_url_decode with the whole array in urls — one call
3. Review the decoded URLs for any suspicious destinations
4. Check each decoded URL against threat intelligence

Click Activity Investigation

1. Identify a suspicious URL from TAP events or quarantine
2. Call proofpoint_tap_get_clicks_permitted and proofpoint_tap_get_clicks_blocked for the window, then filter both result sets on the URL — there is no per-URL click tool
3. Review which users clicked and when
4. Permitted clicks are the exposure; blocked clicks are volume signal
5. For permitted clicks, assess whether credentials may be compromised
6. Initiate password resets for users who clicked on credential harvesting URLs

Re-checking a URL After Delivery

1. Call proofpoint_url_analyze for a URL that was previously clean — URLs can become malicious after delivery, and the analysis reflects the current classification, not the one at delivery time
2. If it now classifies as malicious, check whether users received emails containing it
3. If they did, run the search-and-destroy sequence in the proofpoint-forensics skill

URL Decoding Reference

Manual v2 Decoding

To manually decode a v2 Proofpoint URL:

1. Extract the u= parameter value
2. Replace - with /
3. Replace _ with =
4. URL-decode the result

Input:  https://urldefense.proofpoint.com/v2/url?u=https-3A__example.com_path-3Fparam-3Dvalue&d=...
Step 1: https-3A__example.com_path-3Fparam-3Dvalue
Step 2: https-3A//example.com/path-3Fparam-3Dvalue
Step 3: https-3A//example.com/path-3Fparam=value
Step 4: https://example.com/path?param=value

Manual v3 Decoding

To manually decode a v3 Proofpoint URL:

1. Extract the content between __ delimiters
2. Decode special characters from the !! section
3. Replace encoded characters in the URL

Input:  https://urldefense.com/v3/__https://example.com/path__;!!ABC123!def$
Output: https://example.com/path

Note: Always use the proofpoint_url_decode tool rather than manual decoding to ensure accuracy.

Error Handling

Common API Errors

Decoding Failures

Best Practices

1. Check verdicts at click time - A URL clean at delivery may be malicious when clicked
2. Monitor click activity - Track which users are clicking rewritten URLs
3. Train users on rewritten URLs - Users should recognize Proofpoint-rewritten URLs as a security feature
4. Don't bypass URL Defense - Never instruct users to work around URL rewriting
5. Use browser isolation for risky clicks - Configure isolation for suspicious-but-not-confirmed URLs
6. Audit redirect chains - Multi-hop redirects are a common evasion technique
7. Batch decode for efficiency - proofpoint_url_decode takes an array; pass every URL in one call rather than looping
8. Retain decoded URLs - Log the original URLs for threat intelligence and IOC tracking
9. Combine with TAP data - Cross-reference URL analysis with TAP events for full visibility

Related Skills

• Proofpoint TAP - Click tracking and threat events
• Proofpoint Quarantine - Messages quarantined for malicious URLs
• Proofpoint Forensics - Deep URL investigation
• Proofpoint API Patterns - Authentication and rate limits