Services › Security & Governance

Salesforce Shield & Event Monitoring

Access governance shows who is allowed to do what. Salesforce Shield shows what actually happens with that access. We configure Shield for the scenarios that matter to you, with assigned follow-up.

Analyst follows charts and a timeline with a notable event on two screens

The problem

Prevention is never complete. Permissions are granted that turn out to be too broad in hindsight, an integration does more than intended, or an account is taken over. Without insight into behavior, you only notice this when something visibly goes wrong, and then the first question is always the same: when did this start and what exactly happened?.

Signs that this is happening

  • You cannot determine who exported which data in the past few months
  • There is no notification when someone requests an unusually large number of records
  • Logging is enabled, but no one has been assigned to monitor it
  • The retention period for logs is shorter than the period about which an auditor asks questions

Event in Salesforce

Event Monitoring

Detection and Transaction Security

SIEM or SOC

Succession with owner

Monitoring only works if someone sees the alert and follows up.

What we do

Determine scenarios

Determine which scenarios truly matter to you, instead of turning on everything that can be turned on.

Determine event types and license

Which event types are required for this and whether your license provides them. Event Monitoring requires Salesforce Shield or the standalone Event Monitoring add-on.

Setting up detection

By data volume, unusual exports, login patterns, and API usage.

Transaction Security Policy

Where real-time blocking, an additional verification step, or a notification is appropriate.

Align retention periods

Meeting your audit and research needs, with Field Audit Trail where field history must be preserved longer.

Proceed to SIEM and SOC

Forward logs to your SIEM and arrange for follow-up together with your SOC.

Screen with a connection diagram in which one connection displays a warning

For whom and what it yields

For whom

  • Security teams that want to connect Salesforce to their own SIEM or SOC
  • CISOs who want detection on data volume, privileged usage, and integrations
  • Platform Owners who want to be able to reconstruct what happened after an incident
  • Organizations that need to encrypt sensitive fields or retain field history for longer

What it yields

  • Notifications on the events that matter, with as little noise as possible
  • A documented follow-up: who monitors, how often, and what happens upon a report
  • Sensitive fields encrypted with Platform Encryption, where your requirements demand it
  • The ability to reconstruct what happened after an incident
  • Salesforce events visible in the same view as the rest of your landscape

Where this work begins

Monitoring works best on top of a sound permissions model. We therefore usually start with a Salesforce Security Assessment, so that detection aligns with the risks identified there.

Frequently Asked Questions

Do we need Salesforce Shield for this?

That depends on what you want to see and how long you want to retain it. Event Monitoring requires Salesforce Shield or the standalone Event Monitoring add-on; exactly which event types and retention periods are available varies by license and release. We determine this within your own organization rather than making assumptions. We do not sell licenses and have no interest in recommending an add-on you do not need.

We already have a SIEM. What do you add, then?

The integration is usually the easy part. What is typically missing is the translation: which Salesforce events are significant, which thresholds make sense in your context, and what needs to happen if something is triggered. We provide that substantive layer.

Could you also follow up on the reports for us?

We offer continuous monitoring and remediation support as an optional follow-up service; the scope and frequency are agreed upon separately. We do not offer 24/7 SOC services. For real-time follow-up, we connect to your own SOC or SIEM.

How do you prevent us from being overwhelmed with reports?

By starting small. We first set up a limited number of scenarios, measure the number of alerts this generates for a period, and adjust the thresholds before adding more. A detection that no one reads anymore is worse than no detection.

What is the difference between Event Monitoring and Field Audit Trail?

Event Monitoring records what users and integrations do, such as logins, exports, report views, and API calls. Field Audit Trail concerns the history of fields: what value a field had and who changed it and when. Standard field history tracks a maximum of 20 fields per object and retains them for a limited time; with Field Audit Trail, you track up to 60 fields per object and retain the history for up to ten years. Which of the two you need depends on the questions you want to be able to answer retrospectively.