Security
Proofpoint Essentials integration
Counts how many of each client's users are protected, and how many licenses they hold. Counts only — we never read a mailbox, address or message.
Setup steps are for connected customers — sign in to read them.
What we find in Proofpoint Essentials
How many of a client's people are actually on email security, against the seat count the PSA reports — plus licences bought and never deployed.
Every finding lands on your Client Upsell board as a named client with a number beside it — not a report you have to read.
What the Proofpoint Essentials connection does
Read — powers Client Upsell
Read your clients' stack
Who is actually protected: endpoints still onboarding, seats never deployed, sites with no filtering policy.
Read-only
We only ever read — we never change anything in Proofpoint Essentials
You make a view-only key using our setup steps. Our connection has no code that can write to Proofpoint Essentials, and your key is encrypted and only used to read.
Proofpoint Essentials integration — common questions
- What does the Proofpoint Essentials integration read?
- Counts how many of each client's users are protected, and how many licenses they hold. Counts only — we never read a mailbox, address or message.
- What does MSProspector find in Proofpoint Essentials?
- How many of a client's people are actually on email security, against the seat count the PSA reports — plus licences bought and never deployed.
- Is the Proofpoint Essentials connection read-only?
- Yes. We only ever read from Proofpoint Essentials — our Proofpoint Essentials connection has no code that can change anything, and an automated check on every change to our code blocks any that could. Please create a view-only key using the setup steps, so the key itself can't make changes either.