Skip to main content
< All Topics
Print

Req 2.22: Generate automated alerts for, among others:

📋 Requirement Details

Req 2.22: Generate automated alerts for, among others:
1. Newly enrolled or newly detected devices;
2. High-risk or critical actions executed on managed endpoints.

⚙️ Technical Demonstration

IMTLazarus natively fulfills this requirement through a centralized security auditing and notifications framework located under the Logs & Activity ecosystem. The platform captures real-time endpoint telemetries and generates structured entries for critical lifecycle and compliance events. This includes dedicated monitoring panels for tracking newly registered assets (Device Enrollments) alongside persistent logs for high-risk or critical actions (such as system modifications, policy bypasses, or blocked actions), ensuring immediate operational visibility into DepEd fleet exceptions.


👨‍💻 Administrator Steps

Admin Setup Steps for Req 2.22

Configure Automated Notifications: Navigate to Admin > Setup > Notifications to map specific alert triggers (such as enrollment success or critical policy violations) directly to administrative emails or system webhooks.

Access Audit Logs: Log into the IMTLazarus dashboard and navigate to the left sidebar menu, expanding the Logs & Activity tab.

Track New Device Detections: Click on Device Enrollments to audit a live log of newly registered endpoints, tracking their authorization source, installation timestamps, and enrollment status.

Monitor Critical Endpoint Actions: Select the Logs sub-menu to view the system wide event feed, filtering by severity or action type to isolate high-risk operational events executed on managed endpoints.

🖼️ Visual Evidence

Table of Contents