Enterprise Plan10 minutesintermediate

Enterprise Audit Logging

Advanced audit logging for enterprise - extended retention, SIEM integration, and compliance reporting.

auditloggingcomplianceenterprisesiem
Last updated: January 15, 2025
Enterprise Plan

Enterprise audit logging provides extended retention, real-time streaming, SIEM integration, and compliance-ready reporting.

Enterprise vs Standard Audit

FeatureStandardEnterprise
Retention90 daysExtended (custom)
ExportManual CSVAutomated, multiple formats
Real-time StreamingNoYes (SIEM integration)
Custom EventsLimitedExtensive
Compliance ReportsBasicSOC 2, HIPAA ready
SearchBasicAdvanced query
AlertsLimitedCustom rules

Extended Retention

Configure Retention

  1. Go to SettingsActivity tab
  2. Set retention period
  3. Save

Retention Options

PeriodUse Case
1 yearStandard enterprise
2 yearsFinancial services
CustomSpecific requirements (contact your account manager)

Storage Considerations

Extended retention includes:

  • All logged events
  • Full event details
  • Immutable storage
  • Encrypted at rest

Event Categories

Authentication Events

EventDetails Captured
login.successUser, IP, device, location
login.failedUser, IP, reason, attempts
logoutUser, session duration
mfa.enrolledUser, method
mfa.challengeUser, method, result
password.changedUser, admin/self
session.expiredUser, duration

Team Events

EventDetails Captured
member.invitedTarget, role, inviter
member.joinedUser, method
member.removedTarget, remover, reason
member.role_changedTarget, from, to, changer
member.permissions_changedTarget, changes, changer

Data Events

EventDetails Captured
data.exportedUser, type, date range, format
data.accessedUser, resource type, filter
report.generatedUser, report type, parameters
api.accessedKey, endpoint, response code

Configuration Events

EventDetails Captured
website.createdName, domain, creator
website.deletedName, deleter, reason
goal.createdName, type, creator
settings.changedSetting, old value, new value
integration.connectedType, configurer

Security Events

EventDetails Captured
sso.configuredProvider, configurer
policy.changedPolicy type, changes
ip_restriction.updatedIPs added/removed
brute_force.detectedTarget user, source IP
suspicious.activityType, details

Query Language

Search logs with advanced queries:

user:john@company.com AND action:login.* AND time:>2025-01-01

Query Operators

OperatorExampleDescription
ANDa AND bBoth conditions
ORa OR bEither condition
NOTNOT aExclude condition
:field:valueField equals
:*field:val*Wildcard match
:>time:>dateGreater than
:<time:<dateLess than

Search Examples

# Failed logins from specific IP
action:login.failed AND ip:192.168.1.100

# All admin actions today
role:admin AND time:>2025-01-15

# Data exports last 7 days
action:data.exported AND time:>now-7d

# Settings changes by specific user
user:admin@company.com AND action:settings.*

Saved Searches

Save frequently used queries:

  1. Execute search
  2. Click "Save Search"
  3. Name it
  4. Access from saved list

Real-Time Streaming

Webhook Delivery

Stream events via webhook:

  1. Go to SettingsActivity tab → Streaming
  2. Add webhook URL
  3. Select events to stream
  4. Enable

Webhook Payload

{
  "event_id": "evt_abc123",
  "timestamp": "2025-01-15T14:30:00Z",
  "event_type": "member.role_changed",
  "actor": {
    "id": "user_123",
    "email": "admin@company.com",
    "role": "admin"
  },
  "target": {
    "id": "user_456",
    "email": "john@company.com"
  },
  "details": {
    "from_role": "viewer",
    "to_role": "editor"
  },
  "context": {
    "ip": "192.168.1.100",
    "user_agent": "Chrome/120",
    "location": "San Francisco, CA"
  }
}

Event Filtering

Choose which events to stream:

☑ Authentication events
☑ Team management events
☑ Security events
☐ Data access events (high volume)
☐ API access events (very high volume)

SIEM Integration

Supported SIEMs

SIEMIntegration Method
SplunkHTTP Event Collector
DatadogLog forwarding
ElasticDirect integration
Sumo LogicHTTP source
QRadarSyslog
Microsoft SentinelAPI

Splunk Setup

  1. Create HTTP Event Collector in Splunk
  2. Get HEC token
  3. In Zenovay: SettingsActivity tab → SIEM
  4. Select Splunk
  5. Enter HEC URL and token
  6. Test connection
  7. Enable

Configuration

