Empuls generates and manages security logs as a first-class control in the cloud environment, with all key events captured, centrally stored, and continuously monitored through our SIEM stack (Sentinel One) and internal ISMS processes.
- What we log: The application logs all server-side interactions, including user authentication and authorization events, admin actions, configuration changes, API requests/responses, and processing milestones. Sensitive parameters in requests and responses are obfuscated before being written to the log stream, while still preserving full traceability for investigations.
- Storage, retention & tamper-resistance: Logs are written to centralized, access-controlled logging backends where only authorised operations and security personnel can view them. Our ISMS logging and monitoring controls require event logging, protection of log information, and separate administrator/operator logs; logs are treated as append-only records and time-synchronised to support forensically sound investigations. System/telemetry logs are archived after 7 days, while customer and system data are retained for the contract term with backups preserved up to 7 years (with cryptographic erasure on request).
- SIEM integration & monitoring: Security events and audit logs are exported in JSON/CSV via API and ingested into Sentinel One, which is used for correlation, anomaly detection, and alerting. The InfoSec team monitors SIEM dashboards and alerts to detect brute-force attempts, unusual access patterns, or suspicious API usage, and responds under our ISO-aligned incident management process.
Does Empuls have fraud detection and security alerts?
Empuls uses DLP, EDR, and SIEM systems to detect fraud in real time, automatically alerting security teams to any suspicious activity.
Empuls' User Logins and Integrate with Siem Solutions
Empuls logs every login with timestamp, IP address, and device data, and integrates with SIEM tools like Miral via API for centralized security…