Encrypt

A sysops toolkit for scanning, monitoring, reporting, alerting, tracking top processes, checking usage, verifying system state, applying fixes, cleaning up, backing up, restoring, logging, benchmarking, and comparing — all from the command line.

Commands

Each domain command (scan, monitor, report, etc.) works in two modes:

• Without arguments: displays the 20 most recent entries from that category
• With arguments: logs a new timestamped entry and shows the running total

Data Storage

All data is stored locally in ~/.local/share/encrypt/. Each command writes to its own log file (e.g., scan.log, monitor.log, backup.log) and a shared history.log tracks all activity with timestamps. No cloud sync, no external API calls — everything stays on your machine.

Requirements

• Bash 4+ (uses set -euo pipefail)
• Standard Unix utilities: date, wc, du, grep, head, tail, basename
• No external dependencies or API keys required

When to Use

1. Security scanning and monitoring — Use scan to log security scan results, monitor to track ongoing encryption status, and alert to record security events that need attention
2. Key and certificate lifecycle management — Use backup and restore to track key backup/restore operations, cleanup to log removal of expired certs or old keys, and check to verify current state
3. Encryption performance benchmarking — Use benchmark to log encryption speed tests, compare to track performance across different algorithms or configurations, and report to summarize findings
4. Incident response and auditing — Use log to record custom security events, report to build incident summaries, and search to quickly find relevant entries across all categories
5. System maintenance and compliance — Use fix to track remediation actions, usage to monitor resource consumption, top to identify heavy consumers, and export to generate audit-ready data

Examples

# Scan for encryption issues
encrypt scan "TLS certificates on prod servers — 3 expiring within 30 days"

# Monitor encryption status
encrypt monitor "AES-256 encryption active on all database volumes"

# Set a security alert
encrypt alert "Certificate for api.example.com expires 2025-04-15"

# Backup encryption keys
encrypt backup "GPG keyring exported to /secure/backup/2025-03-18.tar.gz"

# Benchmark encryption performance
encrypt benchmark "AES-256-GCM: 1.2 GB/s encrypt, 1.4 GB/s decrypt on Xeon E5"

# Compare configurations
encrypt compare "ChaCha20 vs AES-256: ChaCha20 15% faster on ARM, AES faster on x86"

# Clean up expired certificates
encrypt cleanup "Removed 12 expired certs from /etc/ssl/archive/"

# Check current state
encrypt check "All 5 TLS endpoints valid, shortest expiry: 89 days"

# Export all data to CSV
encrypt export csv

# View statistics
encrypt stats

# Search for specific entries
encrypt search certificate

How It Works

Encrypt uses a simple append-only log architecture. Each command appends a timestamped, pipe-delimited entry (YYYY-MM-DD HH:MM|value) to its category-specific log file. The stats command aggregates line counts across all logs, search runs case-insensitive grep across all files, and export serializes everything into your chosen format (JSON, CSV, or plain text). The status command gives a quick system health overview including version, total entries, disk usage, and last activity timestamp.

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