Skip to main content

DLP Onboarding Guide

Audience: IT Administrators and Unit IT Staff.

Purpose: Implement Proofpoint Endpoint DLP for your unit.

Project Overview​

Proofpoint Endpoint DLP is the data loss prevention solution for Texas A&M University.

Goals​

Create a robust DLP strategy leveraging:

  • Central security operations for monitoring
  • Local IT staff for environmental knowledge

Scope​

Implementation of Proofpoint Endpoint DLP across all Texas A&M University units.

Cost​

Centrally funded — No cost to individual units.

About Proofpoint Endpoint DLP​

The DLP agent:

  • Discovers, monitors, and protects critical information
  • Scans data as it leaves the TAMU environment (data in motion)
  • Runs in background with minimal user impact

Implementation Resources​

Console Access​

Request Access​

  1. Email secondary NetIDs (typically -admin accounts) to: cloudsecurity-notify@tamu.edu
  2. This opens a ServiceNow ticket for processing

Login Steps​

  1. Visit tamu.explore.proofpoint.com
  2. Click Office 365 button
  3. Log in with secondary NetID

Console Navigation​

ButtonPurpose
AdministrationView endpoints with DLP agent
AnalyticsView alerts for your unit

Agent Installers​

GitHub Repository: ProofpointDLP-Deployment

Contains:

  • Agent installers
  • Documentation
  • Deployment scripts

GitHub Access​

If you haven't set up GitHub access:

  1. Visit github.cloud.tamu.edu/home
  2. Follow setup instructions
  3. Contact GiGi Carbo (a-carbo@tamu.edu) for repository access issues

Frequently Asked Questions​

What's driving this implementation?

Managing DLP in isolation isn't effective for securing information at Texas A&M. Centralized visibility and collaboration across campus is essential for success.

What does my unit gain?

Access to the console for managing DLP across your unit's endpoints without licensing costs.

What console access will we have?

Each unit can designate admins with access to monitor alerts and activities for their clients.

Can we customize policies?

Basic policies are centrally managed. Units can request custom policies. Contact GiGi Carbo (a-carbo@tamu.edu) to discuss options.

Who gets notified of findings?

Technology Services reviews all alerts. If action is required, a ServiceNow ticket is submitted. Alternatively, your team can address findings directly in the console.

Should we install on all workstations?

Recommended for endpoints where faculty/staff handle critical or confidential data. Not needed for kiosks or student lab machines.

Is there a Linux agent?

Not currently. This has been requested for future releases.

Do servers need the agent?

No. The agent is intended for faculty and staff endpoints only.

Is training provided?

Yes — contact us to schedule an admin walk-through of the console.

Communications​

ChannelContact
Primary ContactGiGi Carbo (a-carbo@tamu.edu)
ServiceNowcloudsecurity-notify@tamu.edu
Change NotificationsEmail and IT Alerts