new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

OWASP Cheat Sheets · all subjects

logging/audit

3 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Do not log sensitive tenant data in plain text

Avoid logging personally identifiable information, payment details, or sensitive customer data. Log only sufficient identifiers (tenant_id, user_id) for audit purposes.

Implement immutable append-only audit log with tenant isolation

Create TenantAuditLog that records entries with fields: id (random token), tenant_id, user_id, action, details (JSON), timestamp, ip_address, user_agent. Insert into audit_log table without UPDATE/DELETE capability.

Restrict audit log access to own tenant audit trail

When retrieving audit trail via get_tenant_audit_trail(tenant_id, start_date, end_date), verify current tenant context matches requested tenant_id or user has admin role. Raise SecurityException otherwise.

Give your agent this brain