1. Home
  2. Blog
  3. Security, Fraud & Insider Threats

Employee Monitoring Alert Rules: 20 Examples, Thresholds and Routing

Published: Read time: 8 minsAuthor: Subhash Miriyala

Employee Monitoring Alert Rules: 20 Examples, Thresholds and Routing

Summary

Employee monitoring alert rules are conditions you define in monitoring software that send a notification to a named person when a specific event or pattern occurs, such as a USB drive being inserted, a large upload to personal cloud storage or a missed clock-in. A good rule has six parts: a trigger, a threshold or condition, a scope, a severity, a recipient and an expected first response. This guide gives 20 example rules grouped by goal (data security, access and login, attendance and time, productivity and wellbeing, policy and compliance), explains when to use a fixed threshold and when to use a baseline-based anomaly rule, and sets out how to roll alerts out without flooding your team. Start every rule in observation, tune it for two weeks, and only then let it page anyone.

E-Monitor's real-time alerts let you build rules on idle time, app category, URL pattern, USB events, file access and geographic mismatch, set severity, and route to Slack, Microsoft Teams, email, SMS or webhook with escalation. Start free →

What Are Employee Monitoring Alert Rules?

An alert rule turns monitoring data into a decision point. Dashboards and activity logs record what happened; a rule decides which of those events deserves a human's attention right now, and whose attention. Without rules, security and operations teams either review logs after the fact or miss events entirely.

Every rule in this guide is written in the same six-part format, and you should document your own rules the same way:

  • Trigger: the signal the rule watches (USB event, file access, outbound connection, clock-in, app category, URL pattern).
  • Condition or threshold: what makes the signal alert-worthy (any occurrence, a count in a time window, or a deviation from normal).
  • Scope: which users, teams or roles the rule applies to.
  • Severity: low, medium, high or critical. Severity drives channel and escalation timing.
  • Recipient: a named role, not a shared inbox nobody owns.
  • First response: the first thing the recipient does. If you cannot write this down, the rule is not ready.

Threshold Rules vs Anomaly-Based Rules

There are two ways to define when a rule fires, and most mature setups use both.

Threshold ruleAnomaly-based rule
How it firesA fixed condition is met: any USB insert, more than 25 files copied in 60 seconds, no clock-in 10 minutes after shift startBehavior deviates from that user's own normal pattern, such as an unusual login time or an app they never use
Best forHard policy lines and clear-cut eventsBehavior that varies by person and role, where one fixed number would be wrong for half the team
Setup effortLow; works on day oneNeeds a learning period before it is reliable
Main riskToo tight floods the channel; too loose misses real eventsNoisy during the learning period and after legitimate changes such as a new role

In E-Monitor, anomaly detection learns each user's baseline over a rolling 30-day window and fires on deviations. That means anomaly rules should be switched on early but kept at low severity for the first month. For a fuller explanation of how baselines behave and how to treat their output as a prompt for review rather than a verdict, see our guide to anomaly detection in employee monitoring.

Data Security and Insider Threat Alerts

These are the rules most security teams enable first, because the events are rare, specific and expensive to miss. Insider threat alerts should go to security, not to line managers.

#RuleSuggested conditionSeverityRecipientFirst response
1Unapproved USB storage insertedAny mass-storage device not on the allowlistHighIT securityConfirm the block held; check whether the user has a pending exception request
2Bulk file copy from a sensitive folderMore than N files read or copied in T seconds from a Confidential or Restricted folder, or well above the user's baselineHigh; critical if the destination is removable media or personal cloudIT securityReview the file list and destination; preserve the log before contacting anyone
3Upload to unapproved cloud storageConnection or sync to a personal Dropbox, iCloud, personal Google Drive or personal OneDrive from a managed deviceHighIT securityCheck volume and timing; confirm whether an approved alternative exists for the task
4Abnormal upload volumeOutbound bytes to a destination well above the user's 30-day baseline, or a large transfer to a never-seen destinationHighIT securityCorrelate with file access events in the same window
5Personal VPN, proxy or Tor connectionAny tunnel to a consumer VPN, proxy pool or Tor entry nodeMediumIT securityConfirm it is not an approved tool; remind the user of policy

Rules 2 and 4 are stronger together than apart. A combination rule that fires when a sensitive-folder copy and an abnormal upload happen within the same hour is far more specific than either signal alone. The file access monitoring and USB blocking pages describe the underlying signals.

