audit-logging

Implement tamper-proof audit logging for TypeScript and Python applications.

783|62|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/dadbodgeoff/drift --skill audit-logging-dadbodgeoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-logging
Source: https://github.com/dadbodgeoff/drift/tree/main/drift%20v1%20depreciated/skills/audit-logging
Command: npx skills add https://github.com/dadbodgeoff/drift --skill audit-logging-dadbodgeoff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a robust and tamper-proof system for recording all significant user and system actions, crucial for security, compliance, and debugging.

Core Features & Use Cases

  • Comprehensive Auditing: Records actions, actors, resources, and outcomes with detailed context.
  • Tamper-Proof Storage: Ensures logs cannot be altered or deleted once recorded.
  • Compliance Ready: Meets requirements for SOC 2, HIPAA, GDPR, and PCI DSS.
  • Use Case: Track every login attempt (success or failure), data access, and modification to ensure accountability and aid in security investigations.

Quick Start

Use the audit-logging skill to record a user login event for user 'user-123' with outcome 'success'.

Frequently Asked Questions about audit-logging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement tamper-proof audit logging for compliance in TypeScript and Python?

Tamper-proof audit logging records user actions, data changes, and system events with contextual details like IP addresses, ensuring logs cannot be altered or deleted once recorded in TypeScript and Python applications.

What is the best way to track user actions and data changes for SOC 2 or HIPAA compliance?

Tracking user actions for SOC 2, HIPAA, GDPR, and PCI DSS compliance involves recording actors, resources, and outcomes with detailed context, storing them tamper-proof to ensure accountability and aid security investigations.

Does audit logging work with PostgreSQL and S3 storage backends?

Audit logging supports various storage backends including PostgreSQL and S3, allowing you to securely store tamper-proof records of system events, user logins, and data modifications across your applications.

How do I record a user login event with IP address and request ID for security investigations?

Recording a user login event involves logging the actor, outcome, and contextual details such as IP addresses and request IDs, creating a tamper-proof entry to ensure accountability and support security investigations.

Can I integrate cloud logging services with my application's audit logs?

Cloud logging services can be integrated with audit logs to centralize the tracking of system events, data access, and modifications, maintaining tamper-proof storage and compliance readiness across your infrastructure.

What are the limitations of using tamper-proof storage for audit logs?

Tamper-proof storage ensures logs cannot be altered or deleted once recorded, which is crucial for compliance and security but may require careful management of storage capacity as audit records accumulate indefinitely.