Logging & Monitoring Policy
What PersivX records about who did what, where those records are kept, what raises an alert, and who looks at them.
| Policy owner | Persiv Technology |
|---|---|
| Approved by | Harsh Jain and Ankit Kumar |
| Effective from | 1 November 2026 |
| Reviewed | At least once a year, and after any significant change or incident. Next review: 1 November 2027 |
What Is Recorded
PersivX writes a security event for:
- sign-ins, failed sign-ins, paused sign-ins, password resets and password changes;
- two-step verification: failed codes, turning it on or off, recovery-code use, an admin reset;
- every refused request: a permission refusal, a workspace query outside the caller's organization, a rate limit, a custom query that isn't read-only;
- admin actions, including changing an organization's admin, blocking a user and downloading a database backup;
- data governance changes: masking and row-visibility rules saved as a draft, and published;
- ending every session from the command line.
Each event records the time, the user, their network address and the address requested. Report activity (loads, exports, deliveries, one row per recipient per scheduled run) goes to the activity log in the database.
Where Records Go
- The activity log is the
auditlogstable in the PersivX database. - Security events also go to a file (
SECURITY_LOG_FILE) and/or syslog (SECURITY_LOG_SYSLOG_ADDRESS). On Persiv-run servers they are kept on the server itself and rotated by logrotate. There is no separate log store yet, so anyone with access to the server could change them. - Logs are kept as set in Data Retention. Server clocks are kept accurate with the cloud provider's time service (NTP through the operating system's chrony).
Alerts
PersivX sends an alert straight away, by email to the addresses in SECURITY_ALERT_EMAILS (through the server's own mail settings) and, if set, to a chat webhook (SECURITY_ALERT_WEBHOOK_URL), when:
- two-step verification is turned off or reset by an admin;
- an organization's admin is changed, or a user is blocked;
- a full database backup is downloaded;
- every session is ended from the command line;
- a Data API client is pointed at a different user from the command line;
- an organization's single sign-on settings are changed;
- data governance (masking or row-visibility) rules are published;
- failed sign-ins pass 25, or refused requests pass 50 (both adjustable), within 10 minutes. Each kind of alert is sent at most once in 10 minutes.
On Persiv-run servers alerts are emailed to support@persivx.com. Harsh Jain or Ankit Kumar acknowledges each alert within 1 business day and, if it may be an incident, follows Incident Response.
Review
- Harsh Jain or Ankit Kumar reviews security events every month for patterns no single alert shows, such as one account failing sign-in from many places, and records that the review happened.
- There is no availability monitoring of servers, the database or the scheduler yet.
- Logs never contain passwords, tokens, or datasource credentials.
