Compliance

Security toolkit for logging, tracking, and exporting compliance-related activities. Each command records timestamped entries to its own log file. Call without arguments to view recent entries; call with arguments to record a new entry.

Commands

Data Storage

All data is stored locally in ~/.local/share/compliance/. Each command writes to its own .log file (e.g., audit.log, policy.log). A unified history.log tracks all activity with timestamps.

Requirements

• Bash 4+
• Standard Unix utilities (wc, du, tail, grep, date, sed)

When to Use

• Logging compliance audit findings, policy checks, and security events with timestamps
• Tracking credential rotations, revocations, and strength checks over time
• Recording data store/retrieve operations for audit trail purposes
• Searching historical compliance entries by keyword
• Exporting compliance records to JSON, CSV, or plain text for regulatory reporting

Examples

# Record an audit finding
compliance audit "reviewed access controls for prod database — 3 issues found"

# Log a credential rotation
compliance rotate "rotated API keys for payment gateway"

# Record a policy update
compliance policy "updated data retention policy to 90 days"

# Check password strength assessment
compliance check-strength "admin account meets complexity requirements"

# Search all logs for "database"
compliance search database

# Export compliance records to JSON
compliance export json

# View overall stats
compliance stats

Powered by BytesAgain | bytesagain.com | hello@bytesagain.com