Writing audit logs that pass an MLPS assessment

#md:# The four questions assessors ask

  1. What is recorded: account, time, source IP, object, action, result. A log without a source IP or an object identifier cannot support investigation.
  2. How long it is kept: system logs are usually kept at least six months; business operation logs may be longer depending on the industry.
  3. Tamper resistance: logs need separate or write-once storage, and administrators must not be able to delete them.
  4. Search and export: assessments and internal audit need data by person, time and object, in a readable export format.

How selfhub does it

  • Every file operation is written to a dedicated audit table, kept for 180 days by default and extendable with your plan
  • Filter by account, date range and action type and export to CSV
  • Administrative actions are recorded too, so there is no gap where admins act without a log
  • Abnormal behavior (bulk downloads, out-of-hours access) raises an alert

A tip for preparation

Prepare a feature / demo step / screenshot table against the assessment clauses in advance and walk through it clause by clause; it saves a great deal of time.

# MLPS # compliance # audit
RSS feed

Want these capabilities on your own servers?

A 30-day full-featured trial that you can stop at any time.