Access and Login Alert Rules

#RuleSuggested conditionSeverityRecipientFirst response
6Unusual login timeAnomaly: sign-in well outside the user's 30-day patternMediumIT securityVerify with the employee through a known channel, not by replying to the session
7Geographic mismatchActivity from a location that does not match the user's expected regionHighIT securityVerify travel; if unexplained, reset credentials and review the session
8Possible account sharingAlternating behavioral profiles on one account (behavioral biometrics, opt-in per role)HighIT securityTrigger step-up re-authentication; then talk to the account owner
9Uncharacteristic app accessAnomaly: user opens an admin, finance or HR application not in their baselineMedium; high for privileged systemsIT security and the application ownerCheck whether the access right is still needed

Login rules generate false positives around travel, shift changes and new roles. Tell users in advance that a verification message may come from IT, so a genuine check is not mistaken for phishing. Related guides cover detecting unauthorized logins, detecting account sharing and privileged user monitoring in more depth.

Attendance and Time Alert Rules

#RuleSuggested conditionSeverityRecipientFirst response
10Missed clock-inNo clock-in by the end of the shift grace windowMediumOn-duty supervisorContact the employee; arrange cover if the role is coverage-critical
11Repeated late clock-insLate clock-in flagged three or more times in a rolling two weeksLowManager, in a weekly digestPrivate conversation about the cause
12Overtime thresholdDaily or weekly hours exceed the limit set in your overtime policyMediumManagerApprove, or redistribute work before the limit is crossed again
13Extended idle during a coverage shiftContinuous idle beyond your configured idle threshold during a scheduled coverage windowLowSupervisor, coverage roles onlyCheck for an offline task or meeting before assuming anything

Use snooze for approved absences and leave, otherwise rule 10 will fire on every holiday. For non-exempt staff, rule 12 is also a pay-accuracy control: hours worked must be paid whether or not overtime was approved. Our guide to tracking employee login and logout times explains the attendance data behind these rules.

Productivity Alerts and Wellbeing Signals

Productivity alerts are where most alerting programs go wrong. A real-time alert telling a manager that someone spent 20 minutes on a news site invites micromanagement and teaches nothing. Productivity data is better read as weekly trends, and wellbeing signals should reach the employee or HR before a manager.

#RuleSuggested conditionSeverityRecipientFirst response
14Sustained long daysOvertime threshold met on three or more days in a weekLowHR or people partner; manager as a workload prompt onlyWorkload check-in, not a performance conversation
15Distracting category timeTime in a flagged category (streaming, gaming) during work hours above a daily limitLowThe employee, through a policy nudgeNone from the manager unless a weekly trend persists
16Work on rest daysClock-ins on scheduled days off or outside assigned shifts, repeated over several weeksLowHR or people partnerAsk whether workload or staffing is the cause

Notice that none of these three rules sends a real-time alert to a line manager about an individual. That is deliberate: the same data that protects people from overwork becomes surveillance when it is used to watch the clock.

Policy and Compliance Alert Rules

#RuleSuggested conditionSeverityRecipientFirst response
17Blocked category openedAny attempt to open a category on the block listLowLog only; manager if repeatedUsually none: the block did its job
18Policy nudges repeatedly acknowledgedFive or more nudge acknowledgments for the same flagged domain in a weekLowManager, in a weekly digestClarify policy; check whether the site is actually needed for work
19Restricted URL pattern outside roleURL pattern for a sensitive system (payroll admin, customer data export) opened by a role that should not use itHighIT security and the data ownerReview the access right; confirm whether data was viewed or exported
20Unapproved SaaS or AI toolNew domain outside the approved SaaS list used during work hoursLowIT, in a weekly shadow IT reviewAssess the tool; approve, offer an alternative or block

Rule 20 is a discovery rule, not a disciplinary one. Most unapproved tools signal an unmet need. The shadow IT detection guide covers the review process.

