Audit Logs

Overview

The Audit Logs feature in DeepTraQ provides a complete record of actions performed within the platform. It allows administrators and security teams to monitor user activity, track configuration changes, and maintain accountability across the system.

Audit logs capture important operational events such as:

• Scan creation
• Scan updates or configuration changes
• Scan execution events
• Scan deletions
• System activity related to security scans

These logs help organizations maintain operational transparency, security monitoring, and compliance reporting by providing a chronological history of actions performed in the platform.

The Audit Logs interface allows teams to:

• Track all scan-related activities performed in the system
• Monitor who initiated scans or modified configurations
• Review historical actions for troubleshooting and investigation
• Maintain compliance with audit and governance requirements
• Identify unauthorized or unexpected changes in scanning operations

---

Prerequisites

Before accessing Audit Logs, ensure the following:

• Access to the DeepTraQ platform
• Appropriate user permissions to view system logs
• Scan activities or system events recorded in the platform

---

Viewing Audit Logs

Follow these steps to view audit logs in DeepTraQ.

1. Navigate to Audit Logs

Open the Audit Logs section from the platform dashboard.

This section displays a chronological timeline of activities performed within the system.

---

2. Review Logged Activities

The audit logs display entries for different system actions such as:

• Created new scan
• Scan initiated
• Updated scan configuration
• Deleted scan

Each event shows the action performed along with the associated scan or resource.

Example events:

• Created new scan – Azure Cloud Workload – Complete Vulnerability Assessment
• Scan initiated – test-credit-2
• Updated scan – test-credit-activity-asset
• Deleted scan – fzdxgchvjbklm

---

3. Review Event Details

Each audit log entry includes important information such as:

• The type of action performed
• The scan or resource involved
• The time the event occurred

Example:

Created new scan – Azure Cloud Workload – Complete Vulnerability Assessment
March 10, 2026 at 03:43:21 PM GMT+05:30

This helps administrators understand when the activity occurred and what operation was performed.

---

4. Track Scan Activities

Audit logs allow teams to track the lifecycle of scans, including:

• When a scan was created
• When the scan execution started
• Changes made to scan configuration
• Deletion of scans from the system

This helps maintain visibility into scan management activities across the organization.

---

5. Use Logs for Investigation and Compliance

Audit logs are useful for:

• Investigating unexpected system changes
• Tracking user activity for security monitoring
• Reviewing historical actions during security assessments
• Maintaining compliance with governance and audit requirements

Security teams can review these logs to ensure that all activities within the platform are authorized and properly documented.

---

Field Reference

Field	Description	Example
Action	The operation performed in the system	Created new scan
Resource	The scan or entity affected by the action	Azure Cloud Workload – Complete Vulnerability Assessment
Event Type	Category of activity recorded	Scan Initiated
Timestamp	Date and time when the action occurred	March 10, 2026 at 03:43:21 PM GMT+05:30
Activity Entry	Full audit log record describing the event	Updated scan – test-credit-activity-asset

---

Example Audit Log Entries

Action	Resource	Timestamp
Created new scan	Azure Cloud Workload – Complete Vulnerability Assessment	March 10, 2026
Scan initiated	test-credit-2	March 09, 2026
Scan initiated	test-port	March 09, 2026
Updated scan	test-credit-activity-asset	March 09, 2026
Created new scan	test-credit-2	March 03, 2026
Deleted scan	fzdxgchvjbklm	February 25, 2026

These entries provide a historical record of scan operations performed within the platform.