Study guide
2.3 Event Notification Engine (ENE) & Notification Administration
CyberArk Defender - PAM PAM-DEF
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Vault Architecture, Network & Security
1.1 CyberArk PAS Core Architecture & Component Topology 1.2 Vault OS Hardening, Network Isolation & Port Requirements 1.3 Vault Cryptography, Encryption Keys & Master User Recovery
2 Chapter 2: Vault Configuration, Administration & CLI Utilities
2.1 Vault Server Configuration Files & DBParm.ini Tuning 2.2 Vault Administrative Utilities & PARClient Commands 2.3 Event Notification Engine (ENE) & Notification Administration
3 Chapter 3: Password Vault Web Access (PVWA) Administration
3.1 PVWA Web Portal Architecture & Interface Configuration 3.2 PVWA REST API Administration & Lifecycle Automation 3.3 PVWA Security Settings, User Access & Session Timeouts
4 Chapter 4: Central Policy Manager (CPM) Architecture & Operations
4.1 CPM Service Architecture, Logs & Multi-CPM Load Distribution 4.2 The Credential Management State Machine: Change, Verify & Reconcile 4.3 CPM Plug-in Architecture, Process/Prompts Files & Custom Plug-in Troubleshooting 4.4 Loosely Connected Devices: Rotating Laptop & Workstation Credentials
5 Chapter 5: Safe Design, RBAC & Account Governance
5.1 Enterprise Safe Architecture & Naming Conventions 5.2 Safe Permissions, Authorizations & Safe Handler Delegation 5.3 Object Versioning, Retention Policies & Storage Quotas 5.4 Mandatory Account Properties, Account Types & Linked Accounts 5.5 Vault Users, Predefined Groups & Vault-Level Authorizations
6 Chapter 6: Account Discovery & Lifecycle Workflows
6.1 Automated Account Discovery, Detection Rules & Pending Accounts 6.2 Dual Control Workflows, Multi-Level Approvals & Master Approver 6.3 Exclusive Access, One-Time Passwords (OTP) & Check-out Automation 6.4 Bulk Onboarding: Password Upload Utility, Bulk Upload REST API & AccountUploader
7 Chapter 7: Master Policy & Platform Management
7.1 Master Policy Framework & Enterprise Compliance Rules 7.2 Platform Architecture, Settings Tree & Platform Duplication 7.3 Platform Policy Overrides, Advanced Settings & Target Tuning
8 Chapter 8: Privileged Session Manager (PSM) Core Architecture
8.1 PSM Architecture, Jump Host Isolation & Service Accounts 8.2 PSM Connection Components (PSM-RDP, PSM-SSH, PSM-Web) 8.3 PSM Universal Connector Framework & Custom Integrations 8.4 Split Workflow: Separating Session Use from Credential Retrieval
9 Chapter 9: PSMP, HTML5 Gateway & Session Security
9.1 PSM for SSH (PSMP) Architecture & Unix Proxy Brokering 9.2 PSM HTML5 Gateway Architecture & Clientless Web Access 9.3 Session Recording, Storage in Recordings Safes & Vault Retention 9.4 CyberArk Remote Access (Vendor PAM): Administering Third-Party Privileged Access
10 Chapter 10: Live Session Auditing, Reporting & Privileged Threat Analytics
10.1 Live Session Monitoring, Shadowing & Active Termination 10.2 Privileged Threat Analytics (PTA) Behavioral Anomaly Detection 10.3 PTA Automated Incident Response & SIEM Integration (CEF/Syslog) 10.4 Vault Reports, Report Authorizations & the Export Vault Data (EVD) Utility
11 Chapter 11: Application Access Manager (AAM) & Secrets Management
11.1 AAM Credential Provider (CP) Architecture & Local Memory Cache 11.2 Central Credential Provider (CCP) & Web Service Integration 11.3 Application Server Credential Provider (ASCP) & Application Authentication (AppID) 11.4 Conjur Secrets Manager & Cloud-Native DevOps Workflows
12 Chapter 12: Directory Integration, Disaster Recovery & Troubleshooting
12.1 Directory Integration: LDAP Mapping, RADIUS MFA & SAML 2.0 SSO 12.2 Disaster Recovery (DR) Vault & PADR Replication Architecture 12.3 Vault Backup Operations with PAReplicate & Safe Recovery 12.4 Diagnostic Procedures, Vault/CPM/PSM Error Codes & System Recovery
2.3 Event Notification Engine (ENE) & Notification Administration
Key Takeaways Explain This Topic AI
The Event Notification Engine (ENE) is a Vault-hosted Windows background service that monitors internal queues to deliver real-time email alerts independently of PVWA or CPM availability.
ENE configuration is bifurcated: ENEConf.ini on the local Vault file system defines SMTP host connectivity, while NotificationEngine.ini inside the Notification Engine Safe defines alerting rules and triggers.
Alert policies monitor critical operational events including CPM password change/reconcile failures, repeated account lockouts, Safe storage capacity thresholds, and system health status.
Notification layouts are driven by XSL templates stored in the Notification Engine Safe, dynamically injecting XML event parameters such as account address, error codes, and Safe names.
On hardened Vault servers, ENE SMTP delivery failures frequently stem from disabled DNS services or blocked outbound TCP port 25, requiring static IP definitions or hosts file mapping.
Last updated: September 2026
2.3 Event Notification Engine (ENE) & Notification Administration
Quick Answer: The CyberArk Event Notification Engine (ENE) is a dedicated Windows service ( CyberArk Event Notification Engine ) hosted directly on the Digital Vault server. It operates an event-driven listener that parses Vault audit and operational queues, formats alerts using XSL templates, and dispatches email notifications via SMTP. Low-level mail relay settings reside in ENEConf.ini on the Vault host, while alert rules and recipient templates reside securely inside the Notification Engine Safe.
Event Notification Engine (ENE) Architecture & Mechanics
The Event Notification Engine functions as the automated alerting hub of the CyberArk Privileged Access Management solution. Implemented as a native Windows service ( ENE.exe ), it runs locally on the Vault server host. Because ENE executes directly on the Vault rather than on distributed component servers, it guarantees that critical operational alerts—such as component failures, security violations, and database anomalies—can be processed and dispatched even if Password Vault Web Access (PVWA) or Central Policy Manager (CPM) services are offline.
Decoupled Event-Driven Processing
The ENE architecture operates independently from synchronous user transactions:
Event Interception : As operations occur across the PAM environment (e.g., CPM password rotations, administrator logons, or authentication failures), the Vault database records event entries into dedicated internal notification queue tables.
Queue Monitoring : The ENE background daemon continuously polls these internal database queues.
Rule Evaluation : When an event is detected, ENE evaluates it against active alerting rules defined in NotificationEngine.ini .
Transformation & Dispatch : If an event matches an alerting rule, ENE extracts dynamic metadata (Safe name, account name, target IP, error code, timestamp), merges it with the corresponding Extensible Stylesheet Language (XSL) template, and transmits an email via the configured corporate SMTP relay.
Configuration Architecture: ENEConf.ini vs. NotificationEngine.ini
A central concept on the PAM-DEF certification exam is the architectural division between the two primary ENE configuration files:
1. ENEConf.ini (Host-Level File System Configuration)
Located on the local file system of the Vault server at C:\Program Files (x86)\PrivateArk\Server\Conf\ENEConf.ini . It dictates low-level service parameters, network connectivity, and outbound SMTP relay communication:
SMTPServerIP : IPv4 address or resolvable hostname of the corporate mail server/relay.
SMTPServerPort : Outbound network port (typically 25 for standard SMTP, or 587 for authenticated TLS).
Sender : The email address populated in the "From:" header of all outgoing alerts.
SMTPAuthMethod : Authentication mechanism required by the mail relay ( None , Basic , or NTLM ). When enabled, SenderPassword references an encrypted credential file created by CreateCredFile.exe .
KeepMessagesInQueue : When set to Yes , ENE retains undelivered email alerts in its local queue if the SMTP relay is temporarily unreachable.
QueueExpirationTime : Number of days undelivered messages are preserved before being permanently purged.
2. NotificationEngine.ini (Vault-Stored Operational Rules)
Stored securely inside the Vault within the Notification Engine Safe . It defines the logical alerting policy of the organization: which events trigger notifications, which recipient templates are invoked, and which distribution lists receive messages. Because it is stored inside a Vault Safe, it automatically replicates to Disaster Recovery (DR) Vaults via PADR replication , ensuring identical alerting behavior upon failover without manual synchronization.
Monitored Security Events & Operational Triggers
Administrators configure ENE alert rules to capture critical operational and compliance events:
CPM Password Failures : Dispatched when Central Policy Manager fails to verify, change, or reconcile a credential (e.g., target host unreachable, permission denied, password complexity violation).
Account Lockout & Security Anomalies : Real-time alerts on multiple consecutive failed authentication attempts against a Vault user or administrative account lockout events.
Safe Quota & Version Thresholds : Warnings issued when a Safe approaches 90% or 100% of its disk storage quota or when version retention limits risk object purging.
System Health & Workflow Requests : Alerts covering PrivateArk Server service state changes, DR replication synchronization lag, and pending dual-control authorization requests.
Recipient Templates & XSL Customization
All notification email layouts are governed by Extensible Stylesheet Language (XSL) templates stored inside the Notification Engine Safe . Standard built-in templates include:
PasswordChangeFailed.xsl : Formats CPM password rotation failure alerts.
PasswordReconciliationFailed.xsl : Formats reconciliation error details.
AccountLocked.xsl : Formats user lockout alerts.
SafeCapacityExceeded.xsl : Formats Safe storage warnings.
DualControlRequest.xsl : Formats access approval request notifications.
Dynamic Variable Substitution
When an event occurs, ENE packages audit telemetry into an XML document. The XSL stylesheet parses this XML payload and dynamically substitutes variable tokens into the final email:
Variable Tag Description
<SafeName> The name of the Safe containing the affected account.
<AccountName> The target account username stored in the Safe.
<Address> The hostname or IP address of the managed target asset.
<PolicyID> The associated PAM platform ID governing the account.
<CPMError> The specific error code and diagnostic text returned by CPM.
<Timestamp> Date and time the event was recorded in the Vault.
<Requestor> Username of the operator who triggered the workflow.
Customizing these templates allows organizations to include corporate escalation instructions or structured headers that allow IT Service Management (ITSM) tools (e.g., ServiceNow, Jira) to automatically ingest alerts and create incident tickets.
ENE Operational Diagnostics & Troubleshooting
When email alerts fail to arrive, administrators investigate the operational log file at C:\Program Files (x86)\PrivateArk\Server\Logs\ENE.log . Common failure modes include:
DNS Resolution Failure on Hardened Vault : Hardened Vaults intentionally disable DNS client services to prevent DNS spoofing. If SMTPServerIP in ENEConf.ini uses an FQDN rather than an IP, ENE cannot resolve the address. Administrators must configure a static IPv4 address or add an entry in C:\Windows\System32\drivers\etc\hosts .
Windows Firewall Blocking Outbound Port 25 : The Vault's hardened firewall blocks outbound network traffic by default. An outbound firewall rule must permit TCP traffic from the Vault host to the SMTP relay on port 25 or 587.
SMTP Relay Authentication Rejection : Mail relays often reject unauthenticated submissions ( 550 5.7.1 Unable to relay ). The Vault's IP must be whitelisted on the mail relay's anonymous connector, or valid credentials must be supplied via CreateCredFile.exe .
Architectural Comparison: ENE Configuration Artifacts
- Feature ENEConf.ini NotificationEngine.ini XSL Templates
- Storage Location Local File System ( Server\Conf\ ) Notification Engine Safe Notification Engine Safe
- Scope Low-Level SMTP & Socket Transport High-Level Alert Rules & Triggers Visual Presentation & Layout
- Replication to DR No (Configured per Vault node) Yes (Replicates via PADR) Yes (Replicates via PADR)
Primary Settings SMTPServerIP , SMTPServerPort , Sender Event filters, Recipient mappings HTML structure, <CPMError> tags
Diagnostic Source Evaluated on ENE service startup Evaluated upon each queue event Parsed during message compilation