How to Roll Out Alert Rules Without Flooding Your Team

  1. Pick five rules, not twenty. Start with the data security rules and missed clock-in. Add the rest once the first set is stable.
  2. Run in observation for two weeks. Set new rules to low severity and route them only to a review channel or the alert log, so nobody is paged. Count how often each would have fired and how many of those firings mattered.
  3. Tune alert thresholds from that data. Raise counts that fired on routine work, narrow scopes to the roles that matter, and add exceptions for known tools and service accounts.
  4. Promote rules one at a time. Move a rule to its real severity and recipient only when its false-positive rate is acceptable to the person receiving it.
  5. Write the first response into the rule. Every rule needs a documented owner and first step before it goes live.
  6. Review monthly. Retire rules nobody acts on and check snooze and acknowledgment patterns for signs of fatigue.

If a rule is still noisy after tuning, read our guide to employee monitoring alert fatigue before adding more rules on top.

Routing, Severity and Escalation

Severity should map to a channel and a response time, written down in one place:

  • Critical: page the on-call security responder (SMS or PagerDuty) and escalate to the security lead if not acknowledged within minutes. Reserve for active exfiltration patterns.
  • High: security channel in Slack or Microsoft Teams plus email; acknowledge the same business day.
  • Medium: the relevant channel for the owner (security or the on-duty supervisor); review within the shift.
  • Low: daily or weekly digest, or log only.

Route by scope as well as severity. A missed clock-in for the night shift should reach the night supervisor, not the day manager. In E-Monitor, an escalation policy attached to a rule moves an unacknowledged alert to the next tier, acknowledgments and snoozes are recorded in the alert history, and signed webhooks can send security alerts to your SIEM. Decide who owns each alert type before go-live; an employee monitoring RACI matrix is a simple way to record it.

Privacy Guardrails for Real-Time Monitoring Alerts

  • Disclose the categories of alerts. Employees should know that USB, file, upload and attendance events can generate alerts. Notice is legally required in some places; see our employee monitoring laws by state.
  • Keep wellbeing signals away from performance management. Long hours and weekend work go to the employee or HR as a support signal, not to a manager as a mark against someone.
  • Limit who sees security alerts. Insider threat alerts contain sensitive context. Route them to security, and give managers only what they need to act.
  • Treat an alert as a question, not a finding. Check context before contacting the employee, and never discipline on a single alert.
  • Alert only on work-hours data. E-Monitor captures activity only while an employee is clocked in, so rules cannot fire on off-hours personal activity.

Frequently Asked Questions

1. What are employee monitoring alert rules?

They are conditions set in monitoring software that notify a named person when a specific event or pattern occurs, such as an unapproved USB device, a large upload to personal cloud storage or a missed clock-in. Each rule has a trigger, a condition, a scope, a severity, a recipient and a first response.

2. How many alert rules should we start with?

Start with about five: the main data security rules plus missed clock-in. Run them in observation for two weeks, tune the thresholds, then add more. Launching twenty rules on day one usually produces so many alerts that people stop reading them.

3. What is the difference between a threshold alert and an anomaly alert?

A threshold alert fires when a fixed condition is met, such as any USB insert or 25 files copied in a minute. An anomaly alert fires when behavior deviates from that user's own normal pattern, which E-Monitor learns over a rolling 30-day window.

4. Who should receive insider threat alerts?

IT security or a designated security responder, not line managers. Insider threat alerts carry sensitive context and need a consistent, evidence-first response. Managers can be brought in once security has reviewed the alert and decided action is needed.

5. Should managers get real-time productivity alerts?

Generally no. Real-time productivity alerts encourage micromanagement. Distracting-site use is better handled with a policy nudge to the employee and weekly trend reports for managers, and wellbeing signals such as long hours should go to the employee or HR first.

6. How do you set alert thresholds?

Begin with a reasonable starting value, run the rule without paging anyone for two weeks, and count how often it fired and how often that mattered. Raise or narrow the threshold until the person receiving it considers the false-positive rate acceptable.

7. Do employees need to be told about monitoring alerts?

Telling employees which categories of activity can generate alerts is good practice, and notice of monitoring is legally required in some jurisdictions, such as New York, Connecticut and Delaware, and under GDPR. Check requirements with counsel for your locations.

Turn monitoring data into alerts people act on. E-Monitor gives you rule-based and baseline-based alerts with severity, routing and escalation, built on work-hours data only. 7-day free trial, no credit card. Sign up →

Ready to see E-Monitor in action?

E-Monitor deploys in minutes with screenshots, productivity analytics, real-time alerts and compliance-ready reporting. 7-day free trial, no credit card required.