┌─────────────────────────────────────────────────────┐
│ SIEM Integration                                    │
│ ─────────────────────────────────────────────────── │
│                                                     │
│ Provider: [Splunk ▼]                               │
│                                                     │
│ HEC URL:                                            │
│ [https://splunk.company.com:8088/services/...  ]  │
│                                                     │
│ Token:                                              │
│ [••••••••••••••••••••                          ]  │
│                                                     │
│ Index:                                              │
│ [zenovay_audit                                  ]  │
│                                                     │
│ Events to Forward:                                  │
│ ☑ All security events                              │
│ ☑ Authentication events                            │
│ ☑ Team management                                  │
│ ☐ Data access (high volume)                        │
│                                                     │
│ [Test Connection] [Save]                           │
└─────────────────────────────────────────────────────┘

Compliance Reports

Pre-Built Reports

ReportUse Case
User Access ReportWho has access to what
Login ActivityAuthentication patterns
Permission ChangesRole and access changes
Data AccessWho accessed what data
Admin ActionsAll administrative activity

SOC 2 Report Package

Includes:

  • Access control audit
  • Change management log
  • Security event summary
  • User activity report

Generating Reports

  1. Go to Audit → Reports
  2. Select report type
  3. Choose date range
  4. Generate
  5. Download or schedule

Report Format

┌─────────────────────────────────────────────────────┐
│ SOC 2 Audit Report                                  │
│ Period: January 1-31, 2025                         │
│ Generated: February 1, 2025                        │
│ ─────────────────────────────────────────────────── │
│                                                     │
│ 1. Access Control Summary                           │
│    Total Users: 89                                  │
│    Admins: 5                                        │
│    Users Added: 8                                   │
│    Users Removed: 3                                 │
│                                                     │
│ 2. Authentication Summary                           │
│    Total Logins: 2,450                             │
│    Failed Logins: 45 (1.8%)                        │
│    MFA Compliance: 100%                            │
│                                                     │
│ 3. Security Events                                  │
│    Policy Changes: 2                               │
│    Suspicious Activity: 0                          │
│    Lockouts: 3                                     │
│                                                     │
│ [Full details in attached CSV]                     │
└─────────────────────────────────────────────────────┘

Custom Alerts

Alert Configuration

Create custom alert rules:

┌─────────────────────────────────────────────────────┐
│ Create Alert Rule                                   │
│ ─────────────────────────────────────────────────── │
│                                                     │
│ Name: Multiple Failed Logins                       │
│                                                     │
│ Condition:                                          │
│ Event type: [login.failed ▼]                      │
│ Count: [5] within [10] minutes                    │
│ Group by: [user ▼]                                │
│                                                     │
│ Severity: [High ▼]                                │
│                                                     │
│ Actions:                                            │
│ ☑ Email: security@company.com                      │
│ ☑ Slack: #security-alerts                          │
│ ☐ Webhook                                          │
│                                                     │
│ [Create Alert]                                     │
└─────────────────────────────────────────────────────┘

Alert Types

AlertTriggerRecommended Action
Brute Force5+ failed loginsInvestigate IP
Privilege EscalationRole → AdminVerify legitimate
Mass ExportLarge data exportReview need
Off-Hours AccessLogin outside businessConfirm user
New LocationLogin from new countryVerify user

Data Integrity

Immutable Logs

Audit logs are:

  • Write-once, read-many
  • Cannot be modified
  • Cannot be deleted (within retention)
  • Cryptographically verified

Hash Chain

Each event linked:

Event 1 → Hash → Event 2 → Hash → Event 3

Any tampering breaks the chain.

Verification

Verify log integrity:

  1. Go to Audit → Verification
  2. Select date range
  3. Run verification
  4. View results

Export Options

Automated Export

Schedule regular exports:

FrequencyDestination
DailyS3 bucket
WeeklySFTP server
MonthlyEmail

Export Formats

FormatUse Case
JSONSystem integration
CSVSpreadsheet analysis
CEFSIEM ingestion
LEEFQRadar

Bulk Export

For large exports:

  1. Request via SettingsActivity tab → Export
  2. Receive notification when ready
  3. Download from secure link
  4. Link expires in 24 hours

Best Practices

Regular Review

ReviewFrequency
Security eventsDaily
Admin actionsWeekly
Access changesWeekly
Full auditMonthly

Retention Strategy

Balance:

  • Compliance requirements
  • Storage costs
  • Investigation needs

Alert Tuning

  • Start with conservative thresholds
  • Tune based on false positives
  • Regular review of alert rules

Troubleshooting

Events Missing

If events not appearing:

  • Check date/time range
  • Verify event types selected
  • Allow processing time (few minutes)

SIEM Not Receiving

If SIEM integration fails:

  • Verify credentials
  • Check network connectivity
  • Review error logs
  • Test connection

Reports Slow

If reports take long:

  • Reduce date range
  • Filter to specific events
  • Schedule for off-hours

Next Steps

Was this article helpful?